Update for System Center Configuration Manager version 1806, first wave

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

This update does not apply to sites that downloaded version 1806 on August 10, 2018, or a later date. Therefore, it won't be listed in the Administrator Console for those sites.

Configuration Manager Console

• The Configuration Manager console crashes if you create or edit an ADR and set the deployment package to "No deployment package."
   
• CMPivot is missing the "not like" operator.
   
• CMPivot fails to run a PowerShell script that contains a command to retrieve a registry entry if the registry value contains a NULL.
   

Server

• Ccmexec crashes continuously when Pull DPs are installed.
   
• OfflineServicingMgr fails to find the content library location when the Content Library is on a Universal Naming Convention (UNC) path. Error messages that resemble the following are logged in the OfflineservicingMgr.log:

  SMS_OFFLINE_SERVICING_MANAGER Error getting valid content library path from registry value ContentLibraryPath

  SMS_OFFLINE_SERVICING_MANAGER Content library location could not be found

  SMS_OFFLINE_SERVICING_MANAGER Failed to read content library location used to get content of software updates

• OfflineServicingMgr leaks handle and cause a decrease in performance if it fails to find the content library location on a UNC path.
   
• When you edit an existing co-management policy, instead of the changes being saved, the policy is reset to the default state of No AutoEnroll, all workloads set to Configuration Manager, and pilot collection is empty.
   
• CRP certificate revocation is processing slowly and is blocking the main thread in SMS_CERTIFICATE_MANAGER.
   
• On upgrade, if you have any deployments that require approvals that reference built-in CIs created before 1706, you will see significant SQL I/O and high CPU utilization on the MPs as the CIs and deployments are updated.
   
• Phased Deployment Status Wizard shows multiple rows for the same phase with inconsistent data when a collection has machines spread across multiple sites.
   
• Count of AADJoined and HybridAADJoined may be incorrect on the Co-Management dashboard.
   
• Excessive client request time-outs on the cloud management gateway.
   
• After an upgrade to 1806, the performance of the site may be decreased with high I/O and CPU use by sp_UpdResPolicyMap_PolicyAssignment.
   
• Super peers may fail to download partial content when the management point is remote.
   
• State message component SMS_STATE_SYSTEM reported as critical because of a backlog of Script state messages with no output data reported as corrupt.
   
• Download fails when you use CCM client Delta Download channel to download express updates full files.
   
• The process MP_GetSuperPeerContentLocations stored proc may cause decreased SQL performance and block threads.
   
• Pull DPs may fail to be upgraded because MOFCOMP silently fails when Distribution Manager run it. If the Pull DPs are not upgraded, content cannot be downloaded.
   
• The online client status chart on the CMG Dashboard does not aggregate hourly data correctly from multiple MPs.
   
• When you create an SRM based CMG or CDP by using an existing resource group, the region of the resource group is used to create the resources regardless of the region that you specified.
   
• DP upgrade fails If PXE without WDS enabled.
   
• CMPivot returns NULL if any registry entity values are NULL.
   
• BCP for BGB_NetworkInfo live data fails if there is a duplicate subnet for the same IP address and same client.
   
• CMG HTTP listener stops because of an HttpListenerException.
   
• After WDS-Less PXE is enabled, some clients may not start Task Sequence Wizard because a password is incorrectly expected when multiple clients start at the same time. SMSTS.log shows that the password is incorrect even though the wizard not displayed and no password is set.
   
• On a passive site server, the state message files in the management point staging folder may not process.
   
• The WDS-less PXE responder service, configured after upgrade to Configuration Manager 1806, may reject PXE-boot requests from clients when the management point (MP) is remote.
   

Client

• AtomicUpdate and BundledUpdate metadata used for delta download can get truncated. This causes Unified Update Platform (UUP) updates not to be downloaded.
   
• When the Configuration Manager generated certificate option is selected for the site, and a client fails to download content because it does not have the client public key infrastructure (PKI) certificate, if the client is restarted it will still fail to download content even if token-based content locations are available.
   
• After the 1806 upgrade, Configuration Manager clients fail to send client or Management Point (MP) communication status Fallback Status Point (FSP) messages.
   
• When content that downloads from delta download or CMBITSMgr, the optimal content location is not chosen for all content within a package.
   
• Some client state messages may not be sent, resulting in some reports such as co-management, Windows Upgrade for Business and deployment upgrade reporting being out of sync.
   
• An Internet-only AAD-joined device cannot register if an MP was removed from cloud management gateway.
   
• Task sequences that have a restart action before an Install Packages action may fail.  Error messages that resemble the following are logged in the smsts.log:

  Query = 'CCM_UUPPSFXConfig.SiteSettingsKey="1"'

  …

  WMI error reading policy, hr=0x80041010

  …

  Class CCM_UUPPSFXConfig does not exist in name space 'root\ccm\policy\machine' because client has version of

• Unable to delete a secondary site. After the deletion action, the site remains in either an "active" or "deleting" state.
   

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 1806 and that were downloaded between July 26, 2018, and August 09, 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 1806 from packages that have the following GUIDs:

AEEEDD26-D507-4840-9881-EBA398A33B8C

058CA7DF-DBA5-4441-85AF-6AAF31F57E7F

DB2EB391-D92F-47D5-9B4B-BE521C65B7A2

B54DB0D0-FD7F-480C-BC2F-099C28781581

5B823327-92D9-4908-A24C-8D8C6625F407

Note This update does not apply to installations of version 1806 from packages that have the following GUID: 
 
284366B8-7D7C-41FF-A407-A3D61EF98C85
 
If you have this GUID, refer to the KB 4459354 interoperability update for System Center Configuration Manager, version 1806.

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.