Another take.
1. The only requirement for SCCM Software Updates to work is that the automatic updates service is started .. do not configure it at all, especially by GPO, the SCCM client will do the configuration
2. clients will go directly to your primary site where sofwtare update service is installed, as the Software Update point on the secondary will be by default a passive software update point, used for downloading the scan package at nothing else.
3. You are correct with the scanning part, though the clients will not automatically 'pull' down udpates as such, you first have to deploy them the updates via a Deployment Package which is advertised to a collection of clients (via a Deployment template). It's pretty easy once you get the hang of it. Clients will report what patches are required, then you can either create a new deployment package (based on a Deployment Template), or drag and drop the updates on to an existing Deployment Package via Deployment Management. So in summary, the clients will get their updates from an Distribution Point they have access to that contains the Deployment Package
4. If you install a Software Update point on your secondary sites, it will sync upstream to the primary site. For the clients, this will only save the amount of traffic related to the scan packages (It's called a Passive Software Update Point from memory). The actually updates will be downloaded from a distribution point. (Depending on the number of clients you are servicing, I wouldn't bother)
5. as per 5, they will go to the local SUP for downloading the scan package
6. SCCM takes care of it all.
Main Topics
Browse All Topics





by: xxdcmastPosted on 2009-09-01 at 18:46:53ID: 25237626
Ok so here is my take on the situation.
1. You will need to re-enable automatic updates on the client this is how they communicate with WSUS. Rather than going to ms website you point them to your WSUS server with a GPO. See number 6
2. Depending on how your have your WSUS configured it could go to either. If you have only the main WSUS server they will go there but if you configure the other servers to be downstream servers they will go to their local server.
3. Again this depends on if you use a downstream server. If you dont use a downstream server the updates will come from the main server. If you do use the downstream server then the updates will be downloaded one time to the downstream server and then pushed out from there.
4. You are correct this should decrease your bandwith usage and give your clients a local install source.
5. Im not 100% sure on this but I belive it will go to the local server at the site and you can configure those servers to update the main server with their status.
6. You can use a GPO in order to point your clients to the correct servers.