When you create an active software update point we take over the configuration settings for WSUS running on the active software update point.
We initiate synchronization from the ConfigMgr console. That is the process of contacting WSUS on the active software update point for the site server, requesting that WSUS synchronize with its upstream update source (Microsoft Update on the central site), and then at the central site synchronize the software updates metadata from the WSUS database to the ConfigMgr database. When there are child sites, we replicate the software updates metadata from the central site server database to the child sites. When a site is finished synchronizing, it will send a synchronization request to child sites telling them to initiate a WSUS sync, where WSUS running on the active software update point the that site will synchronize with WSUS running on the active software update point for the parent site. Now we have our metadata in both the WSUS database and the ConfigMgr database.
Clients connect to WSUS running on the active software update point configured for their assigned site and run a scan for updates (based on the classifications and products configured) and send a state message to the site server reporting whether the updates were required or installed.
When you create a deployment and specify to use a new deployment package, you configure the package source (a shared folder that must not be used by any other package). You also specify whether the update files will be downloaded from the Internet or from a local share. When you installed WSUS to store updates locally, you can point to the WSUS location (or any other location where the update files reside) so the site server doesn't need to go to the Internet to get the update files. So, we will get the update files at the location (Internet or local), the files are then downloaded to the package source that you specified. Assuming that you specified a distribution point during the package creation, the source files will now be copied to the distribution points specified. You will then finish the Deploy Software Updates Wizard to complete the deployment.
The clients in the collection that was specified in the deployment will receive an assignment policy that tells them that updates are available for installation, and if a deadline is configured, that the software updates should be downloaded right away to the local cache. The client connects to a distribution point that has the update file and downloads the file. When the deadline is reached or the user initiates installation manually, the update will be installed from the local file.
Ok...that is the full process in a nutshell. In summary, even if you have WSUS download and store approved updates locally, the update files will be downloaded/copied to the specified package source, and then copied to the specified distribution points where the clients will download the files when they receive the assignment policy.
No comments:
Post a Comment