Update Rollup 4 for System Center 2012 R2 Service Manager

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

Issues that are fixed in this update rollup

  • The GUIDs for AD users get scrambled if the Automatically add users of AD Groups imported by this connector check box is selected in the Active Directory connector.

  • The Folder and View links for the work items in the central pane of the console disappear after the data warehouse management server is connected.

  • When the title of a manual activity is updated, the change is not replicated to the DisplayName field.

  • The Request Offering wizard should display only the runbook input parameters instead of displaying all properties on the activity. This behavior is limited to Orchestrator-based Runbook Automation Templates, and does not work for Service Management Automation-based runbooks.

    Note This issue is only found in GridPro.

  • Assume that a configuration item has an enumeration property that contains a value that no longer exists. When you save a template that contains the configuration item, an exception is thrown.

  • Data Warehouse Transform jobs have a hardcoded 60-minute time-out. Therefore, Data Warehouse jobs cannot be disabled for very long because the volume of data to be transformed can quickly pile up. This can cause an issue if the volume exceeds the amount that can be processed by the transform modules within the time-out period.

  • When a service request is put on hold, it might be evaluated incorrectly as being complete. This is because of a race condition between workflows.

  • When the local time zone on the computer is custom-set, you cannot create a new service level agreement (SLA) calendar and receive an error if you try.

  • Console freezes when a user tries to save changes to an existing knowledge article by clicking the Apply button.

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

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:

Download Download the update package now.

Installation instructions

Before you apply this update, follow these steps:

  1. Exit all Service Manager-related applications before you apply this cumulative 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

    5. Self-Service Portal

  4. It is important to restart all the consoles as soon as the update has installed.


To install this cumulative update, follow these steps:

  1. Download the cumulative update to a target folder. This cumulative 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_KB 2989601_AMD64_ 7.5.3079.236.exe

    • SCSM2012R2_CU_KB2989601_i386_ 7.5.3079.236.exe

  3. Click Run as administrator.

  4. Accept the Microsoft Software License Terms, and then follow the steps in the installation wizard.


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 (SCSM2012R2_CU_ KB2989601)


Resynchronize System Center Operations Manager mount point data

To resynchronize Operations Manager mount point data after you apply this update, follow these steps:

  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.ps1By 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 then 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. In the Value data box, type 1, and then click OK.

    Note The value is in seconds, and it can range from 0 to the max integer value, which is 2,147,483,647.

  7. Exit Registry Editor.


File that are updated

File Version or Date

Size (in bytes)

Microsoft.EnterpriseManagement.Core.Cmdlets.psd1

10/17/2014 09:17pm

11373

Microsoft.EnterpriseManagement.Core.dll

7.5.3079.236

4082376

Microsoft.EnterpriseManagement.DataAccessLayer.dll

7.5.3079.236

2513600

Microsoft.EnterpriseManagement.DataAccessService.Core.dll

7.5.3079.236

711360

Microsoft.EnterpriseManagement.MPImporter.dll

7.5.3079.236

20168

Microsoft.EnterpriseManagement.Reporting.Code.dll

7.5.3079.236

88768

Microsoft.EnterpriseManagement.ServiceManager.ActivityManagement.Forms.dll

7.5.3079.236

408264

Microsoft.EnterpriseManagement.ServiceManager.Application.Common.dll

7.5.3079.236

1186504

Microsoft.EnterpriseManagement.ServiceManager.Applications.ServiceCatalog.Tasks.dll

7.5.3079.236

576192

Microsoft.EnterpriseManagement.ServiceManager.Applications.ServiceRequest.Common.dll

7.5.3079.236

187072

Microsoft.EnterpriseManagement.ServiceManager.Applications.ServiceRequest.Tasks.dll

7.5.3079.236

80576

Microsoft.EnterpriseManagement.ServiceManager.Applications.ServiceRequest.Workflows.dll

7.5.3079.236

101056

Microsoft.EnterpriseManagement.ServiceManager.ChangeManagement.Presentation.dll

7.5.3079.236

92864

Microsoft.EnterpriseManagement.ServiceManager.Cmdlets.psd1

10/17/2014 09:46pm

11407

Microsoft.EnterpriseManagement.ServiceManager.Datawarehouse.dll

7.5.3079.236

248520

Microsoft.EnterpriseManagement.ServiceManager.KnowledgeManagement.Forms.dll

7.5.3079.236

215744

Microsoft.EnterpriseManagement.ServiceManager.Linking.Consumer.OperationalStore.dll

7.5.3079.236

109248

Microsoft.EnterpriseManagement.ServiceManager.OpsMgrConnector.dll

7.5.3079.236

182976

Microsoft.EnterpriseManagement.ServiceManager.ReleaseManagement.Forms.dll

7.5.3079.236

338624

Microsoft.EnterpriseManagement.ServiceManager.ReleaseManagement.Presentation.dll

7.5.3079.236

92864

Microsoft.EnterpriseManagement.ServiceManager.Sdk.dll

7.5.3079.236

293568

Microsoft.EnterpriseManagement.ServiceManager.SLA.Common.dll

7.5.3079.236

232128

Microsoft.EnterpriseManagement.ServiceManager.UI.Administration.dll

7.5.3079.236

1460928

Microsoft.EnterpriseManagement.UI.ExtendedControls.dll

7.5.6111.0

60104

Microsoft.EnterpriseManagement.UI.SdkDataAccess.dll

7.5.3079.236

1227456

Microsoft.EnterpriseManagement.UI.SMControls.dll

7.5.3079.236

1166016

Microsoft.EnterpriseManagement.Warehouse.SynchModule.dll

7.5.3079.236

154304

Microsoft.EnterpriseManagement.Warehouse.Utility.dll

7.5.3079.236

305856

Microsoft.Mom.CmdbInstanceSubscriptionDataSourceModule.dll

7.5.3079.236

330432

Microsoft.Mom.DatabaseQueryModules.dll

7.5.3079.236

223936

OMCIConnector_SyncMetadata_UpdateTimestamp.PS1

10/17/2014 09:46pm

21544

System.Center.Service.Manager.psm1

10/17/2014 09:46pm

12898




The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×