+1. Bingo. This script actually can cure many things. It's the only fix-related work I have ever had to do regarding WSUS.
WSUS is a spectacular product IMO. Sam -----Original Message----- From: Richard Stovall [mailto:[email protected]] Sent: Tuesday, September 29, 2009 1:29 PM To: NT System Admin Issues Subject: RE: WSUS question Naahh. Why bother? There is one thing that I recommend new WSUSers wrap their heads around when deploying and running it for the first time. If you do image based deployment of new computers (including using templates to deploy VMs), WSUS can show seemingly bizarre behavior at times. What can happen is that sometimes a client will show up in your console, and sometimes it won't. This has to do with each client being assigned a GUID, and if you deploy machines from images which already have a GUID assigned the last one to check in is the one that shows up in the WSUS console. This can happen even on properly sysprepped images. It's an easy fix, and is scriptable. For details and some sample scripts see: http://msmvps.com/blogs/athif/archive/2005/09/04/65174.aspx -----Original Message----- From: Joseph Heaton [mailto:[email protected]] Sent: Tuesday, September 29, 2009 1:41 PM To: NT System Admin Issues Subject: RE: WSUS question Instructions??? You want me to read the instructions? Aww man... >>> "Richard Stovall" <[email protected]> 9/29/2009 10:35 AM >>> Correct. See page 32 of the deployment guide. http://www.microsoft.com/downloads/details.aspx?FamilyID=113d4d0c-5649-4 343-8244-e09e102f9706&displaylang=en -----Original Message----- From: Joseph Heaton [mailto:[email protected]] Sent: Tuesday, September 29, 2009 1:24 PM To: NT System Admin Issues Subject: RE: WSUS question That's what I was thinking, thanks to all that suggested that method. One last, possibly silly, question/verification: When I'm setting up the redirection to go to the server, since we used the custom WSUS website during install, the path would be http(s)://servername:8530(8531) Is that correct? >>> "Richard Stovall" <[email protected]> 9/29/2009 10:12 AM >>> I use WSUS for servers and workstations. I've got OUs for different machine types. The server OU has a policy setting of "3 - Auto download and notify for install." The machines get the updates I approve and when I can open a maintenance window I install the updates and restart manually. A small subset of workstations is in an OU with similar settings and the rest of the workstations are set to update and restart on weekends. HTH, RS -----Original Message----- From: Joseph Heaton [mailto:[email protected]] Sent: Tuesday, September 29, 2009 1:04 PM To: NT System Admin Issues Subject: WSUS question Do you guys use WSUS for server updates? If so, how do you handle auto-restarts? We don't want any automatic restarts based on updates, we want notification that it needs to be restarted, but we want to manually do that. If not, how do you handle updates for your servers? Thanks, Joseph L. Heaton Windows Server Support Group Information Technology Branch Department of Fish and Game 1807 13th Street, Suite 201 Sacramento, CA 95811 Desk: (916) 323-1284 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
