An update is available to administrators who opted in through a PowerShell script to the early update ring deployment for Microsoft System Center Configuration Manager current branch, version 1906. You can access the update in the Updates and Servicing node of the Configuration Manager console.
This update addresses important, late-breaking issues that were resolved before the release of the globally available version of 1906. This article contains information about the most significant changes.
This update does not apply to sites that downloaded version 1906 on August 15, 2019, or a later date. Therefore, it won't be listed in the Administrator Console for those sites.
Issues that are fixed
- Users in custom security roles no longer have access to folders in the Configuration Manager console.
- The SQL view vDCMDeploymentNonCompliantRuleDetailsPerClientMachine is an incorrect version after reinitializing site replication. This affects reporting of device compliance details in the Configuration Manager console.
- If the update to Configuration Manager current branch, version 1906, fails during the Upgrade Configuration Manager database or Copy files steps, the installation retry will fail. This occurs if Azure Active Directory User Discovery is configured in the environment. An error resembling the following is recorded in the CMUpdate.log.
Violation of UNIQUE KEY constraint 'AADDiscovery_Settings_Ex_AK'. Cannot insert duplicate key in object 'dbo.AADDiscovery_Settings_Ex'.
Administrators are unable to disable the TLS 1.1 protocol after updating to version 1906.
The Summarize Installed Software Data fails with errors resembling the following recorded in the smsdbmon.log file.
Cannot insert duplicate key row in object 'dbo.INSTALLED_SOFTWARE_DATA_Summary' with unique index 'INSTALLED_SOFTWARE_DATA_Summary_idx_ByCode'.
The client registration process fails if the database contains duplicate client key data. This duplication may occur if the client’s certificate changes.
When using CMPivot from inside the Configuration Manager console, a new client job is created after you refine a query and run it again. This can delay results being returned, and is more resource intensive on client devices.
The Reassign Shared Distribution Point Wizard may fail with an unhandled exception, generating the following error text in the console.
The given key was not present in the dictionary.
Changes to the Enabled status of site maintenance task are not shown in the Site Maintenance properties window without closing and reopening the window.
The Connection Health dashboard in the Desktop Analytics Servicing node takes longer than expected to display results.
Alerts are displayed in English in the Monitoring node of the Configuration Manager console even when another alert language setting is specified.
Update information for System Center Configuration Manager, version 1906
This update is available in the Updates and Servicing node of the Configuration Manager console for environments that were installed by using early update ring builds of version 1906 and that were downloaded between July 26, 2019, and August 14, 2019.
To verify which first wave build is installed, look for a package GUID by adding the Package GUID column to the details pane of the Updates and Servicing node in the console. This update applies to first wave installations of version 1806 from packages that have the following GUIDs:
Note This update does not apply to installations of version 1906 from packages that have the following GUID:
You do not have to restart the computer after you apply this update.
Update replacement information
This update replaces the previously released update KB 4515740: Custom security roles lose folder permissions after an update to Configuration Manager current branch, version 1906
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.