If your site uses automatic client upgrade, when you update the site to Microsoft Endpoint Configuration Manager current branch, version 1910, all clients immediately upgrade after the site updates successfully. The only randomization is when clients receive the policy, which by default is every hour. For a large site with many clients, this behavior can consume a significant amount of network traffic and stress distribution points.
Note: This issue is already resolved in the revised version of Configuration Manager version 1910 released on January 17, 2020. It is also resolved with the following update rollup:
KB 4537079 Update Rollup for Microsoft Endpoint Configuration Manager current branch, version 1910
Update information for Microsoft Endpoint Configuration Manager current branch, version 1910
This update is applicable only to early update and globally available installations of Configuration Manager, version 1910 that are installed by using one of the following package GUIDs:
It is also applicable to the following package GUID's with the private TAP rollup, or update KB 4535819 applied:
To verify which build is installed, add the Package GUID column to the details pane of the Updates and Servicing node in the console.
Users who installed an early update ring version of 1910 should first apply the following update.
4535819 Update for Microsoft Endpoint Configuration Manager version 1910, early update ring
You do not have to restart the computer after you apply this update.
Update replacement information
This update does not replace any previously released update.
Additional installation information
After you install this update on a primary site, pre-existing secondary sites must be manually updated. To update a secondary site in the Configuration Manager console, click Administration, click Site Configuration, click Sites, click Recover Secondary Site, and then select the secondary site. The primary site then reinstalls that secondary site by using the updated files. Configurations and settings for the secondary site are not affected by this reinstallation. The new, upgraded, and reinstalled secondary sites under that primary site automatically receive this update.
Run the following SQL Server command on the site database to check whether the update version of a secondary site matches that of its parent primary site:
select dbo.fnGetSecondarySiteCMUpdateStatus ('SiteCode_of_secondary_site')
If the value 1 is returned, the site is up-to-date, with all the hotfixes applied on its parent primary site.
If the value 0 is returned, the site has not installed all the fixes that are applied to the primary site, and you should use the Recover Secondary Site option to update the secondary site.