For more information, see Software update points. Add individual software update points to different boundary groups to control which servers a client can find. If their current software update point is no longer accessible, they also use boundary groups to fallback and find a new one. Internet-based clients: Receive a list of software update points that you configure to allow connections only from the internet, or a list of software update points that allow internet and intranet client connections.Ĭlients use boundary groups to find a new software update point. Intranet-based clients: Receive a list of software update points that you can configure to allow connections only from the intranet, or a list of software update points that allow internet and intranet client connections. Configuration Manager provides clients with a different list depending on the type of client: It prioritizes the software update points in the same forest. The client randomly selects a software update point from the list. Software update point listĬonfiguration Manager provides the client with a software update point list in the following scenarios:Ī new client receives the policy to enable software updatesĪ client can't contact its assigned software update point and needs to switch to another For more information, see Remove a site system role. Then select a new software update point to use as the synchronization source. When there's a failure of the software update point configured as the synchronization source for the site, manually remove the failed role. After you add software update points and start synchronization, view the status of the software update points and the synchronization source from the Software Update Point Synchronization Status node in the Monitoring workspace.
SOFTWARE UPDATE ENABLER INSTALL
The first software update point that you install on a primary site is the synchronization source for all additional software update points that you add at the primary site. Therefore, the client preserves affinity with the last software update point from which it successfully scanned. When the client switches to a new WSUS server to scan for software updates, the result is an increase in the catalog size and associated client-side and network performance demands. Unlike in the design of management points, there are client and network performance costs in the software update point design when clients switch to a new software update point. The failover design of the software update point is different than the pure randomization model that's used in the design for management points.
Software update point on a secondary site.Use an existing WSUS server as the synchronization source at the top-level site.Software update points in an untrusted forest.Manually switch clients to a new software update point.
This section includes the following subtopics: Determine the software update point infrastructure For information about capacity planning for software updates, see Size and scale numbers. Having a good plan for the software update point infrastructure is key to a successful software updates implementation. Applies to: Configuration Manager (current branch)īefore you use software updates in a Configuration Manager production environment, it's important that you go through the planning process.