The following list describes the basic steps for the synchronization process on the top-level site: You can specify an existing WSUS server that is not in the Configuration Manager hierarchy instead of Microsoft Updates as the synchronization source.
The other software update points at the site use the first software update point as the synchronization source. This synchronizes from Microsoft Update or a WSUS server not in your Configuration Manager hierarchy. The first software update point that you install is configured as the synchronization source.
You can install multiple software update points at a primary site. For more information about compliance assessment, see the Software updates compliance assessment section in this topic.
The compliance information is then sent to the management point that then sends the information to the site server. For details, see software updates client settings.Īfter the client receives the policy, the client starts a scan for software updates compliance and writes the information to Windows Management Instrumentation (WMI). However, if you set the Enable software updates on clients client setting to No to disable software updates on a collection or in the default settings, the location for software update points are not sent to associated clients. Software updates are enabled by default in client settings. When synchronization is complete at each primary site or secondary site, a site-wide policy is created that provides to client computers the location of the software update points. When Configuration Manager finishes software updates synchronization at the top-level site, software updates synchronization starts at child sites, if they exist. The top-level site (central administration site or stand-alone primary site) synchronizes with Microsoft Update on a schedule or when you manually start synchronization from the Configuration Manager console. Software updates synchronization in Configuration Manager connects to Microsoft Update to retrieve software updates metadata. However, because of the changing nature of technology and the continual appearance of new security threats, effective software update management requires consistent and continual attention.įor an example scenario that shows how you might deploy software updates in your environment, see Example scenario to deploy security software updates. An effective software update management process is necessary to maintain operational efficiency, overcome security issues, and maintain the stability of the network infrastructure. Software updates in Configuration Manager provides a set of tools and resources that can help manage the complex task of tracking and applying software updates to client computers in the enterprise. Applies to: Configuration Manager (current branch)
0 kommentar(er)
