csummers311
Posts: 103
Score: 5 Joined: 2/20/2004 From: Tampa, FL Status: offline
|
If you are going to use your current WSUS server then you should unapprove all updates before making it a Software Update Point (SUP). ConfigMgr will take over WSUS on that server and it is not supported to use it like a normal WSUS server. If the computer has the Configuration Manager client installed and you have a SUP then the client will need to (automatically) configure the WSUS settings in the registry. You will need to disable any GPOs that are pointing your computers to WSUS, the GPO will override the ConfigMgr client and you won't get the results you would expect. If you are using the SUP point to do the initial deployment of the ConfigMgr client then you would use a GPO to set the SUP as the WSUS server and then remove the GPO once the clients get installed. If you want to patch computers that do not have the ConfigMgr client then you would need a seperate WSUS server from the SUP and a GPO that points those specified computers to that WSUS server. In my environment I created a new WSUS server, made it a SUP, and left the old WSUS intact in case I need it for some reason. Also, if you install WSUS on the ConfigMgr server, make sure you change the port from the default of 80, I think the Wiki on MyITForum has information on that.
|