A client in boundary group Z fails to reach its last known-good software update point. For the next minutes, the client tries to reach only its original server in boundary group Z. After 10 minutes, Configuration Manager adds the software update points from boundary group A to the pool of available servers.
However, the client doesn't try to contact them or any other server until the initial minute period elapses. After trying to contact the original software update point for minutes, the client expands its search.
It adds servers to the available pool of software update points that are in it's current and any neighbor boundary groups configured for minutes or less.
This pool includes the servers in boundary group A, which were previously added to the pool of available servers. After 10 more minutes, the client expands the search to include software update points from boundary group B. This period is minutes of total time after the client first failed to reach its last known-good software update point.
Along with fallback, use client notification to manually force a device to switch to a new software update point. When you switch to a new server, the devices use fallback to find that new server. Clients switch to the new software update point during their next software updates scan cycle. Review your boundary group configurations. Before you start this change, make sure that your software update points are in the correct boundary groups. For more information, see Manually switch clients to a new software update point.
Starting in version , intranet clients can access a software update point via a cloud management gateway CMG. Assign the CMG to a boundary group, and enable the software update point to Allow Configuration Manager cloud management gateway traffic. When an internet machine connects to the VPN, it will continue to scan against the CMG software update point over the internet.
If the only software update point for the boundary group is the CMG software update point, then all intranet and internet devices will scan against it.
Boundary groups and management points. Otherwise click Next. Finally we are on the System Role Selection step. From the list of available roles, select Software Update Point. Click Next. The firewall on the WSUS server must be configured to allow inbound traffic on these ports. If you have a proxy server configured in your setup, specify the proxy server settings for SUP. The options are greyed out because you must configure the site system role to use a proxy server first.
You can configure an account to be used by the site server when it connects to WSUS that runs on the software update point. In this step you select a synchronization source for the software update point. In other words you define the source from where updates download. You can define a synchronization schedule and configure the software updates to sync automatically. Click Enable synchronization on a schedule box and configure the sync schedule.
You can either select Simple Schedule also known as recurring schedule or go with a custom schedule. By default the synchronization occurs every 7 days. You can change it if required. You can also let Configuration Manager create an alert when the synchronization fails on the site. On this page you can configure the software update to expire as soon as it is superseded by a recent update.
You can also set a software update to expire after specific period of time. Starting in Configuration Manager version , you can specify the supersedence rules behavior for feature updates separately from non-feature updates.
This is a nice addition. To automate the cleanup procedures after each synchronization, Microsoft has added some cool WSUS Maintenance options. If you are using Configuration Manager version or newer, you will find these options. Since we are installing the SUP for the first time, you can leave these options unchecked.
We can later revisit and enable them. Specify the maximum amount of time for a software update installation to complete. I am going to leave the values to default because they look fine to me.
However you can change the values if required. On this page you have to select whether you want to deploy full files for approved updates or deploy both full files and express installation files.
I am going to select Download full files for all approved updates and click Next. When you say you deploy a software update, it is actually very broad term. This is because every software update is defined with an update classification. This helps to organize the different types of updates. When you setup SUP, during the synchronization process, the site synchronizes the metadata for the specified classifications.
To know about these software update classifications, refer this article. Once you know what classifications you require, you can enable them under All Classifications. Wait a minute, let me cover something very important here. When you first install the software update point on the top-level site, you must clear all of the software updates classifications. After the initial software updates synchronization, configure the classifications from an updated list, and then re-initiate synchronization.
We will select the products once we complete the initial SUP synchronization. For every language, you can select the software update files and summary info to download. In this example, I will select only English language. In my other blog I have listed the software updates related log files which you can refer during software updates troubleshooting.
In most cases the installation goes well however if it fails you must know which log file to check. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? Submit and view feedback for This product This page. View all page feedback. In this article.
0コメント