Update rollup for System Center Configuration Manager current branch, version 1802

Notice


This update rollup was revised on June 14, 2018, to prevent an issue that affects some first wave users. No action is required for the following groups:
 

  • First wave users who first applied update 4132447 before they applied this update rollup.

  • Non-first wave users who applied the original version of this update rollup.

Summary

This article describes the issues that are fixed in this update rollup for Microsoft System Center Configuration Manager current branch, version 1802.

Issues that are fixed

  • In System Center Configuration Manager current branch, version 1802, conditional access compliance reporting fails for intranet clients if a proxy is required. This failure occurs even if the proxy settings are defined on the Network tab of Configuration Manager properties in the client Control Panel item.

    Additionally, errors entries that resemble the following are recorded in the ComplRelayAgent.log file on the client:

    [CCMHTTP] ERROR: URL={Intune CA Relay service URL}(GuidKey1={guid},GuidKey2={guid},GuidKey3={guid}, Port=443, Options=31, Code=12002, Text=ERROR_WINHTTP_TIMEOUT

     

  • Data warehouse synchronization may be unsuccessful in large environments. The Microsoft.ConfigMgrDataWarehouse.log file contains entries that resemble the following:

    DATA_WAREHOUSE_SERVICE_POINT Error: 0 : {timestamp}: Arithmetic overflow error converting expression to data type int.

     

  • The Configuration Manager console may terminate unexpectedly after you go to the Script Status node in the Monitoring workspace.

     

  • Synchronization of Unified Update Platform (UUP) files may time-out on a Central Administration site or primary site.

     

  • After you apply this update rollup, files that are associated with UUP packages will be downloaded only one time to a site server if the same file is already present in the local package source cache.

     

  • A multicast operating system deployment task sequence that is initiated from Software Center is unsuccessful if it is used together with a distribution point that is configured for HTTPS traffic.

     

  • After you update to Configuration Manager current branch, version 1802, the Run Script feature does not work with spaces in the script parameters.

     

  • After you update to Configuration Manager current branch, version 1710 or a later version, the SMSTSDownloadProgram variable does not function as expected in conjunction with applications or software updates. This issue occurs on clients in provisioning mode. It prevents an Alternate Content Provider from being specified in the task sequence.

     

  • SQL Server replication may be unsuccessful in a hierarchy after a secondary site is deleted and uninstalled. When this occurs, the ConfigMgrRCMQueue replication queue is disabled, and the SQL error log contains entries that resemble the following:

    257, Level 16, State 3, Procedure spLogEntry, Line 0, Message: Implicit conversion from data type xml to nvarchar(max) is not allowed. Use the CONVERT function to run this query.

     

  • The Application Management option is not available for OneNote for Android when you deploy it in a Configuration Manager and Microsoft Intune hybrid environment.

     

  • After you update to Configuration Manager current branch, version 1802, Software Center settings cannot be customized from the Configuration Manager console. When you click the Customize button in the Default Settings pane, you receive an unhandled exception error message that resembles the following:

    System.IO.InvalidDataException: Invalid format in settings xml.


    This error occurs if a custom logo is specified before you install the version 1802 update.

     

  • Management points cannot communicate with a specified Device Health Attestation service if a proxy server is required.

     

  • The operating system is reinstalled on an existing Configuration Manager client, If the same host name is maintained that is registered in Azure Active Directory, Conditional Access compliance scenarios may start to fail.

     

  • Configuration Manager Data Warehouse synchronization may be unsuccessful when it processes inventory summarization. This issue can occur because the tempdb database on the server that is running SQL Server is running out of space while stored procedures are running.

     

  • The Configuration Manager client installation may be unsuccessful in a co-management scenario. This issue can occur if the installation is initiated from Microsoft Intune to an Azure Active Directory-joined client. Additionally, errors entries that resemble the following are recorded in the ccmsetup.log file on the client:

    Client certificate is not provided.

    Failed to receive ccm message response. Status code = 401 and StatusText = 'CMGConnector_Unauthorized'

    GetDPLocations failed with error 0x80004005

     

  • If the Enable clients to use a cloud management gateway option is set to No in an environment that has multiple management points and cloud management gateways in use, the client cannot process any location service requests. Additionally, errors entries that resemble the following are repeated in the ClientLocation.log file on the client:

    Cloud Management Gateway is not allowed to use on this machine, skip it.


    Note This message is intended to read, "...is not allowed to be used..." 

     

  • When you edit nested task sequences, changes that you make in a child task sequence are not automatically reflected in the parent task sequence.

     

  • Task sequences may hang and return a status of “Installing” in Software Center on a client. This issue occurs if there is insufficient space in the Configuration Manager client cache, and the currently cached content is 24 hours old or newer.

     

  • Content may not distribute to a cloud-based distribution point if the package contains several hundred files (for example, an Endpoint Protection Definition Update). Additionally, the PkgXferMgr.log file contains errors entries that resemble the following:

    Caught exception System.ServiceModel.ServerTooBusyException - The HTTP service located at https://{source_url} is unavailable. This could be because the service is too busy or because no endpoint was found listening at the specified address. Please ensure that the address is correct and try accessing the service again later.

     

  • Synchronization of updates to a remote Software Update Point may be unsuccessful  if hundreds of files are being imported. For example, this issue may occur when you import Microsoft Surface drivers. Additionally, errors entries that resemble the following are recorded in the wsyncmgr.log file, and the synchronization process fails 15 minutes after it starts:

    Generic exception : ImportUpdateFromCatalogSite failed. Arg = {guid}. Error =Thread was being aborted.

     

  • The download of express installation files for Windows 10 may time out in some environments. This issue can occur when Delivery Optimization (DO) or the Background Intelligent Transfer Service (BITS) are throttled. Additionally, messages that resemble the following are recorded in the DeltaDownload.log file:

    Download timed out after 5 minutes. Cancelling download job.

     

  • Uninstall content for an application is not updated in the content library. This issue occurs if the content is modified after the original deployment type is created.

     

  • Applications may not install through a task sequence in environments that use a management point that is configured for HTTPS traffic and have a cloud management gateway enabled.

     

  • After a restart, an installation of a Windows Feature Update, such as Windows 10 Version 1803, through Windows Software Update Services (WSUS) may be reported as having failed. Error 0x80070422 is displayed in Software Center even though the operation was successful. Additionally, errors entries that resemble the following are recorded in the WUAHandler.log file:

    Failed to query IsRebootRequiredBeforeInstall property of WUA UpdateInstaller. Error = 0x80070422.

     

  • When the Add-CMDeviceCollectionDirectMembershipRule cmdlet is used to add a client resource to an existing collection, it may unexpectedly remove nested Include or Exclude membership rules. This causes the collection to contain incorrect clients.

     

  • After you upgrade to Configuration Manager current branch, version 1802, the Export-CMDriverPackage cmdlet may not correctly generate the expected driver package.

     

  • The New-CMCloudDistributionPoint cmdlet may be unsuccessful, and you receive errors messages that resemble the following:

    The WriteObject and WriteError methods cannot be called from outside the overrides of the BeginProcessing, ProcessRecord, and EndProcessing methods, and they can only be called from within the same thread.

     

  • The New-CMCloudManagementGateway cmdlet may be unsuccessful, and you receive errors messages that resemble the following:

    Operation is not valid due to the current state of the object.

     

  • The New-CMBootableMedia cmdlet does not create valid subfolders. Additionally, the CreateTSMedia.log file contains errors entries that resemble the following:

    Output directory “C:\\Folder1\\Folder2\” does not exist.

     

  • After you connect to a client through a Remote Control session and you the Keyboard Translation feature enabled, the language bar on the client is no longer visible. It can be restored after you log off and back on, or by making a change to the keyboard language through Control Panel.

     

  • The Endpoint Protection Client does not install on Windows 10 ARM-based devices.

Additional hotfixes included in this update rollup

4295281 Internet-based Configuration Manager clients can't scan for updates after upgrade to Configuration Manager current branch, version 1802

Update information for System Center Configuration Manager, version 1802

This update is available for installation in the Updates and Servicing node of the Configuration Manager console.

Restart information

You do not have to restart the computer after you apply this update.

Update replacement information

This update replaces previously released update KB 4132447. For first wave customers, after this update rollup is applied, update KB 4132447 may still appear in the Updates and Servicing node with a state of “Ready to Install”. This can be safely ignored.

Known issues for first wave customers

First wave customers who installed this update before June 14, 2018, without first applying update 4132447 are unable to upgrade the Configuration Manager console. Error entries that resemble the following are recorded in the AdminUI.ExtensionInstaller.log:

AdminUI.ExtensionInstaller.exe Warning: 0 : Downloaded file does NOT match Hash, delete the file.
AdminUI.ExtensionInstaller.exe Error: 0 : Microsoft.ConfigurationManagement.ManagementProvider.SmsException\r\nDownloaded file does NOT pass Hash validation.

This issue does not occur for customers who download and install this update rollup on or after June 14, 2018. 

To resolve this issue, manually update the Configuration Manager console installation file (AdminConsole.msi). To do this, follow these steps:

  1. Verify that update 4132447 is listed in the “Ready to install” state in the Updates and Servicing node of the Configuration Manager console. If KB 4132447 is not listed, select Check for Updates. For service connection points in Offline mode, download and then import the update by using the service connection tool.

  2. Copy the <SMSROOT>\EasySetupPayload\b15738e1-039c-4769-91d2-3043fba4e579\smssetup\bin\i386\AdminConsole.msi file to the following locations:

    • <SMSRoot>\bin\i386\AdminConsole.msi

    • <SMSRoot>\tools\ConsoleSetup\AdminConsole.msi

Other considerations

If the service connection point is in Offline mode, you must reimport the update so that it is listed in the Configuration Manager console. For more information, see Install in-console updates for System Center Configuration Manager.

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')


Notes

  • If a value of 1 is returned, the site is up-to-date, with all the hotfixes applied on its parent primary site.

  • If a value of 0 is returned, the site does not have all the fixes that were applied to the primary site installed. In this case, you should use the Recover Secondary Site option to update the secondary site.

File information

The English version of this update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

 For System Center Configuration Manager current branch, version 1802

File name

File version

File size

Date

Time

Platform

Adminui.clientagentsettings.dll

5.1802.1082.1807

1,103,232

01-May-2018

02:35

x86

Adminui.createdt.dll

5.1802.1082.1807

1,357,696

01-May-2018

02:35

x86

Adminui.ps.collections.dll

5.1802.1082.1807

195,456

01-May-2018

02:35

x86

Adminui.ps.content.dll

5.1802.1082.1807

66,432

01-May-2018

02:35

x86

Adminui.ps.hs.dll

5.1802.1082.1807

705,920

01-May-2018

02:35

x86

Adminui.ps.osd.dll

5.1802.1082.1807

657,280

01-May-2018

02:35

x86

Baseobj.dll

5.0.8634.1813

2,355,072

01-May-2018

02:35

x64

Basesvr.dll

5.0.8634.1813

4,032,896

01-May-2018

02:35

x64

Baseutil.dll

5.0.8634.1813

1,514,880

01-May-2018

02:35

x64

Bgbclientendpoint.dll

5.0.8634.1813

425,344

01-May-2018

02:35

x64

Ccmctm.dll

5.0.8634.1813

1,387,904

01-May-2018

02:35

x64

Ccmexec.exe

5.0.8634.1813

2,180,480

01-May-2018

02:35

x64

Ccmhttp.dll

5.0.8634.1813

382,848

01-May-2018

02:35

x64

Ccmid.dll

5.0.8634.1813

569,728

01-May-2018

02:35

x64

Ccmsetup-sup.cab

Not applicable

980,215

01-May-2018

02:35

Not applicable

Ccmsetup.cab

Not applicable

9,519

16-Mar-2018

18:10

Not applicable

Ccmsetup.exe

5.0.8634.1813

4,656,816

01-May-2018

02:35

x64

Ccmsetup.sdp

Not applicable

2,445

01-May-2018

02:35

Not applicable

Ccmsetupactioni.dll

5.0.8634.1813

1,241,984

01-May-2018

02:35

x64

Ccmutillib.dll

5.0.8634.1813

1,255,808

01-May-2018

02:35

x64

Client.msi

Not applicable

45,260,800

01-May-2018

02:35

Not applicable

Cmupdate.exe

5.0.8634.1813

21,959,552

01-May-2018

02:35

x64

Createmedia.exe

5.0.8634.1813

671,104

01-May-2018

02:35

x64

Createtsmediaadm.dll

5.0.8634.1813

6,624,128

01-May-2018

02:35

x64

Deltadownload.dll

5.0.8634.1813

310,656

01-May-2018

02:35

x64

Dwss.msi

Not applicable

11,206,656

01-May-2018

02:35

Not applicable

Endpointprotectionendpoint.dll

5.0.8634.1813

564,608

01-May-2018

02:35

x64

Execmgr.dll

5.0.8634.1813

1,329,536

01-May-2018

02:35

x64

Exportcontent.dll

5.0.8634.1813

4,329,856

01-May-2018

02:35

x64

Extractcontent.exe

5.0.8634.1813

4,536,704

01-May-2018

02:35

x64

Hman.dll

5.0.8634.1813

1,063,808

01-May-2018

02:35

x64

Lsinterface.dll

5.0.8634.1813

622,464

01-May-2018

02:35

x64

Lsutilities.dll

5.0.8634.1813

1,122,688

01-May-2018

02:35

x64

Managementinsightrules.resx

Not applicable

15,049

01-May-2018

02:35

Not applicable

Mcs.msi

Not applicable

15,056,896

01-May-2018

02:35

Not applicable

Microsoft.configmgrdatawarehouse.exe

5.0.8634.1813

677,760

01-May-2018

02:35

x86

Microsoft.configurationmanagement.migrationmanager.dll

5.0.8634.1813

938,880

01-May-2018

02:35

x86

Microsoft.configurationmanager.azuremanagement.dll

5.1802.1052.1004

121,216

01-May-2018

02:35

x86

Microsoft.configurationmanager.azureroles.contentmanager.dll

5.0.8634.1813

43,904

01-May-2018

02:35

x86

Microsoft.configurationmanager.cloudbase.dll

5.1802.1052.1004

86,912

01-May-2018

02:35

x86

Microsoft.configurationmanager.cloudconnection.proxyconnector.dll

5.0.8634.1813

88,960

01-May-2018

02:35

x86

Mp.msi

Not applicable

19,537,920

01-May-2018

02:35

Not applicable

Osdbitlocker_wtg.exe

5.0.8634.1813

3,982,720

01-May-2018

02:35

x64

Osdimageproperties.dll

5.0.8634.1813

3,863,424

01-May-2018

02:35

x64

Osdsetuphook.exe

5.0.8634.1813

4,910,464

01-May-2018

02:35

x64

Patchdownloader.dll

5.0.8634.1813

153,472

01-May-2018

02:35

x64

Policypv.dll

5.0.8634.1813

969,600

01-May-2018

02:35

x64

Portlweb.msi

Not applicable

5,824,512

01-May-2018

02:35

Not applicable

Pulldp.msi

Not applicable

13,565,952

01-May-2018

02:35

Not applicable

Rdpcoresccm.dll

5.0.8540.1606

2,254,720

01-May-2018

02:35

x64

Reghandler.dll

5.0.8634.1813

325,504

01-May-2018

02:35

x64

Scripts.dll

5.0.8634.1813

198,016

01-May-2018

02:35

x64

Setupcore.dll

5.0.8634.1813

23,348,096

01-May-2018

02:35

x64

Setupwpf.exe

5.0.8634.1813

543,104

01-May-2018

02:35

x86

Setupwpf_cdlatest.exe

5.0.8634.1813

543,104

01-May-2018

02:35

x86

Sitecomp.exe

5.0.8634.1813

890,752

01-May-2018

02:35

x64

Smp.msi

Not applicable

9,515,008

01-May-2018

02:35

Not applicable

Smsdpmon.exe

5.0.8634.1813

3,698,560

01-May-2018

02:35

x64

Smsdpusage.exe

5.0.8634.1813

3,355,520

01-May-2018

02:35

x64

Smsprov.dll

5.0.8634.1813

13,991,296

01-May-2018

02:35

x64

Tokenmgr.dll

5.0.8634.1813

582,528

01-May-2018

02:35

x64

Tsagent.dll

5.0.8634.1813

333,184

01-May-2018

02:35

x64

Tscore.dll

5.0.8634.1813

3,637,120

01-May-2018

02:35

x64

Tsmbootstrap.exe

5.0.8634.1813

738,688

01-May-2018

02:35

x64

Tsmessaging.dll

5.0.8634.1813

1,703,808

01-May-2018

02:35

x64

Tsprogressui.exe

5.0.8634.1813

3,752,832

01-May-2018

02:35

x64

Update.sql

Not applicable

111,674

01-May-2018

02:35

Not applicable

Updateshandler.dll

5.0.8634.1813

1,133,440

01-May-2018

02:35

x64

Wsyncact.dll

5.0.8634.1813

87,424

01-May-2018

02:35

x86

Adminui.clientagentsettings.dll

5.1802.1082.1807

1,103,232

01-May-2018

02:35

x86

Adminui.createdt.dll

5.1802.1082.1807

1,357,696

01-May-2018

02:35

x86

Adminui.ps.collections.dll

5.1802.1082.1807

195,456

01-May-2018

02:35

x86

Adminui.ps.content.dll

5.1802.1082.1807

66,432

01-May-2018

02:35

x86

Adminui.ps.hs.dll

5.1802.1082.1807

705,920

01-May-2018

02:35

x86

Adminui.ps.osd.dll

5.1802.1082.1807

657,280

01-May-2018

02:35

x86

Baseutil.dll

5.0.8634.1813

1,050,496

01-May-2018

02:35

x86

Bgbclientendpoint.dll

5.0.8634.1813

345,472

01-May-2018

02:35

x86

Ccmctm.dll

5.0.8634.1813

1,110,912

01-May-2018

02:35

x86

Ccmexec.exe

5.0.8634.1813

1,634,688

01-May-2018

02:35

x86

Ccmhttp.dll

5.0.8634.1813

321,408

01-May-2018

02:35

x86

Ccmid.dll

5.0.8634.1813

454,528

01-May-2018

02:35

x86

Ccmsetup-sup.cab

Not applicable

980,215

01-May-2018

02:35

Not applicable

Ccmsetup.exe

5.0.8634.1813

4,656,816

01-May-2018

02:35

x64

Ccmsetup.msi

Not applicable

5,079,040

01-May-2018

02:35

Not applicable

Ccmsetup.sdp

Not applicable

2,445

01-May-2018

02:35

Not applicable

Ccmsetupactioni.dll

5.0.8634.1813

1,040,256

01-May-2018

02:35

x86

Ccmutillib.dll

5.0.8634.1813

1,015,680

01-May-2018

02:35

x86

Client.msi

Not applicable

37,670,912

01-May-2018

02:35

Not applicable

Createmedia.exe

5.0.8634.1813

601,984

01-May-2018

02:35

x86

Createtsmediaadm.dll

5.0.8634.1813

5,339,008

01-May-2018

02:35

x86

Deltadownload.dll

5.0.8634.1813

251,776

01-May-2018

02:35

x86

Endpointprotectionendpoint.dll

5.0.8634.1813

438,144

01-May-2018

02:35

x86

Execmgr.dll

5.0.8634.1813

1,050,496

01-May-2018

02:35

x86

Exportcontent.dll

5.0.8634.1813

3,507,072

01-May-2018

02:35

x86

Extractcontent.exe

5.0.8634.1813

3,648,384

01-May-2018

02:35

x86

Lsinterface.dll

5.0.8634.1813

491,904

01-May-2018

02:35

x86

Lsutilities.dll

5.0.8634.1813

884,608

01-May-2018

02:35

x86

Microsoft.configurationmanager.azuremanagement.dll

5.1802.1052.1004

121,216

01-May-2018

02:35

x86

Microsoft.configurationmanager.azureroles.contentmanager.dll

5.0.8634.1813

43,904

01-May-2018

02:35

x86

Microsoft.configurationmanager.cloudbase.dll

5.1802.1052.1004

86,912

01-May-2018

02:35

x86

Osdbitlocker_wtg.exe

5.0.8634.1813

3,251,584

01-May-2018

02:35

x86

Osdimageproperties.dll

5.0.8634.1813

3,175,808

01-May-2018

02:35

x86

Osdsetuphook.exe

5.0.8634.1813

3,948,416

01-May-2018

02:35

x86

Patchdownloader.dll

5.0.8634.1813

114,048

01-May-2018

02:35

Not applicable

Pulldp.msi

Not applicable

10,940,416

01-May-2018

02:35

Not applicable

Rdpcoresccm.dll

5.0.8540.1606

1,894,272

01-May-2018

02:35

x86

Scripts.dll

5.0.8634.1813

155,008

01-May-2018

02:35

x86

Smsdpmon.exe

5.0.8634.1813

2,961,792

01-May-2018

02:35

x86

Smsdpusage.exe

5.0.8634.1813

2,665,344

01-May-2018

02:35

x86

Tsagent.dll

5.0.8634.1813

272,768

01-May-2018

02:35

x86

Tscore.dll

5.0.8634.1813

2,819,968

01-May-2018

02:35

x86

Tsmbootstrap.exe

5.0.8634.1813

596,352

01-May-2018

02:35

x86

Tsmessaging.dll

5.0.8634.1813

1,206,144

01-May-2018

02:35

x86

Tsprogressui.exe

5.0.8634.1813

3,074,944

01-May-2018

02:35

x86

Updateshandler.dll

5.0.8634.1813

853,376

01-May-2018

02:35

x86

References

What’s new in version 1802 of System Center Configuration Manager

Updates for System Center Configuration Manager

Learn about the terminology Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×