An update is available to administrators who opted in through a PowerShell script to the early update ring deployment for Microsoft Endpoint Configuration Manager current branch, version 1910. 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 after version 1910 became available globally. This article contains information about the most significant changes.
This update does not apply to sites that downloaded version 1910 on December 17, 2019, or a later date. Therefore, it will not be listed in the Configuration Manager console for those sites.
Note: This update is superseded by the following update rollup:
KB 4537079 Update Rollup for Microsoft Endpoint Configuration Manager current branch, version 1910
Issues that are fixed
- "Violation of PRIMARY KEY constraint 'OfficeAddinHealth_PK'." appears in the statesys.log after updating to version 1910.
- When using the search feature in a task sequence, the "Result X of Y" label appears does not have a fixed location within the console.
- After updating to 1910, users are listed with their names as (lastname\) instead of (lastname, firstname) as it shows in Active Directory.
- An App group with multiple deployments fails to show up in Software Center when targeted to users as available.
- Enforcing TLS 1.2 can cause content download failures from a cloud distribution point.
- Operating system in-place-upgrade task sequences may not start as expected on Windows 10, version 1709 clients.
- The Configuration Manager console may terminate unexpectedly when configuring a Microsoft Edge Management policy.
- The Configuration Manager console may terminate with an ArgumentOutOfRangeException if the user navigates away from the Deployments node while it is still returning results.
- The Delete Aged Discovery Data task may incorrectly remove active records.
- The SMS Agent Host service on Management Points may terminate unexpectedly after updating to version 1910.
- The 1910 update process may fail due to a duplicate key violation. An error resembling the following is recorded in the ConfigMgrSetup.log.
Violation of UNIQUE KEY constraint 'SR_SummaryTasks_G_AK'. Cant insert dup. key in object 'dbo.SR_SummaryTasks_G'. The dup.key value is (Office Pilot Collection Machines Task)
- Bitlocker Management is an optional feature, now unchecked by default in the Configuration Manager update wizard.
- Distribution Point Status does not load as expected after updating to version 1910.
- The CMGatewaySyncNotificationWorker component reports status message every 1 minute.
- Cloud Management Gateway servers may report authentication errors after updating to version 1910.
- The MP_GetProxyMPListForSite stored procedure does not prefer the clients assigned site, resulting in random MP assignment when fallback is enabled for secondary sites.
- The SMS Agent Host service (CCMExec.exe) may not restart as expected when the client computer reboots during an operating system deployment task sequence.
- Content is not available for tasks sequences when the client is on an intranet network, and the Always Internet Facing (CCMALWAYSINF) parameter is set to 1.
- CMPivot auto completion is not working for the first table in the query.
- The Disable Bitlocker step in the Task Sequence Editor generates an exception when editing a task sequence created in version 1902 or earlier.
- The Software Center client (SCClient.exe) terminates unexpectedly due to unhandled exception when downloading task sequence policy.
Additional hotfixes contained in this update
KB 4535384: Client update available for Configuration Manager current branch, version 1910 early update ring
Update information for Microsoft Endpoint Configuration Manager, version 1910 early update ring
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 1910 and that were downloaded between November 29, 2019 and December 17, 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 1910 from packages that have the following GUIDs:
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.