Update for System Center Configuration Manager version 1706, first wave

An update is available to administrators who opted in through a Windows PowerShell script to the first wave (early update ring) deployment for Microsoft System Center Configuration Manager current branch, version 1706. 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 1706 became available globally.

This update is no longer available and has been replaced by update KB 4036267.

• Applications may not install on clients because of a failure to download the required content. When you try to install the software manually through Software Center, the installation is unsuccessful, and you receive an “Unable to download the software” error message. The "More information" section of the error message resembles the following:
  The software change returned error code 0x80070057 (-2147024809)

   

• Client upgrades may be unsuccessful, and errors that resemble the following are logged in the Ccmsetup.log file:
  File C:\windows\ccmsetup\{E71CEDAC-161C-4FC7-BBD1-334BFFC60C1C}\client.msi installation failed. Error text: ExitCode: 1603
  Action: CcmCompileSqlCEScripts.
  ErrorMessages:
  Setup was unable to compile Sql CE script file C:\windows\CCM\UserAffinityStore.sqlce.
  The error code is 80004005.

  MSI: Setup was unable to compile Sql CE script file C:\windows\CCM\UserAffinityStore.sqlce.
  The error code is 80004005.

• Client communication that's directed through the client notification server channel fails. StatusCode 500 is logged in Internet Information Services (IIS) logs on the Management Point.

• The SMS Site Component Manager service (sitecomp.exe) can stop unexpectedly after you upgrade to Configuration Manager version 1706, first wave one. An error that resembles the following is recorded in the Sitecomp.log file:
  A pure virtual function was called. Fatal error, cannot continue.
• You cannot enable a PXE Service Point, and an error that resembles the following is logged in the Distmgr.log file:
  CDistributionManager::ConfigurePXE failed; 0x80041002

• Android for Work devices cannot register with Azure Active Directory, blocking access to Exchange Active Sync.

   

• Improvements: Multiple accessibility improvements are added to the Configuration Manager console.

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 1706 downloaded between August 8 and August 11, 2017.

To verify which first wave build you have 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. The update applies only to first wave installations of version 1706 from packages that have the following GUID:

• ABB97C8D-81E2-4D97-85CD-26FF3C561058.cab

This update does not apply to first wave installations of version 1706 from packages that have the following GUIDs (because they are already up-to-date):

• C88976EC-69E5-4B14-90CE-FF84B656CE86.cab
• B1C7BBFD-4C85-46DF-AB2C-2AB2114ED8F9.cab

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

Note This update does not change the major client version. Therefore, it will not install through a Windows Server Update Services (WSUS) based deployment.

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, and all the hotfixes are applied on its parent primary site.

If the value 0 is returned, the site has not installed all the fixes that apply to the primary site. In this case, you should use the Recover Secondary Site option to update the secondary site.

Install Updates for System Center Configuration Manager

Learn about the terminology Microsoft uses to describe software updates.