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

Applies to: System Center Configuration Manager (current branch - version 1602)


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

Issues that are fixed

Remote Control

  • The SccmRdpsystem.exe process stops running on Windows Embedded clients after you try to start Remote Control.

Site Systems

  • The version of a built-in client policy is updated incorrectly every hour. This results in additional load on clients and management points. Messages that resemble the following are recorded in the PolicyAgent.log file on the client.
    PolicyAgent.log file on the client.
    Policy state for [CCM_Policy_Policy5.PolicyID="FEC10000",PolicySource="SMS:PRI",PolicyVersion="243.00"] is currently [Active] PolicyAgent_PolicyDownload 3/15/2016 8:56:43 AM
    Policy state for [CCM_Policy_Policy5.PolicyID="FEC10000",PolicySource="SMS:PRI",PolicyVersion="244.00"] is currently [Active] PolicyAgent_PolicyDownload 3/15/2016 9:53:57 AM
    Policy state for [CCM_Policy_Policy5.PolicyID="FEC10000",PolicySource="SMS:PRI",PolicyVersion="245.00"] is currently [Active] PolicyAgent_PolicyDownload 3/15/2016 11:28:25 AM

    Note The PolicyID references "FEC1000" and the version will update hourly.

  • The SMS Executive service may terminate unexpectedly if there is an error condition within the Exchange Connector component. Event ID 1026 is recorded in the application event log of the site server, with exception details that resemble the following.

    Note The following example is truncated for readability.
    Exception Info: System.AccessViolationException
    at Microsoft.ConfigurationManager.ExchangeConnector.NativeMethods.EasLog(System.String)
    at Microsoft.ConfigurationManager.ExchangeConnector.NativeMethods.EasLog(System.String)
    at Microsoft.ConfigurationManager.ExchangeConnector.MyTraceListener.TraceEvent(System.Diagnostics.TraceEventCache, System.String, System.Diagnostics.TraceEventType, Int32, System.String)
    at System.Diagnostics.TraceSource.TraceEvent(System.Diagnostics.TraceEventType, Int32, System.String)
    at Microsoft.ConfigurationManager.ExchangeConnector.Connector.HostedDiscovery()
    at Microsoft.ConfigurationManager.ExchangeConnector.Connector.Discovery()

  • The DBSchemaChangeHistory table in the site database grows excessively because of incorrectly reported changes.

    Note Administrators can use the sample SQL script, DBSchemaChangeHistory_cleanup, which is posted to the TechNet Gallery, as a starting point for reducing the size of this table. The script truncates the table on secondary sites and on sites where change tracking is not enabled. For other sites, records are deleted in batches to reduce replication traffic. This script is considered unsupported and is provided as an example that should be tested in a nonproduction environment first. For more information, see Support policy for manual database changes in a Configuration Manager environment .

Microsoft Intune and mobile device management

  • The Service Connection Point may take 30 minutes to recognize a newly added Intune subscription.

  • Some mobile device management actions, such as a remote wipe, can be initiated by using the incorrect certificate data. This causes those actions to fail.

  • The Service Connection Point may try to renew the wrong certificate that's used to communicate with Microsoft Intune if multiple certificates are installed that have the same expiration date.

  • An “Invalid parameter to CIM setting” message is displayed when you try to check the baseline deployment status of a custom IOS or Mac profile.

  • The SMS_DMP_Connector registry key remains after you remove a Microsoft Intune subscription. Successive attempts to add a new Microsoft Intune subscription trigger authentication errors.

Hotfix information for System Center Configuration Manager, version 1602

This hotfix is available for installation in the Updates and Servicing node of the Configuration Manager console. If the service connection point is in offline mode, you have to re-import the update so that it is listed in the Configuration Manager console. Refer to Install Updates for System Center Configuration Manager for additional detail.

Installation information

Be aware that this update does not currently apply to secondary sites.

Installation notes

After you install this update rollup, the client versions in both pre-production and production may roll back to Configuration Manager version 1511, build 8325.1000. This occurs when the following conditions are true:
  • The Validate in pre-production collection setting is selected under Client Update Options when you upgrade from Configuration Manager version 1511 to version 1602.
  • The 1602 client is not promoted to production, leaving the 1511 client as the production version.

This update rollup is not a full version of the client. Therefore, Hierarchy Manager will remove the rollup after it detects that it's not applicable to the 1511 client. Then, the production and pre-production clients will be synchronized back to the 1511 version. To prevent this scenario, make sure to promote the 1602 client from pre-production to production before you install this rollup.

Note This scenario does not apply to future versions of Configuration Manager, starting with version 1606.

If this installation issue occurs, the following steps can be taken to restore the 1602 client versions in the hierarchy. These steps assume a Central Administration Site (CAS) and administrative rights to the site servers. Step 1 can also apply to a stand-alone primary site. In that situation, step 4 is not required. An example script to automate steps 1-4 is available on the TechNet Gallery here.
  1. Recover the client and update files on the CAS. Language packs are recovered in step 5:
    robocopy "\\{CAS_Servername}\SMS_{CAS SiteCode}\CMUStaging\609f1263-04e0-49a8-940b-09e0e34de2d2\SMSSETUP\CLIENT" "\\{CAS_Servername}\SMS_{CAS SiteCode}\CMUClient" client.msi ccmsetup.exe ccmsetup.cab /S
    copy /y "\\{CAS_Servername}\SMS_{CAS SiteCode}\CMUStaging\609f1263-04e0-49a8-940b-09e0e34de2d2\redist\Silverlight.exe" "\\{CAS_Servername}\SMS{CAS SiteCode}\CMUClient\i386"

    robocopy "\\{CAS_Servername}\SMS_{CAS SiteCode}\CMUStaging\59BCA34E-DF87-4041-B9B7-F53395849E81\SMSSETUP\CLIENT" "\\{CAS_Servername}\SMS_{CAS SiteCode}\CMUClient" *.msp /S

    xcopy /s /y "\\{CAS_Servername}\SMS_{CAS SiteCode}\CMUClient" "\\{CAS_Servername}\SMS_{CAS SiteCode}\StagingClient"
    xcopy /s /y "\\{CAS_Servername}\SMS_{CAS SiteCode}\CMUClient" "\\{CAS_Servername}\SMS_{CAS SiteCode}\Client"

  2. Create an empty trigger file to update the client package:
    echo. 2>"\\{CAS_Servername}\SMS_{CAS SiteCode}\inboxes\hman.box\client.acu"

  3. Check the status by using the Monitoring\Overview\Client Status\Production Client Deployment node of the Administrator Console. The client version should now be 5.00.8355.1306.
  4. Recover the client files on any child primary sites by using the CAS as a source, and then create an empty trigger file to update remote management points:
    xcopy /s /y "\\{CAS_Servername}\SMS_{CAS SiteCode}\CMUClient" "\\{Primary_Servername}\SMS_{PRI SiteCode}\\Client"
    xcopy /s /y "\\{CAS_Servername}\SMS_{CAS SiteCode}\CMUClient" "\\{Primary_Servername}\SMS_{PRI SiteCode}\CMUClient"

  5. Remove and reinstall any client language packs both at the CAS and all child primary sites. For more information, see Language Packs in System Center Configuration Manager.

For more information, see How to test client upgrades in a preproduction collection in System Center Configuration Manager.

Restart information

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

Update replacement information

This hotfix does not replace any previously released hotfix.

More Information

For a summary of the changes made in System Center Configuration Manager current branch, version 1602, see the following article in the Microsoft Knowledge Base:
3168240 Summary of changes made in System Center Configuration Manager current branch, version 1602


For more information, see the Install Updates for System Center Configuration Manager (version 1602) topic on the Microsoft TechNet website.

Learn about the terminology that Microsoft uses to describe software updates.

Applies to

This article applies to the following:
  • System Center Configuration Manager current branch, version 1602