Update Rollup 9 for System Center 2012 R2 Service Manager

[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, and 1606 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:

Installation instructions

Before the installation

Before you apply this update, follow these steps:

  1. Exit all Service Manager-related applications before you apply this update. For example, exit the Service Manager Console, the Self-Service Portal links, and the authoring tool.
  2. Make sure that the Data Warehouse Server has successfully synchronized with the Management Server at least one time.
  3. Make sure that the update is installed on the Service Manager components in the following order:

    1. Data Warehouse Server
    2. Primary Management Server
    3. Secondary Management Servers
    4. All analyst consoles

Important Restart all the consoles as soon as the update is installed.


To install this update, follow these steps:

  1. Download the update to a target folder. This update contains both the x86-based version and the x64-based version. Download the appropriate version for your system.
  2. Open the target folder, and then right-click one of the following files:

    • SCSM2012R2_CU_KB3129780_AMD64_ 7.5.3079.607.exe
    • SCSM2012R2_CU_ KB3129780_i386_ 7.5.3079.607.exe
  3. Click Run as administrator.
  4. Accept the Microsoft Software License Terms, and then follow the steps in the installation wizard.

Verify the installation

To verify the successful installation of this update, follow these steps:

  1. In Control Panel, open Programs and Features.
  2. Click View Installed Updates.
  3. If the following item is listed, the installation succeeded:

    Hotfix for Microsoft System Center Service Manager (KB3129780)

After the installation

To fix the existing incidents in Configuration Manager database that are throwing insufficient permission issues while trying to update them

This issue occurs when any incident has multiple billable item objects associated with it. Therefore, you must prune the extra objects to fix the already affected Incidents. The "RemoveDuplicateBillableItem.ps1" PowerShell script (included in downloads) can help you do this.

Run the PowerShell script on a computer that has the Service Manager Console or the Management Server installed on it.

Note We recommend that you run the script during off hours, as the script may hinder performance during operational hours.

The script expects three parameters in the following format:

.\RemoveDuplicateBillableItem.ps1 <UpdateDB-flag> <SumorMax-flag> <DateArgument>

UpdateDB-flagThis flag helps you select between only viewing the list of affected incidents and fixing (updating) the incidents.0: To view the list of affected incidents

1: To fix (update) the affected incidents
SumorMax-flagBecause this issue is caused by duplicate billable items that exist in an incident, you must remove the multiple bill entries and should keep only one.

This flag helps you select whether to keep only the maximum value out of all recorded billable times or keep a sum of all items.
0: Merges all the billable items into one as a Sum of all

1: Keeps only the billable item that has the Maximum value and removes all other items
DateArgument (optional)This parameter helps to control the incidents that are processed by this script.

The script processes only those incidents that are changed after the provided date-time (UTC value).
This optional parameter expects a date in "mm/dd/yyyy hh:mm" (UTC value) format.

By default, if no value is provided, the parameter picks the value as "07/28/2015 07:00" (UR7 release date).

For example, to obtain a list of all affected incidents modified after 1st December 2015, 5 PM (UTC), run the following script command:

.\RemoveDuplicateBillableItem.ps1 0 0 "12/01/2015 17:00"

Or, to obtain the fix (update) of all affected incidents modified after 1st December 2015, 5 PM (UTC), run the following script command:

  • To merge all the billable items into one item as a Sum of all, run the following script command:

    .\RemoveDuplicateBillableItem.ps1 1 0 "12/01/2015 17:00"

  • Or, to keep only the billable item with Maximum value and remove others, run the following script command:

    .\RemoveDuplicateBillableItem.ps1 1 1 "12/01/2015 17:00"

To resynchronize Operations Manager mount point data after you apply this update

  1. Disable all the Operations Manager configuration item (CI) connectors in the Service Manager console.
  2. In Windows PowerShell, check the current execution policy by running the following cmdlet:

  3. If the current execution policy is Restricted, set it to Remotesigned by running the following command:

    Set-ExecutionPolicy –force RemoteSigned

  4. Find the following PowerShell script in your System Center 2012 R2 installation directory:


    By default, you should find this file in the following location:

    C:\Program Files\Microsoft System Center 2012 R2\Service Manager\PowerShell
  5. Run the following command from the Primary Management server:

    PowerShell .\OMCIConnector_SyncMetadata_UpdateTimestamp.ps1
  6. Revert the execution policy to the original value that it had in step 2.
  7. Enable and synchronize the relevant Operations Manager CI connectors.
  8. Make sure that all the mount point data is populated in Service Manager.

Configure the time-out period for Data Warehouse Transform jobs
Important Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.

After you apply this update, the time-out for Data Warehouse Transform jobs is now configurable with the Windows registry. Also, the default time-out is increased to three hours (180 minutes). To override this, follow these steps:

  1. Click Start, click Run, type regedit in the Open box, and then click OK.
  2. Locate and select the following registry subkey:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\System Center\2010\Common\DAL
  3. On the Edit menu, point to New, and then click DWORD (32-bit) Value.
  4. Type SqlCommandTimeout, and then press Enter.
  5. In the Details pane, right-click SqlCommandTimeout, and then click Modify.
  6. Under Base, choose Decimal. In the Value data box, type the value in seconds that you want to use, and then click OK.

    Note This value is measured in seconds. It can range from 0 to the maximum integer value of 2,147,483,647.

  7. Exit Registry Editor.

Files updated in this update rollup

FileFile Version or DateSize (in bytes)
Microsoft.EnterpriseManagement.Core.Cmdlets.psd114-May-2015 00:051587
Microsoft.EnterpriseManagement.ServiceManager.Cmdlets.psd114-May-2015 00:071605
OMCIConnector_SyncMetadata_UpdateTimestamp.PS114-May-2015 00:0711742
System.Center.Service.Manager.psm114-May-2015 00:073112

Article ID: 3129780 - Last Review: 09/08/2016 11:12:00 - Revision: 14.0

Microsoft System Center 2012 R2 Service Manager, Microsoft System Center 2012 R2

  • kbqfe kbsurveynew kbfix kbexpertiseinter atdownload KB3129780