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.
  ----------------------------
  
  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 the available executable files:
  SCSM2012R2_CU_KB3063263_AMD64_ 7.5.3079.442.exe
  SCSM2012R2_CU_ KB3063263_i386_ 7.5.3079.442.exe
  SCSM2012R2_OD_KB3099983_AMD64_7.5.3079.504.exe
  
  Note: The System Center 2012 R2 Service Manager Update Rollups are cumulative, hence this UR7 contains new payload for the following updates along with the content shipped with System Center 2012 R2 Service Manager UR6, UR5, UR4, UR3, and UR2.
  
  Issues that are fixed in this update rollup
  
  • Service Manager does not let users save any changes in a form, and the user receives an error message saying "The item cannot be updates because it has been changed by another user or process.". This issue occurs if any workflow or another user has made changes to same item at the same time. With this update rollup installed, Service Manager will let the items to be saved successfully in case of nonconflicting disjoint changes. To read more about this update, click here.
  • Employee-Manager relationship is not established when both the users are imported through different Active Directory connectors.
  • MPSync Data Warehouse job stops responding very frequently because deployer jobs in Data Warehouse try to re-create already existing Primary & Foreign keys.
  • During execution of the Active Directory connector, the Console may experience a significant decrease in performance because the Active Directory connector performs a full sync after every Domain Controller failover. With this update installed, the Active Directory connector should sync only those items which have changed after a previous sync, including after a Domain Controller failover.
  • If a user changes from having a manager in Active Directory not to having a manager, the relationship is not removed or updated in the configuration management database (CMDB).
  • The Get-SCDWInfraLocations cmdlet (included in Update Rollup 5) is improved to support Automation and all PowerShell standards including the following:
    • Now it is renamed to “Get-SCDWInfraLocation” – It was done to make it follow powershell naming convention standards.
    • Originally it expected “DWServer” parameter but now it was removed. Now it accepts the same parameters as other DW Cmdlets and parameter “ComputerName” can be used to pass DW Server name. and the parameter “Credential” is used for passing Credentials to log on to the DW Server. These parameters are same across most of the DW Cmdlets.
    • Now it returns an object to Powershell pipeline instead of just text output. It enables this Cmdlet to be automation friendly which means this Cmdlet can be used in scripting.
    • Default format of the output is Table format and can be customized.
    • Detailed Help documentation is added to the Cmdlet.
  • The Actual Start Date and Actual End Date fields are not populated for most activities. After this update is installed, these fields should be populated for all types of activities in Service Manager.
  • The Service Manager console crashes when you try to open an email message with a colon (:) in its name that was attached to an Incident through Exchange Connector (such as for prefixes “RE:” and “FW:” that are added by Outlook).
  • The SLA information that appears in the Service Manager console does not reflect an updated status in Data Warehouse if there are multiple status changes during extract.
  • The request offering wizard displays a cryptic "XML parsing error" and prevents the user from continuing with the request offering creation. This causes a problem if management packs are changed in Visual Studio (or any program that "pretty-prints" XML).

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_KB3063263_AMD64_7.5.3079.442.exe SHA1: 988d9b3082d5aba894fdc11cdad92a36fec054fb	72.80 MB
SCSM2012R2_CU_KB3063263_i386_7.5.3079.442.exe SHA1: 23f01ab7d325e9b12ab9d9a655bcf8ccdb1ec332	72.65 MB
SCSM2012R2_OD_KB3099983_AMD64_7.5.3079.504.exe SHA1: c4aecf78ab718db543bfd0780d47323c03d42b73	50.29 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_ KB3063263_AMD64_7.5.3079.442.exe file or the SCSM2012R2_CU_ KB3063263_i386_7.5.3079.442.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_KB3099983_AMD64_7.5.3079.504.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 (KB3099983) on Primary Management Server and as Microsoft System Center Service 2012 R2 Service Manager (KB3063263) 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.