Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Description of Update Rollup 5 for System Center 2012 R2 Service Manager


View products that this article applies to.

Introduction

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

↑ Back to the top


Issues that are fixed in this update rollup

Service Manager

Note The System Center 2012 R2 Service Manager Update Rollups are cumulative. Therefore, this update rollup contains new fixes for the following issues along with fixes that were included in System Center 2012 R2 Service Manager Update Rollup 4 , Update Rollup 3 , and Update Rollup 2 .
  • Change request still stays "in progress" when last activity is skipped and all previous activities are completed.

  • ActualStartDate and ActualEndDate field values for Change Request and Release Request do not set.

  • Multiple System Center Service Manager Connectors to System Center Configuration Manager execute and complete successfully. However, the start, finish, and status property values are not updated in the Service Manager Console under the Connectors view, and event 3334 is logged.

  • Trying to delete a Service Request template that is being used by a Request Offering causes a cryptic and non-user-friendly error message.

  • The "Group By" functionality in a view does not work correctly when the Group By column has empty fields.

  • The console crashes when the user tries to open an already opened attachment from a Work Item form.

  • Opening the Views for Groups takes a long if there are a large number of explicit members in the groups.

  • The OM CI connector fails if you try to import a distributed application that contains an instance of the Hyper-V Virtual Network Adapter class.

  • Monitoring Host process crashes if there exists a notification after the user who created it was deleted or moved to a hidden organizational unit (OU) in Active Directory.

  • An exception is raised if a user tries to open a sorted view that is created by using TypeProjection on a custom class that is neither Abstract and nor a first Concrete class.

  • An exception is thrown when a user tries to open the Service Components tab on the Service Maps form when there are large number of services in CMDB.

  • Enhanced in-event logging for DW jobs.

    Logging the batch start and completion events for all DW job categories in event log. The start and completion event will include the following:
    • Process category
    • Process name
    • Batch ID
    • Batch start or completion time


  • Enhanced in event logging for DW cube processing.
    • Time taken by Cube’s batch ID to complete will be logged in seconds.
    • Information about whether the cube is processed under Analysis Services that are running in Microsoft SQL Server Standard Edition or in SQL Server Enterprise Edition.
    • Event logs will be added during processing of each Dimension and Measure Group for each partition (if applicable) for both enterprise and standard editions of SQL Server. 


  • Added the new Windows PowerShell cmdlet Get-SCDWInfraLocations on the Service Manager management server to retrieve the following location information about its data warehouse infrastructure:
    • Service Manager database
    • Service Manager data warehouse database
    • Service Manager Analysis server database
    • Data Warehouse Reporting Server database and Report Server URL


↑ Back to the top



How to obtain and install Update Rollup 5 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:


↑ Back to the top


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
    5. Self-Service Portal

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

Installation
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_KB3009517_AMD64_ 7.5.3079.315.exe
    • SCSM2012R2_CU_ KB3009517_i386_ 7.5.3079.315.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 (SCSM2012R2_CU_ KB3009517)

After the installation
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 Windows 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 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 3 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.


↑ Back to the top


Files that are updated in this update rollup
Files that are changedFile VersionFile size
Microsoft.EnterpriseManagement.Core.Cmdlets.psd1Not applicable11,373
Microsoft.EnterpriseManagement.Core.dll7.5.3079.3154,082,376
Microsoft.EnterpriseManagement.DataAccessLayer.dll7.5.3079.3152,513,600
Microsoft.EnterpriseManagement.DataAccessService.Core.dll7.5.3079.315711,360
Microsoft.EnterpriseManagement.MPImporter.dll7.5.3079.31520,168
Microsoft.EnterpriseManagement.Reporting.Code.dll7.5.3079.31588,768
Microsoft.EnterpriseManagement.ServiceManager.ActivityManagement.Forms.dll7.5.3079.315408,256
Microsoft.EnterpriseManagement.ServiceManager.Application.Common.dll7.5.3079.3151,186,496
Microsoft.EnterpriseManagement.ServiceManager.Applications.ServiceCatalog.Tasks.dll7.5.3079.315576,192
Microsoft.EnterpriseManagement.ServiceManager.Applications.ServiceRequest.Common.dll7.5.3079.315187,072
Microsoft.EnterpriseManagement.ServiceManager.Applications.ServiceRequest.Tasks.dll7.5.3079.31580,576
Microsoft.EnterpriseManagement.ServiceManager.Applications.ServiceRequest.Workflows.dll7.5.3079.315101,056
Microsoft.EnterpriseManagement.ServiceManager.ChangeManagement.Presentation.dll7.5.3079.31592,864
Microsoft.EnterpriseManagement.ServiceManager.Cmdlets.psd1Not applicable11,391
Microsoft.EnterpriseManagement.ServiceManager.Datawarehouse.dll7.5.3079.315248,512
Microsoft.EnterpriseManagement.ServiceManager.KnowledgeManagement.Forms.dll7.5.3079.315215,744
Microsoft.EnterpriseManagement.ServiceManager.Linking.Consumer.OperationalStore.dll7.5.3079.315109,248
Microsoft.EnterpriseManagement.ServiceManager.OpsMgrConnector.dll7.5.3079.315182,984
Microsoft.EnterpriseManagement.ServiceManager.ReleaseManagement.Forms.dll7.5.3079.315338,624
Microsoft.EnterpriseManagement.ServiceManager.ReleaseManagement.Presentation.dll7.5.3079.31592,864
Microsoft.EnterpriseManagement.ServiceManager.Sdk.dll7.5.3079.315293,568
Microsoft.EnterpriseManagement.ServiceManager.SLA.Common.dll7.5.3079.315232,128
Microsoft.EnterpriseManagement.ServiceManager.UI.Administration.dll7.5.3079.3151,460,928
Microsoft.EnterpriseManagement.UI.ExtendedControls.dll7.5.6111.060,104
Microsoft.EnterpriseManagement.UI.SdkDataAccess.dll7.5.3079.3151,227,464
Microsoft.EnterpriseManagement.UI.SMControls.dll7.5.3079.3151,166,024
Microsoft.EnterpriseManagement.Warehouse.SynchModule.dll7.5.3079.315154,304
Microsoft.EnterpriseManagement.Warehouse.Utility.dll7.5.3079.315314,048
Microsoft.Mom.CmdbInstanceSubscriptionDataSourceModule.dll7.5.3079.315330,432
Microsoft.Mom.DatabaseQueryModules.dll7.5.3079.315223,936
OMCIConnector_SyncMetadata_UpdateTimestamp.PS1Not applicable21,544
System.Center.Service.Manager.psm1Not applicable12,898
Microsoft.EnterpriseManagement.Warehouse.Cmdlets.dll7.5.3079.315162,496
Microsoft.EnterpriseManagement.UI.ViewFramework.dll7.5.6122.0120,008
Microsoft.EnterpriseManagement.Core.SdkUtilities.dll7.5.3079.315133,824
SCMsgs.dll7.5.3079.315121,544
Microsoft.EnterpriseManagement.ServiceManager.ChangeManagement.Workflows.dll7.5.3079.315185,728
Microsoft.EnterpriseManagement.ServiceManager.ReleaseManagement.Workflows.dll7.5.3079.31584,672
Microsoft.EnterpriseManagement.ServiceManager.Connector.DataCenter.dll7.5.3079.315150,208
Microsoft.EnterpriseManagement.Orchestration.dll7.5.3079.315133,824
Microsoft.EnterpriseManagement.Warehouse.Olap.dll7.5.3079.315207,560
TraceScenarios.cabNot applicable11,599

↑ Back to the top


Keywords: kbnotautohotfix, kbfix, kbqfe, kbexpertiseinter, kbsurveynew, atdownload, kb

↑ Back to the top

Article Info
Article ID : 3009517
Revision : 1
Created on : 1/7/2017
Published on : 4/23/2015
Exists online : False
Views : 350