Update for System Center Configuration Manager version 1802, first wave

This update is replaced by update KB 4163547. However, if this update is still listed with a state of “Ready to Install” in the Updates and Servicing node, it can be safely ignored. You do not have to install this update if update KB 4163547 is installed.

An update is available to administrators who opted in through a PowerShell script to the first wave (early update ring) deployment for System Center Configuration Manager current branch, version 1802. 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 1802 became available globally. This article contains information about the most significant changes.

This update does not apply to sites that downloaded version 1802 on April 2, 2018 or a later date. Therefore, it will not be listed in the Administrator Console for those sites.

The client version 5.00.8634.1010 and 5.00.8634.1011 have equivalent functionality and the same fix level. They are basically identical releases. The different version numbers indicate only which installation path was taken. The clients that have version 5.00.8634.1010 indicate customers who deployed the non–opt-in release on April 12 or a later date. The clients that have version 5.00.8634.1011 were initially deployed through the System Center Configuration Manager 1802 early opt-in release before April 12 and then were updated to the non–opt-in level.

• The Configuration Manager console may terminate and return an exception when the Run Script wizard is closed.
   
• The Deadline time value cannot be changed in Phase Properties after a new phased deployment is created.
   
• User-available applications do not install from Software Center on devices that are Azure Active Directory (AD)-joined.
   
• The Management insights node in Configuration Manager console does not display empty collections, even if those collections are selected as Action Needed.
   
• Microsoft Edge web browser settings do not correctly deploy to devices as expected.
   
• Multi-selecting a task sequence in Software Center causes a “Software Center cannot be loaded” error message on screen.
   
• Heartbeat discovery and hardware inventory data from Server Core installations of Windows Server 2016 are not processed.
   
• Hierarchy Manager reports errors on a secondary site after Configuration Manager is upgraded to version 1802. Errors entries that resemble the following are recorded in the hman.lof log:

  Microsoft SQL Server reported SQL message 2627, severity 14: [23000][2627][Microsoft][SQL Server Native Client 11.0][SQL Server]Violation of PRIMARY KEY constraint 'DPInfo_PK'. Cannot insert duplicate key in object 'dbo.DPInfo'. The duplicate key value is ({site server}, {site code}).

   
• A Configuration Manager client does not function as a Peer Cache client if there are many (thousands) of cached items.
   
• Configuration Manager clients fail to renew their Windows Hello for Business certificates because of a Management Point error. Errors entries that resemble the following are recorded in the mp_token.log:

  Failed in NCryptImportKey with 0x80090005

   
• Installation of a Configuration Manager, version 1802 site fails. Error entries that resemble the following are recorded in the cmupdate.log:

  ERROR: Failed to renew inventory views and rbac functions
  Failed to update database.
  Failed to apply update changes 0x87d20b15

   
• Modifying installed languages through Setup after installing Configuration Manager fails. An error entry that resembles the following is recorded in the ConfigMgrSetupWizard.log file:

  System.FormatException: Input string was not in a correct format.

This update is available in the Updates and Servicing node of the Configuration Manager console for environments that were installed by using first wave (Fast Ring) builds of version 1802 and that were downloaded between March 22, 2018, and April 2, 2018.

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 1802 from packages that have GUID C78E7992-75DB-4CD2-B89E-8024FC99884B.

Restart information

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.

File information

Install Updates for System Center Configuration Manager

Learn about the terminology Microsoft uses to describe software updates.