Automatic Updates Configuration
How does automatic updates work for Core Server? Is there any way to configure Automatic Updates in the following way?
1. User defines a max cache storage (X)
2. AU are downloaded and stay in cache until X is reached and the patch is installed
3. If X is reached, AU stops downloading until user updates the machine and the installed updates can be removed from cache.
BTW, the reason I am asking is because I am testing this in a Virtual Machine and when I try to set automatic updates it says:
"CScript Error. Execution of the Windows Script Host Failed. (Not Enough Storage is available to complete this operation)"
Thanks,
Réponses
Your command should look like:
cscript SCRegEdit.wsf /AU 4
instead of:
cscript SCRegEdit.wsf /AU /4
Following the link I posted in an earlier response you might have found out there are only two valid options for Server Core installations of Windows Server 2008:
1 - Disable Automatic Updates
4 - Automatically download updates and install them on the schedule specified below
The other options are not available, since they rely on explorer.exe as the shell (cmd.exe is the default shell for Server Core installations) or the availability of the Automatic Updates Configuration Panel applet. (not present in Server Core)
Toutes les réponses
I've looked quite extenisvely at the configuration of Automatic Updates on Server Core installations of Windows Server 2008, but have not experienced the error you encounter.
Could you please post the specific command you typed which generated the error?
Could you also specify the version of Windows Server 2008 you are testing?
I just downloaded RC0 Today and that is what I used.
cscript c:\windows\system32\ scregedit.wsf /au /4
I also tried using /1 instead of /4 but had the same issue.
Again, I am just testing this out so I did it in a Virtual Server R2 64bit SP1 machine.
Your command should look like:
cscript SCRegEdit.wsf /AU 4
instead of:
cscript SCRegEdit.wsf /AU /4
hehe. I got it from http://www.petri.co.il/configuring-windows-server-2008-networking-settings.htm. I found something else that is wrong from his posting there so I should have known that there was a possibility of syntax. I cannot test it right now, but I will do tonight. Thanks,
ok. I tried and it gave me the same error. Since I saw that you had put AU in caps, I changed it and it worked. So one has to make sure that AU is in CAPS.
Now. This turns on Automatic Updates. However, how does one define which kind of update one wants (Auto Download/Install, Auto Download, Notification or None)?
Thanks,
Following the link I posted in an earlier response you might have found out there are only two valid options for Server Core installations of Windows Server 2008:
1 - Disable Automatic Updates
4 - Automatically download updates and install them on the schedule specified below
The other options are not available, since they rely on explorer.exe as the shell (cmd.exe is the default shell for Server Core installations) or the availability of the Automatic Updates Configuration Panel applet. (not present in Server Core)
Yeah. I found out that there are two options. However, one of the options says "and install them on the schedule specified below" so I was hoping that somehow you can tell the schedule not to do it at all.
Thanks,
hehe. I installed another image with Windows 2008 Full installation and tried to use the command to enable the Automatic Updates and it says that it cannot find c:\Windows\System32\scregedit.wsf
. I guess I will have to do it via GUI
.
Hi,
Yes, scregedit.wsf and oclist.exe are only in Server Core.
AndrewUnder c:\Windows\System32\ I've run "cscript scregedit.wsf /AU 4"
The result is the following message: "c:\Windows\System32\scregedit.wsf(777, 3) (null): 0x80240037"
After running "cscript scregedit.wsf /AU /v" I then am told that "Auto Update AUOptions Value not set"
So somethings gotten buggy there. **edit** perhaps this is due to WSUS pushing the setting ***end edit**
P.S. I am able to trigger an update check through the use of the WSUS detect mechanism. Type wuauclte.exe /detectnow at a command. After a short period of time then ctrl-alt-del and see if the shutdown button is offering updates. This of course is merely a workaround until the Auto Update functionality can get set.
- Windows Automatic Updates feels half done in Server 2008 Core.
It's waiting till 3:00 AM or Shutdown! Where is the Applynow cmd option?!?
- I also have the "c:\Windows\System32\scregedit.wsf(777, 3) (null): 0x80240037" error when using the cscript scregedit.wsf /AU 4 command. I have gone in and manual set the AUOption reg key to 4 and this has at least looks like it might have done something as when i do a cscript scregedit.wsf /AU /v it now returns "4" value.
How do i apply patches now without shutting down the server... This would be very useful on server core. ???
Alan Burchill - Not only an addnow functionality missing, also how can you view what is in pipeline for updating, both recomended update but also what already been downloaded and waiting for installation.
You can change the schedule update time through regedit, but seems a little to much. - This error is also due to having a domain policy for WSUS affecting the Core server. In my case it worked after moving my core server to another OU not affected by my WSUS policy.
I also run gpupdate /force to update my policy on the Core server and finally tried the command cscript SCregEdit.wsf /AU 1 again. This time it worked great. I wrote a FREE application to manage Windows 2008 Core servers.
This application includes a module to show updates available and install selected updates. You can set Automatic Updates and select the day/hour or Turn Off Automatic Updates.
Visual Core Configurator 2008 is available to download at http://ctxadmtools.musumeci.com.ar- Hello,
i had the same issue (C:\Windows\System32\Scregedit.wsf(777, 3) (null): 0x80240037).
The server is in workgroup since the beginning. I found that i had this registry entries:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
I removed it, and then the command worked immedately. I am running Windows Server 2008 R2 core.
