Update Rollup 9 for System Center 2012 R2 Service Manager

Applies to: System Center 2012 R2 Service ManagerSystem Center 2012 R2

[Update: February 16, 2016]

The original Update Rollup 9 (UR9) package (7.5.3079.571) was withdrawn and replaced by a new installation package (7.5.3079.607).


  • If you installed the original UR9 package (7.5.3079.571), you will notice that some unsealed management packs of your deployment were overwritten. Therefore, follow these steps:

    1. Reimport the following unsealed management packs:

      • ServiceManager.IncidentManagement.Configuration.xml
      • ServiceManager.ServiceRequest.Configuration.xml
      • ServiceManager.ProblemManagement.Configuration.xml
      • ServiceManager.KnowledgeManagement.Configuration.xml

    2. Apply the new version of UR9 (7.5.3079.607).

      Note The new update package (7.5.3079.607) is the official UR9 release. The original version (7.5.3079.571) is no longer supported.
  • If you have not installed the original UR9 package (7.5.3079.571), update your deployment directly by using only the new package (7.5.3079.607).
  • Important Version 7.5.3079.607 is the supported UR9 version. Therefore, install the new UR9 update if you have one of the old UR9 updates (version 7.5.3079.571 or 7.5.3079.601) installed.


This article describes the issues that are fixed in Update Rollup 9 for Microsoft System Center 2012 R2 Service Manager. Additionally, it contains the installation instructions for the update rollup.

Update rollups that are included in this release

System Center 2012 R2 Service Manager update rollups are cumulative. Therefore, this update rollup contains new payloads for the following updates together with the content that's included in the following System Center 2012 R2 Service Manager update rollups:
Be aware that this release does not contain the payload of Update Rollup 8 . This is because it contains the new HTML-based Self Service Portal and requires a separate installation.

Issues that are fixed in this update rollup

  • System Center Configuration Manager 1511, 1602, 1606, 1610, 1702, and 1706 are supported in this Service Manager update for Configuration Manager Connectors.
  • The AD connector goes for a full sync after you update an LDAP query through PowerShell.
  • After Update Rollup 7 is installed, you may receive the following error message when you update a work item:
    Failed to execute Submit operation. Fix the reported error before...
    The user <username> does not have sufficient permission to perform the operation.

    Error message

    The exception that's raised on simultaneous conflicting changes on the same item by multiple analysts or by analyst and workflows does not contain the details of fields and values that caused the conflict.

    After this update is installed, the raised exception contains the details of fields (and their values) that have conflicting updates. Therefore, the analyst can save the changes after the conflict is resolved.
  • The Service Manager console does not show the details about the settings that have changed and triggered a noncompliance issue for DCM incidents.
  • Runbook activity does not change the status when the associated Runboook job is removed from Orchestrator.
  • SQL CoreEnterprise64 is not detected as an enterprise edition by Service Manager.
  • After Update Rollup 7 is installed, the Active Directory connector fails and generates an InvalidCastException error.
  • After Update Rollup 7 installed, the service component is not available for some Business Services that are imported from Operations Manager.

    Note A new update for HTML Self Service Portal is also available separately. You can obtain the update here .

How to obtain and install Update Rollup 9 for System Center 2012 R2 Service Manager

Download information

Update packages for Service Manager are available from Microsoft Download Center.

Microsoft Download Center

Go to the following website to manually download the update packages from the Microsoft Download Center: