Update Rollup for System Center Configuration Manager current branch, version 1906

Van toepassing: System Center Configuration Manager (current branch - version 1906)

Summary


This article describes issues that are fixed in this update rollup for Microsoft System Center Configuration Manager current branch, version 1906. This update applies both to customers who opted in through a PowerShell script to the early update ring deployment, and customers who installed the globally available release.

For additional information on changes in Configuration Manager version 1906, refer to:
What’s new in version 1906 of Configuration Manager current branch

Summary of changes in System Center Configuration Manager current branch, version 1906

Issues that are fixed


  • The Configuration Manager console may terminate unexpectedly after reevaluating Management Insight rules or synchronizing third party updates.
  • The Task Sequence Editor may return an Out of Memory error when trying to save large task sequences.
  • Alternate Content Provider (ACP) settings are not defined as expected in the policy for custom client settings. Affected customers should remove the original custom client setting for Software Deployment, then recreate the Software Deployment client setting after installing this update.
  • Special characters, such as an apostrophe, in metadata cause the evaluation of application groups to fail. The SettingsAgent.log contains entries similar to the following.
  • Windows Server 2019 displays as Unknown in the Microsoft Defender Advanced Thread Protection dashboard.
  • Group membership data is removed if the Active Directory group discovery process fails with the following error recorded in the adgdis.log

The group membership data is restored after the discovery process runs successfully.

  • A management point is unable to connect to a read-only replica in environments using SQL Server Always On availability groups.

 

Additional changes


  • A cloud distribution point can now be defined as the content source for a pull-distribution point on the central administration site (CAS).

 

Update rollup for System Center Configuration Manager current branch, 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 or globally available builds of version 1906.

Members of the Configuration Manager Technology Adoption Program (TAP) must first apply the private TAP rollup before this update is displayed.

To verify which build is in use, look for a Package GUID by adding the Package GUID column to the details pane of the Updates and Servicing node in the console. The update applies to installations of version 1906 from packages that have the following GUIDs:

  • F0B30EB3-B2B8-4AEA-88C3-3336E53EAB13
  • B28C4A2A-9297-4E9C-B0EE-3BB55DE1ACB9
  • AC5BDC8B-2700-4F0D-AEB2-5F94B55111B6
  • 18F5A2D7-BCA6-4CA2-A296-F753E702A959
  • EF272173-F3A9-413D-B4CF-56662CB102F2

Update replacement information

This update replaces the following previously released updates:

KB 4515740: Custom security roles lose folder permissions after an update to Configuration Manager current branch, version 1906

KB 4516430: Update for System Center Configuration Manager version 1906, early update ring

Restart information

You do not have to restart the computer after you apply this 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 a value of 1 is returned, the site is up to date, with all the hotfixes applied on its parent primary site.

If a value of 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.