rdixon
Posts: 31
Score: 3 Joined: 5/23/2005 From: rdixon5652@hotmail.com Status: offline
|
With the integration of WSUS and ConfigMgr, first you only have the ability to setup auto approval from within WSUS. This you probably figured out. No auto approval option in ConfigMgr. When approving or auto approving updates in WSUS, WSUS is the tool that will actually delivering the updates to clients. When you manually approve updates in ConfigMgr, and deploy those updates, ConfigMgr will be the tool that delivers updates to clients. Once you have ConfigMgr/WSUS running, clients assigned to a site configured with WSUS/SUP Points will be configured to run scans against your WSUS/SUP Point role only automatically. If a client that is assigned to this site wants to scan against the Microsoft Updates site, the user will have to click on the link in the Windows Update dialog that says "Check online for updates from Microsoft Update". Else your client will always scan against your ConfigMgr site's WSUS/SUP point roles. Actually RTM and SP1 requires WSUS. You can't install a Software Update Point Role with WSUS previously installed. So the catch is, if you approve updates in WSUS, WSUS delivers the content/update to clients. If you approve and deploy in ConfigMgr, ConfigMgr will deliver the content/update to clients. Note: If you do both approval in WSUS and approval and deployment in ConfigMgr, the you may hit your clients twice with updates. Because one tool can come by and patch the system and needs a reboot to satisfy the installation requirement, and the other tool could come by and also attempt to patch the system not knowing it was patched already.
_____________________________
Richard Dixon MSFT Sr Systems Engineer
|