Description of Update Rollup 1 for System Center Configuration Manager current branch, version 1606

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


This article describes the issues that are fixed and the functionality that is updated in Update Rollup 1 for Microsoft System Center Configuration Manager current branch, version 1606.

Issues that are fixed

Administrator Console

  • The System Architecture section of the Choose Updates pane in the Schedule Updates Wizard incorrectly shows x86 as the platform instead of x64.

Updates and servicing

  • Update packages installed through the Updates and Servicing node of the console show a status of "In progress" for installation when there are no redistributable files to validate.


  • Software center incorrectly displays a status of Waiting to install when it should display "Waiting for next available maintenance schedule."
  • Clients installed through Configuration Manager Operating System deployment may take longer than expected to start to install device-targeted deployments. This issue occurs if the SMS Agent Host (ccmexec.exe) restarts after installation while policy data is being downloaded. Messages that resemble the following are recorded in the PolicyAgent.log file on the client:
    Policy [...]is pointing to invalid DTS job [{GUID}]. Will attempt to re-download

  • Configuration Manager Clients installed on Windows Embedded POS Ready 2009 computers cannot download content for application deployments. Errors that resemble the following are recorded in the ExecMgr.log file on the client:
    CoCreateInstance ContentAccessService failed 0x80040154

  • Inventory data that is received from a Mac client computer may not be processed as expected on the site server. This issue occurs when the inventory data contains an unexpected carriage return. Additionally, error messages that resemble the following are logged in the SMS_DM.log file, even though the client certificate is correct:
    An existing device CN=User_name needs to re-register.

Software updates

  • Attempts to service a server group (cluster patching) on a child primary site that has a remote management point result in errors. Error messages that resemble the following are logged in the MP_ClientID.log file:
    CMPDBConnection::ExecuteSQL(): ICommandText::Execute() failed with 0x80040E09
    MPDB Method : ExecuteSP()
    MPDB Method HRESULT : 0x80040E09
    Error Description : The EXECUTE permission was denied on the object 'spGetLockState', database 'CM_PRI', schema 'dbo'.

  • A software update group that contains Microsoft Office updates may not always replicate to a secondary site. Messages that resemble the following are recorded in the PkgXferMgr.log file on the site server:
    Invalid object name 'v_UpdateContents'

    Note This issue only affects the delta replication of Office updates.

Site Systems

  • Inventory views are not updated to reflect the removal of applications uninstalled from mobile devices.

Operating System Deployment

  • Task sequences that contain the Install Software Update step cannot be imported in Configuration Manager, version 1606. Additionally, you receive an error message that resembles the following, and the error is recorded in the SMSAdminUI.log file:
    Object reference not set to an instance of an object.

  • The Install Application task sequence step, when it is applied to pre-staged media, downloads content from a distribution point instead of using the content that is stored on the media. This issue increases the time for task sequence execution from pre-staged media.

Microsoft Store for Business

  • Offline license information for Microsoft Store for Business applications is not replicated in a Configuration Manager hierarchy.
  • When you click the Content Status link for the deployment of an online Microsoft Store for Business application, you receive the following error message in the Administrator Console:

  • Not all expected applications are synchronized during synchronization of applications from the Microsoft Store for Business. Errors that resemble the following are recorded in the WsfbSyncWorker.log file:
    There was a problem with the configuration for Microsoft Store for Business.
    Exception: [System.ArgumentException: Content location does not exist or user does not have access.

  • The Create Date field in the Administrator Console is empty for Online Microsoft Store for Business applications.

Software distribution and content management

  • Redistributing a package to a remote distribution point at a secondary site results in all distribution points for that site receiving the package. This issue occurs when the secondary site was recovered, and the original database was lost.
  • The OK button is unavailable (appears dimmed) in the Windows App Package Browser window of the Create Application Wizard. This prevents administrators from browsing in order to select applications in the Microsoft Store.

Endpoint Protection

  • .EPP files remain in the \\process folder after all files are successfully processed into the database. Additionally, errors that resemble the following are recorded in the EPMgr.log file on the site server:
    Failed to check if file \\?\E:\Microsoft Configuration Manager\inboxes\\process\\mi26ckw8.EPP exists with error 123

  • The Windows Defender Advanced Threat Protection feature incorrectly requires consent to use, even though it is not a pre-release feature.

Additional changes included in this update

  • Windows Server 2016 is now available in the supported platform list for Content Distribution, Software Update Management, and Settings Management.
  • The following fix is included in this update rollup:
    3184153 Can't create, edit, or delete rules for a compliance policy in System Center Configuration Manager version 1606

Update information for System Center Configuration Manager, version 1606

This update 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 details.

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

When the return is 1, the site is up to date with all the hotfixes applied on its parent primary site.

When the return is 0, 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.

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.


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

Learn about the terminology Microsoft uses to describe software updates.