An update is available to address important upgrade-related issues for Microsoft System Center Configuration Manager current branch, version 1806. The issues that are described in this article apply only to sites that upgraded to version 1806 before August 24, 2018.
The fixes for these issues are included in the builds of version 1806 that are available from August 24, 2018, onward.
Issues that are fixed
- After the WDS-less PXE responder service is configured after an upgrade to Configuration Manager 1806, it may reject PXE-boot requests from clients when the management point (MP) is remote.
- 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.
- CMPivot cannot run a PowerShell script that contains a command to retrieve a registry entry if the registry contains a NULL value.
Update information for System Center Configuration Manager, version 1806
This update is available in the Updates and Servicing node of the Configuration Manager console for environments that were installed by using builds of version 1806 and that were downloaded before August 24, 2018.
To verify which 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 installations of version 1806 from packages that have the following GUID:
This update does not apply to installations of version 1806 from packages that have the following GUIDs:
If you have any of these GUIDs, refer to KB 4346645 Update for System Center Configuration Manager version 1806, first wave.
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 updated 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 name||File version||File size||Date||Time||Platform|
|Ccmsetup.cab||Not applicable||9,501||23-Jul-2018||20:36||Not applicable|
|Client.msi||Not applicable||47,407,104||20-Aug-2018||01:15||Not applicable|
|Cmpivotcontent.xml||Not applicable||53,791||20-Aug-2018||01:15||Not applicable|
|Setupcore.dll||Not applicable||39,518,208||20-Aug-2018||01:15||Not applicable|