Couldn't you also create a test OU, create a GPO for the new WSUS server, link it to the test OU, put the VMs in that OU, reboot the VMs for the OU move and verify your WSUS settings? That way you are not touching production and also, even better, not relying on reg hacks.
Thanks Webster > -----Original Message----- > From: Michael Leone [mailto:[email protected]] > Subject: Registry entries to set a WSUS client > > I'd like to test my new WSUS server, before changing my GPO to point to it. > And it occurred to me that I could set a couple test VMs to point to the new > server, and see if they can get their updates from it, before making the > change to the GPO. There used to be a way to set this via registry entries. > Anybody know if this would this still work on a Win2008 R2 server? > > Windows Registry Editor Version 5.00 > > [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\windows\Windows > Update] > "WUServer"="http://new-WSUS-server"; > "WUStatusServer"="http://new-WSUS-server"; > > [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\windows\Windows > Update\AU] > "UseWUServer"=dword:00000001 > "NoAutoUpdate"=dword:00000000 > "AUOptions"=dword:00000002 > "ScheduledInstallDay"=dword:00000000 > "ScheduledInstallTime"=dword:00000003 > "DetectionFrequencyEnabled"=dword:00000001 > "DetectionFrequency"=dword:00000001 > "NoAUAsDefaultShutdownOption"=dword:00000001 > "NoAUShutdownOption"=dword:00000001 > "RescheduleWaitTimeEnabled"=dword:00000001 > "RescheduleWaitTime"=dword:00000001 > "UseWUServer"=dword:00000001 > > If I import these registry entries to a test Win2003 and Win2008 R2 VMs, and > then stop and start the Windows Update service, those VMs should check in > with the new server, and get it's updates. Then I can see that the new server > is working. Then I can change the GPO ... ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
