On Wed, Feb 6, 2013 at 11:51 AM, Webster <[email protected]> wrote: > 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?
I could. That's a lot more work than just changing 2 registry entries on some test VMs that are already set to look at my old WSUS server. :-) > That way you are not touching production and also, even better, not relying > on reg hacks. I was never touching production anyway - I created a new WSUS server, and using a test VM that I keep around to test stuff like this. Never changed any settings on production servers, or changed any production GPOs. Never pointed the new WSUS server at the old server, started over clean. Changing the registry entries and restarting the service worked just fine, BTW. The test VM checked in to the new server, and I see a list of updates that need to be applied (as expected, since this test VM hasn't been updated in a few months). So it looks like all that is left is changing the production GPO to point to the new server, give the clients a couple days to check in, and All Should Be Good ... > > 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 > ~ 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
