Legacy Update: Get back online, activate, and install updates on your legacy Windows PC

This update contains a number of fixes for System Center 2012 R2 Service Manager

• [Update]
  Note: Update Rollup 9 for Service Manager 2012 R2 is now available for download, you can get it from here - http://aka.ms/smr2ur9
  
  The Service Manager update rollups are cumulative, UR9 contains new updates in addition to all the payload which was shipped in UR7,UR6, UR5, UR4, UR3, and UR2. You can directly patch SM 2012 R2 deployment with UR9 to get all the fixes together.Please be aware that UR9 release does not contain the payload of Update Rollup 8 (https://support.microsoft.com/kb/3124091), because UR8 contains the new HTML based Self Service Portal and requires separate installation.
  
  Hence, now we are removing the Update Rollup 5 files from this Download Center page and those files will be available for on-demand in special cases only. Feel free to reach us at [email protected] in case of any queries or concerns.
  ----------------------------
  
  [Update - March 16th, 2015]
  Note: After installing this update, you may experience the following issue:
  
  If your Data Warehouse server does not use Month-Date-Year time format, then an event “The conversion of a nvarchar data type to a datetime data type resulted in an out-of-range value” is logged in your Service Manager Data Warehouse, and the Extract job no longer runs.
  
  A hotfix for this problem is now available. If you are facing this issue, then you can download the hotfix from here.
  -----------------------------------
  
  This update contains a set of bug fixes to the System Center 2012 R2 Service Manager release. It should be applied to all Service Manager 2012 R2 server installations.
  There are two executable files available:
  SCSM2012R2_CU_KB3009517_AMD64_7.5.3079.315.exe
  SCSM2012R2_CU_KB3009517_i386_7.5.3079.315.exe
  
  Bug fixes included in this update:
  Note: The System Center 2012 R2 Service Manager Update Rollups are cumulative, hence this UR5 contains new fixes for the following issues along with fixes shipped with System Center 2012 R2 Service Manager UR4, UR3, and UR2.
  
  1. Change request still stays "in progress" when last activity is skipped and all previous activities are completed.
  2. ActualStartDate and ActualEndDate field values for Change Request and Release Request do not set.
  3. 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.
  4. Trying to delete a Service Request template that is being used by a Request Offering causes a cryptic and non-user friendly error message.
  5. The "Group By" functionality in a View does not work correctly when "Group By" column has empty fields.
  6. The Console crashes when the user tries to open an already opened attachment from a Work Item form.
  7. Opening the Views for Groups takes a long if there are large number of explicit members in the groups.
  8. The OM CI connector fails if one tries to import a distributed application that contains an instance of the 'Hyper-V Virtual Network Adapter' class.
  9. Monitoring Host process crashes if there exists a Notification after the user who created it was deleted or has moved to a hidden organizational unit (OU) in the Active Directory.
  10. An exception is raised if the user tries to open a sorted View which is created by using TypeProjection on custom Class that is neither Abstract and nor a first Concrete class.
  11. 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.
  12. 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
      1. Process Name
      2. Batch Id
      3. Batch Start or completion Time
  13. Enhanced in event logging for DW cube processing.
      1. Time taken by Cube’s batch id to complete will be logged in seconds.
      2. Information whether the cube is processed under Analysis Services that are running in SQL Server Standard Edition or the SQL Server Enterprise Edition.
      3. Event logs will be added during processing of each Dimension and Measure Group for each partition (if applicable) for both enterprise and standard SQL editions.
  14. Added a new PowerShell cmdlet Get-SCDWInfraLocations Cmdlet on the Service Manager management server to retrieve the following location information about its data warehouse infrastructure:
      1. Service Manager database
      2. Service Manager data warehouse database
      3. Service Manager Analysis server database
      4. Data Warehouse Reporting Server database and Report Server URL

Files

Status: Live This download is still available on microsoft.com. The downloads below will come directly from the Microsoft Download Center.

File	Size
Readme - UR9 now available.docx SHA1: b979e578a5b69bbb272f78b99f92bd8d2ade6767	11 KB

File sizes and hashes are retrieved from the Wayback Machine’s indexes. They may not match the latest versions of files hosted on Microsoft servers.

• System Center 2012 R2 Service Manager

• Before you update:
  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. Ensure that the Data Warehouse Server has successfully synchronized with the Management Server at least once
  3. Ensure that the update is first installed on Service Manager components in the following order:
     1. DataWarehouse 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 once the update has been 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 version and the x64 version. Download the appropriate version for your system.
  2. Open the target folder and right-click the SCSM2012R2_CU_KB3009517_AMD64_7.5.3079.315.exe file or the SCSM2012R2_CU_KB3009517_i386_7.5.3079.315.exe file, and then click Run as administrator
  3. Accept the Microsoft Software License Terms, and then follow the steps in the installation wizard
  
  How to verify a successful installation of this cumulative update
  1. In Control Panel, open Programs and Features.
  2. Click View installed updates.
  3. The following item is listed: Hotfix for Microsoft System Center Service 2012 R2 Service Manager (KB3009517)
  
  Steps to be followed post application of the UR to resynchronize SCOM (Operations Manager) mount points data:
  1. Disable all the OM CI Connector(s) in SM console
  2. In Windows PowerShell, check the current execution policy by executing "Get-ExecutionPolicy"
  3. If the current execution policy is Restricted then set to Remotesigned by executing "Set-ExecutionPolicy –force RemoteSigned"
  4. Find the PowerShell script "OMCIConnector_SyncMetadata_UpdateTimestamp.ps1" in your System Center 2012 R2 installation directory. You should get this file under "Microsoft System Center 2012 R2\Service Manager\PowerShell".
  5. Execute "PowerShell .\OMCIConnector_SyncMetadata_UpdateTimestamp.ps1" from Primary Management server
  6. Change the execution policy back to the value that you noted in step 2
  7. Enable and Synchronize the relevant OM CI Connector(s)
  8. All the Mount Points data should be populated in SCSM
  
  　Steps to be followed post application of the UR to configure the timeout period for DataWarehouse Transform jobs:
  With this Update Rollup, the timeout for DataWarehouse Transform jobs is now configurable with the Windows registry. Also now the default timeout has increased to 3 hours (180 minutes).
  
  To override this, create
  1. Key is under "SOFTWARE\Microsoft\System Center\2010\Common\DAL" and the name should be "SqlCommandTimeout" of type DWORD
  2. The value is in seconds and can vary from 0 up to the max integer value, which is 2,147,483,647.