Re: Registry entries to set a WSUS client
On Wed, Feb 6, 2013 at 12:51 PM, Andrew S. Baker asbz...@gmail.com wrote: Yes, it still does work if you change the registry manually, but having a separate OU for testing (like everyone else is saying) is the best path. Yes, you're right. So I did this - set up a test OU, and a test GPO, pointing at my new WSUS server. I rolled out some new VMs - Win7, Win2003, Win2008, Win2012, put them in that OU, added them to the group that links to that new GPO. All are showing up in the new WSUS server (yay!). However, the 2012 server is showing up as OS Win2003 STD x64, and not Win2012. What's up with that? :-) I am up to date on the WSUS updates, apparently. Is this just a display bug? It shows I need 14 updates (which I suppose is correct), ~ 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 listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
RE: Registry entries to set a WSUS client
Do you have this update? http://blogs.technet.com/b/sus/archive/2012/09/04/an-update-for-windows-server-update-services-3-0-service-pack-2-is-available-kb2734608.aspx Thanks Webster -Original Message- From: Michael Leone [mailto:oozerd...@gmail.com] Sent: Thursday, February 07, 2013 10:53 AM To: NT System Admin Issues Subject: Re: Registry entries to set a WSUS client On Wed, Feb 6, 2013 at 12:51 PM, Andrew S. Baker asbz...@gmail.com wrote: Yes, it still does work if you change the registry manually, but having a separate OU for testing (like everyone else is saying) is the best path. Yes, you're right. So I did this - set up a test OU, and a test GPO, pointing at my new WSUS server. I rolled out some new VMs - Win7, Win2003, Win2008, Win2012, put them in that OU, added them to the group that links to that new GPO. All are showing up in the new WSUS server (yay!). However, the 2012 server is showing up as OS Win2003 STD x64, and not Win2012. What's up with that? :-) I am up to date on the WSUS updates, apparently. Is this just a display bug? It shows I need 14 updates (which I suppose is correct), ~ 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 listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
RE: Registry entries to set a WSUS client
First and foremost I suggested that before Andrew did. He just copied off me. http://support.microsoft.com/kb/2734608 Then reregister the server. Also that update needs to be on your console machine if that is how you are doing it. Andrew is going to copy, I just know it. -Original Message- From: Michael Leone [mailto:oozerd...@gmail.com] Sent: Thursday, February 07, 2013 11:59 AM To: NT System Admin Issues Subject: Re: Registry entries to set a WSUS client On Wed, Feb 6, 2013 at 12:51 PM, Andrew S. Baker asbz...@gmail.com wrote: Yes, it still does work if you change the registry manually, but having a separate OU for testing (like everyone else is saying) is the best path. Yes, you're right. So I did this - set up a test OU, and a test GPO, pointing at my new WSUS server. I rolled out some new VMs - Win7, Win2003, Win2008, Win2012, put them in that OU, added them to the group that links to that new GPO. All are showing up in the new WSUS server (yay!). However, the 2012 server is showing up as OS Win2003 STD x64, and not Win2012. What's up with that? :-) I am up to date on the WSUS updates, apparently. Is this just a display bug? It shows I need 14 updates (which I suppose is correct), ~ 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 listmana...@lyris.sunbeltsoftware.com 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 listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
Re: Registry entries to set a WSUS client
On Thu, Feb 7, 2013 at 12:16 PM, Webster webs...@carlwebster.com wrote: Do you have this update? http://blogs.technet.com/b/sus/archive/2012/09/04/an-update-for-windows-server-update-services-3-0-service-pack-2-is-available-kb2734608.aspx I don't see that on my list of WSUS updates, that my WSUS server has ... I will download and install it ... Thanks Thanks Webster -Original Message- From: Michael Leone [mailto:oozerd...@gmail.com] Sent: Thursday, February 07, 2013 10:53 AM To: NT System Admin Issues Subject: Re: Registry entries to set a WSUS client On Wed, Feb 6, 2013 at 12:51 PM, Andrew S. Baker asbz...@gmail.com wrote: Yes, it still does work if you change the registry manually, but having a separate OU for testing (like everyone else is saying) is the best path. Yes, you're right. So I did this - set up a test OU, and a test GPO, pointing at my new WSUS server. I rolled out some new VMs - Win7, Win2003, Win2008, Win2012, put them in that OU, added them to the group that links to that new GPO. All are showing up in the new WSUS server (yay!). However, the 2012 server is showing up as OS Win2003 STD x64, and not Win2012. What's up with that? :-) I am up to date on the WSUS updates, apparently. Is this just a display bug? It shows I need 14 updates (which I suppose is correct), ~ 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 listmana...@lyris.sunbeltsoftware.com 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 listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
Re: Registry entries to set a WSUS client
On Thu, Feb 7, 2013 at 12:17 PM, Kennedy, Jim kennedy...@elyriaschools.org wrote: First and foremost I suggested that before Andrew did. He just copied off me. True. Thanks, first and foremost! :-) http://support.microsoft.com/kb/2734608 Then reregister the server. Also that update needs to be on your console machine if that is how you are doing it. I did download and install that update, and now my Win2012 server shows up as Win2012. I will re-synchronize again, before I update the Win2012 server. Andrew is going to copy, I just know it. Imitation is the sincerest form of flattery -Original Message- From: Michael Leone [mailto:oozerd...@gmail.com] Sent: Thursday, February 07, 2013 11:59 AM To: NT System Admin Issues Subject: Re: Registry entries to set a WSUS client On Wed, Feb 6, 2013 at 12:51 PM, Andrew S. Baker asbz...@gmail.com wrote: Yes, it still does work if you change the registry manually, but having a separate OU for testing (like everyone else is saying) is the best path. Yes, you're right. So I did this - set up a test OU, and a test GPO, pointing at my new WSUS server. I rolled out some new VMs - Win7, Win2003, Win2008, Win2012, put them in that OU, added them to the group that links to that new GPO. All are showing up in the new WSUS server (yay!). However, the 2012 server is showing up as OS Win2003 STD x64, and not Win2012. What's up with that? :-) I am up to date on the WSUS updates, apparently. Is this just a display bug? It shows I need 14 updates (which I suppose is correct), ~ 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 listmana...@lyris.sunbeltsoftware.com 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 listmana...@lyris.sunbeltsoftware.com 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 listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
Re: Registry entries to set a WSUS client
LOL. Hey, I did give anonymous attributions. :) *ASB **http://XeeMe.com/AndrewBaker* http://xeeme.com/AndrewBaker* **Providing Virtual CIO Services (IT Operations Information Security) for the SMB market…*** On Thu, Feb 7, 2013 at 12:17 PM, Kennedy, Jim kennedy...@elyriaschools.orgwrote: First and foremost I suggested that before Andrew did. He just copied off me. http://support.microsoft.com/kb/2734608 Then reregister the server. Also that update needs to be on your console machine if that is how you are doing it. Andrew is going to copy, I just know it. -Original Message- From: Michael Leone [mailto:oozerd...@gmail.com] Sent: Thursday, February 07, 2013 11:59 AM To: NT System Admin Issues Subject: Re: Registry entries to set a WSUS client On Wed, Feb 6, 2013 at 12:51 PM, Andrew S. Baker asbz...@gmail.com wrote: Yes, it still does work if you change the registry manually, but having a separate OU for testing (like everyone else is saying) is the best path. Yes, you're right. So I did this - set up a test OU, and a test GPO, pointing at my new WSUS server. I rolled out some new VMs - Win7, Win2003, Win2008, Win2012, put them in that OU, added them to the group that links to that new GPO. All are showing up in the new WSUS server (yay!). However, the 2012 server is showing up as OS Win2003 STD x64, and not Win2012. What's up with that? :-) I am up to date on the WSUS updates, apparently. Is this just a display bug? It shows I need 14 updates (which I suppose is correct), ~ 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 listmana...@lyris.sunbeltsoftware.com 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 listmana...@lyris.sunbeltsoftware.com 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 listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
RE: Registry entries to set a WSUS client
Would it be easier to put the test subjects in their own OU, block the domain gpo for updates and make a new gpo for that ou? After testing is complete you now have a tested gpo to roll out with. -Original Message- From: Michael Leone [mailto:oozerd...@gmail.com] Sent: Wednesday, February 06, 2013 11:35 AM To: NT System Admin Issues 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\WindowsUpdate] WUServer=http://new-WSUS-server; WUStatusServer=http://new-WSUS-server; [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\windows\WindowsUpdate\AU] UseWUServer=dword:0001 NoAutoUpdate=dword: AUOptions=dword:0002 ScheduledInstallDay=dword: ScheduledInstallTime=dword:0003 DetectionFrequencyEnabled=dword:0001 DetectionFrequency=dword:0001 NoAUAsDefaultShutdownOption=dword:0001 NoAUShutdownOption=dword:0001 RescheduleWaitTimeEnabled=dword:0001 RescheduleWaitTime=dword:0001 UseWUServer=dword:0001 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 ... Thanks ~ 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 listmana...@lyris.sunbeltsoftware.com 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 listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
RE: Registry entries to set a WSUS client
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:oozerd...@gmail.com] 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:0001 NoAutoUpdate=dword: AUOptions=dword:0002 ScheduledInstallDay=dword: ScheduledInstallTime=dword:0003 DetectionFrequencyEnabled=dword:0001 DetectionFrequency=dword:0001 NoAUAsDefaultShutdownOption=dword:0001 NoAUShutdownOption=dword:0001 RescheduleWaitTimeEnabled=dword:0001 RescheduleWaitTime=dword:0001 UseWUServer=dword:0001 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 listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
Re: Registry entries to set a WSUS client
On Wed, Feb 6, 2013 at 11:51 AM, Webster webs...@carlwebster.com 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:oozerd...@gmail.com] 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:0001 NoAutoUpdate=dword: AUOptions=dword:0002 ScheduledInstallDay=dword: ScheduledInstallTime=dword:0003 DetectionFrequencyEnabled=dword:0001 DetectionFrequency=dword:0001 NoAUAsDefaultShutdownOption=dword:0001 NoAUShutdownOption=dword:0001 RescheduleWaitTimeEnabled=dword:0001 RescheduleWaitTime=dword:0001 UseWUServer=dword:0001 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 listmana...@lyris.sunbeltsoftware.com 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 listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
RE: Registry entries to set a WSUS client
I don't use all of those, but have a few non-domain WS08 R2 servers that have settings defined under (HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\windows\WindowsUpdate\AU(second section) to autoinstall non-reboot patches (for FEP AV Definitions), and it works. -Original Message- From: Michael Leone [mailto:oozerd...@gmail.com] Sent: Wednesday, February 06, 2013 7:57 AM To: NT System Admin Issues 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\WindowsUpdate] WUServer=http://new-WSUS-server; WUStatusServer=http://new-WSUS-server; [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\windows\WindowsUpdate\AU] UseWUServer=dword:0001 NoAutoUpdate=dword: AUOptions=dword:0002 ScheduledInstallDay=dword: ScheduledInstallTime=dword:0003 DetectionFrequencyEnabled=dword:0001 DetectionFrequency=dword:0001 NoAUAsDefaultShutdownOption=dword:0001 NoAUShutdownOption=dword:0001 RescheduleWaitTimeEnabled=dword:0001 RescheduleWaitTime=dword:0001 UseWUServer=dword:0001 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 ... Thanks ~ 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 listmana...@lyris.sunbeltsoftware.com 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 listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
