Update Rollup 9 for System Center 2012 R2 Service Manager

Before the installationBefore 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.

InstallationTo 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 installationTo 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 installationTo 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>

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:
   
   

   Get-ExecutionPolicy

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:
   
   

   OMCIConnector_SyncMetadata_UpdateTimestamp.ps1
   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 jobsImportant 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.