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.
  ----------------------------
  
  Please note that you may experience a full sync of AD for the first time after installing this update rollup. This will cause a slow sync for first time only and the optimizations will come into action for subsequent sync cycles.
  
  [Updates May 25th, 2015]
  • You will need to install SCSM2012R2_OD_KB3064088_AMD64_7.5.3079.402.exe on your primary management server, after deploying the Update Rollup 6. Please refer the "Installation Instructions" section below.
  • Following bug fix is withdrawn from Update Rollup 6 -
    "During execution of the AD connector, the Console may experience a significant decrease in performance because the AD connector performs a full sync after every domain controller failover."
  ----------------------------
  
  
  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 three executable files available:
  SCSM2012R2_CU_KB3039363_AMD64_7.5.3079.367.exe
  SCSM2012R2_CU_KB3039363_i386_7.5.3079.367.exe
  SCSM2012R2_OD_KB3064088_AMD64_7.5.3079.402.exe
  
  Note: The System Center 2012 R2 Service Manager Update Rollups are cumulative, hence this UR6 contains new payload for the following updates along with the content shipped with System Center 2012 R2 Service Manager UR5, UR4, UR3, and UR2.
  
  Update highlights
  
  • Service Manager 2012 R2 now supports SQL Server 2014.
  • This update contains several improvements for a significant reduction in sync time of the System Center Configuration Manager (CM) connector and the Active Director (AD) connector.
  • The AD connector sync schedule has now become configurable through the console and PowerShell.
  Issues that are fixed in this update rollup
  
  • MPSync jobs hang after you import a new version of a Management Pack.
  • The AD connector group expansion workflow runs even if the corresponding connector is disabled.
  • [Withdrawn]During execution of the AD connector, the Console may experience a significant decrease in performance because the AD connector performs a full sync after every domain controller failover.
  • AD connector sync fetches the same Tombstone objects multiple times, and slows down the sync if the deployment has a large number of deleted objects.
  • If you use the extended screen to open forms, the SM console continues to try to open the form window in the extended display, even when it no longer exists.
  • Service Request and Problem management forms do not save the data changes that are made after Refreshing the form.
  • The AD connector sync generates many warning events with Event ID 3305.
  • Deleting a System Center Configuration Manager connector freezes the console until all the associated Configuration items are deleted.
  • Additions are missed when the Configuration Manager database is hosted on SQL Always On and is successfully failed over to another node.
  • The Console crashes if a large amount of data or an image is pasted in the Release Request’s documentation tab.
  • Groups & Users cannot be added to a user role from a domain which is two-way selective authenticated trust with the SM Management Server’s Domain.
  • When the number of user CIs is large, the Global Operators Group takes a long time to return and spikes the memory and CPU in the SDK process.
  • EMG and TypeSpace Cache calls are slow and makes the CPU spike when there are lots of Enumerations in the Management Group.
  • An exception occurs when you click an entity of a service on the Service Component tab.
  • Creating a Request offering with Cireson SMA Connector results in an exception, after you install update rollup 4 or 5.
  • KB3045893: Data type conversion error after you install Update Rollup 5 for System Center 2012 R2 Service Manager

Files

Status: Deleted This download is no longer available on microsoft.com. The downloads below are archives provided by the Internet Archive Wayback Machine from the Microsoft Download Center prior to August 2020.

File	Size
SCSM2012R2_CU_KB3039363_AMD64_7.5.3079.367.exe SHA1: c15db356475d3394bb0a5539c4466af4a4f1215d	69.96 MB
SCSM2012R2_CU_KB3039363_i386_7.5.3079.367.exe SHA1: b88c5fab39ef99c95b63af455dbea64cfd5a0a28	69.82 MB
SCSM2012R2_OD_KB3064088_AMD64_7.5.3079.402.exe SHA1: dba2b3582e3c1fcb1be8751a7e830a17580445eb	50.39 MB

• 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_KB3039363_AMD64_7.5.3079.367.exe file or the SCSM2012R2_CU_KB3039363_i386_7.5.3079.367.exe file, and then click Run as administrator
  3. Accept the Microsoft Software License Terms, and then follow the steps in the installation wizard
  4. Disable all your AD connectors, and install SCSM2012R2_OD_KB3064088_AMD64_7.5.3079.402.exe on your primary management server
  5. Enable the AD connectors which were disabled in previous step
  
  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 (KB3064088) on Primary Management Server and as Microsoft System Center Service 2012 R2 Service Manager (KB3039363) on rest of the servers.
  
  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.