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:[email protected]] 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 <[email protected]> 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 [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
