Update Rollup 12 for System Center 2012 R2 Operations Manager

• When you try to upgrade System Center 2012 R2 Operations Manager Reporting Server to System Center 2016 Operations Manager reporting server, the upgrade fails for the following configuration:
• Server A is configured as System Center 2012 R2 Operations Manager including Management Server.
• Server B is configured as System Center 2012 R2 Operations Manager, including Operations Manager Database (OpsMgrDB), Operations Manager Data Warehouse (OpsMgrDW) and Operations Manager Reporting Server.
( X ) Management Server Upgraded Check
The management server to which this component reports has not been upgraded.
• Recovery tasks on "Computer Not Reachable" messages in the System Center Operations Manager Monitor generate failed logons for System Center Operations Manager Agents that are not part of the same domain as the Management Groups.
• When a Management Server is removed from the All Management Servers Resource Pool, the monitoring host process do not update the Type Space Cache.
• SHA1 is deprecated for the System Center 2012 R2 Operations Manager Agent and SHA2 is now supported.
• Because of incorrect computations of configuration and overrides, some managed entities go into an unmonitored state. This behavior is accompanied by event 1215 errors that are logged in the Operations Manager log.
• IntelliTrace Profiling workflows fail on certain Windows operating system versions. The workflow cannot resolve Shell32 interface issues correctly.
• There is a character limitation of 50 characters on the custom fields in the notification subscription criteria. This update increases the size of the limitation to 255 characters.
• You cannot add Windows Client computers for Operational Insights (OMS) monitoring. This update fixes the OMS Managed Computers wizard in the System Center Operations Manager Administration pane to let you search or add Windows Client computers.
• When you use the Unix Process Monitoring Template wizard to add a new template to the monitor processes on UNIX servers, the monitored data is not inserted into the database. This issue occurs until the Monitoring Host is restarted. Additionally, the following is logged in the Operations Manager log file:
  
  
  Log entry:
  Log Name: Operations Manager
  Source: Health Service Modules
  Date:
  Event ID: 10801
  Task Category: None
  Level: Error
  Keywords: Classic
  User: N/A
  Computer:
  Description: Discovery data couldn't be inserted to the database. This could have happened because of one of the following reasons:
  - Discovery data is stale. The discovery data is generated by an MP recently deleted.
  - Database connectivity problems or database running out of space.
  - Discovery data received is not valid.


Additionally, you may receive the following exception, which causes this issue to occur:

Exception type:   Microsoft.EnterpriseManagement.Common.DataItemDoesNotExistException
Message:          ManagedTypeId = ccf81b2f-4b92-bbaf-f53e-d42cd9591c1c
InnerException:   <none>
StackTrace (generated):         SP            IP            Function            000000000EE4EF10 00007FF8789773D5 Microsoft_EnterpriseManagement_DataAccessLayer!Microsoft.EnterpriseManagement.DataAccessLayer.TypeSpaceData.IsDerivedFrom(System.Guid, System.Guid)+0x385

• RHEL 7 on Power8 is now supported in System Center2012 R2 Operations Manager

• SHA1 is deprecated and SHA2 is now supported on the management server that's used to sign the UNIX/Linux Operations Manager i (OMi) certificate.
• OMi start attempts fail on all FIPS-enabled UNIX/Linux systems. This fix updates the agents to support FIPS-enabled systems.
• The Average Physical disk sec/transfer performance counters are not displayed for Hewlett Packard systems.
• OMi displays incorrect memory information for Solaris 10 systems.
• The Network Adapter Performance counter is not displayed for SLES 12 x64 platforms in the console.
• You can't discover file systems on HPUX 11.31 IA-64 computers that have more than 128 disks. Previously, only 128 VGs were supported. This update extends support to 256 VGs.
• Deep monitoring can't be started successfully for some Jboss applications because the discovery of the Jboss application server sets the DiskPath for the Jboss server incorrect. Deep monitoring is not started in JBoss stand-alone mode when a nondefault configuration is used. This update provides additional support for JBoss stand-alone mode.

Download information

Update packages for Operations Manager are available from Microsoft Update or by manual download.

Microsoft Update

To obtain and install an update package from Microsoft Update, follow these steps on a computer that has an Operations Manager component installed:

1. Click Start, and then click Control Panel.
2. In Control Panel, double-click Windows Update.
3. In the Windows Update window, click Check Online for updates from Microsoft Update.
4. Click Important updates are available.
5. Select the update rollup package, and then click Ok.
6. Click Install updates to install the update package.

Manual download of the update packages

Go to the following website to manually download the update packages from the Microsoft Update Catalog:

 Download the Operations Manager update package now.

Installation notes

• This update rollup package is available from Microsoft Update in the following languages:
• Chinese Simplified (CHS)
• Japanese (JPN)
• French (FRA)
• German (DEU)
• Russian (RUS)
• Italian (ITA)
• Spanish (ESN)
• Portuguese (Brazil) (PTB)
• Chinese Traditional (CHT)
• Korean (KOR)
• Czech (CSY)
• Dutch (NLD)
• Polish (POL)
• Portuguese (Portugal) (PTG)
• Swedish (SWE)
• Turkish (TUR)
• Hungarian (HUN)
• English (ENU)
• Chinese Hong Kong (HK)
• Some components are multilanguage, and the updates for these components are not localized.
• You must run this update rollup as an administrator.
• If you do not want to restart the computer after you apply the console update, close the console before you apply the update for the console role.
• To start a new instance of Microsoft Silverlight, clear the browser cache in Silverlight, and then restart Silverlight.
• Do not install this update rollup package immediately after you install the System Center 2012 R2 server. Otherwise, the Health Service state may not be initialized.
• If User Account Control is enabled, run the .msp update files from an elevated command prompt.
• You must have System Administrator rights on the database instances for the Operational Database and Data warehouse to apply updates to these databases.
• To enable the web console fixes, add the following line to the %windir%\Microsoft.NET\Framework64\v2.0.50727\CONFIG\web.config file:
  

  <machineKeyvalidationKey="AutoGenerate,IsolateApps"decryptionKey="AutoGenerate,IsolateApps" validation="3DES"decryption="3DES"/>

  Note Add the line under the <system.web> section, as described in the following article in the Microsoft Knowledge Base:
  
  911722 You may receive an error message when you access ASP.NET web pages that have ViewState enabled after you upgrade from ASP.NET 1.1 to ASP.NET 2.0
  
  
• The fix for the data warehouse BULK insert commands time-out issue that's described in Update Rollup 1 for System Center 2012 R2 Operations Manager adds a registry key. This key can be used to set the time-out value (in seconds) for the data warehouse BULK insert commands. These are the commands that insert new data into the data warehouse.
  
  Note This key must be manually added on any management server on which you want to override the default BULK insert command time-out.
  
  Registry settings:

  Registry location: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft OperationsManager\3.0\Data Warehouse

  DWORD name: Bulk Insert Command Time Out Seconds

  DWORD Value: 40
  

  
  Note Set this value in seconds. For example, for a 40-second time-out, set this value to 40.

Supported installation order

We recommend that you install this update rollup package by following these steps in the given order:

1. Install the update rollup package on the following server infrastructure:
• Management server or servers
• Audit Collection Services
• Gateway servers
• Web console server role computers
• Operations console role computers
• Reporting
  
  Note

  January 26, 2017: We had an issue with the Reporting component available through the Microsoft Update Catalog. When you download the Reporting component, the update files offered are those of the Console component. We are working to fix the Reporting component update offered through the Microsoft Update Catalog.
  
  January 26, 2017: This issue is now resolved. The update files offered are now those of the Reporting component.
  

• Agent
  
2. Apply SQL scripts (see installation information).
3. Manually import the management packs.
4. Apply the agent update to manually installed agents, or push the installation from the Pending view in the Operations console.
   

Operations Manager update

To download the update rollup package and extract the files that are contained in the update rollup package, follow these steps:

1. Download the update packages that Microsoft Update provides for each computer. Microsoft Update provides the appropriate updates according to the components that are installed on each computer. Or download from the Microsoft Download Catalog.
2. Apply the appropriate .msp files on each computer.
   
   Note MSP files are included in the update rollup package. Apply all .msp files that correspond to a specific computer. For example, if the web console and console roles are installed on a management server, apply the .msp files on the management server. Apply one .msp file on a server for each specific role that the server holds.
   
   
3. Run the flowing Datawarehouse SQL script on Datawarehouse Server against OperationsManagerDW database:
   
   UR_Datawarehouse.sql
   
   Note This script is can be found in the following location:
   
   %SystemDrive%\Program Files\System Center2012 R2\Operations Manager\Server\SQL Script for Update Rollups
   
   
4. Run the following Database sql script on the Database server against the OperationsManagerDB database:
   
   Update_rollup_mom_db.sql
   
5. Import the following management packs:
• Microsoft.SystemCenter.TFSWISynchronization.mpb, which has the following dependencies:
• Microsoft.SystemCenter.AlertAttachment.mpb, which should be installed from the System Center Operations Manager 2012 R2 media.
• Microsoft.SystemCenter.Visualization.Library.mpb
• Microsoft.SystemCenter.Visualization.Component.Library.mpb
• Microsoft.SystemCenter.Visualization.Library.mpb
• Microsoft.SystemCenter.Advisor.mpb
• Microsoft.SystemCenter.Advisor.Internal.mpb
• Microsoft.SystemCenter.2007.mp
• Microsoft.SystemCenter.Advisor.Resources.(LANGUAGECODE_3LTR).mpb
• Microsoft.SystemCenter.SyntheticTransactions.Library.mp
• Microsoft.SystemCenter.OperationsManager.Library.mp
• Microsoft.SystemCenter.OperationsManager.Internal.mp
• Microsoft.SystemCenter.Apm.Web.IIS10.mp, which has the following dependencies:
• Microsoft.SystemCenter.Apm.Infrastructure.mpb
• Microsoft.SystemCenter.Apm.Library.mpb
• Microsoft.SystemCenter.Apm.Library.Resources.(LANGUAGECODE_3LTR).mpb
• Microsoft.Windows.InternetInformationServices.2016.mp (this MP has to be downloaded separately from the Microsoft Update Catalog) which has the following dependency:
• Microsoft.Windows.Server.2016.Discovery.mp (this MP has to be downloaded separately from the Microsoft Update Catalog)
• Microsoft.SystemCenter.ClientMonitoring.Internal.mp, which has the following dependency:
• Microsoft.SystemCenter.ClientMonitoring.Library.mp
• Microsoft.SystemCenter.DataWarehouse.Report.Library.mp
• Microsoft.SystemCenter.ClientMonitoring.Views.Internal.mp
• Microsoft.SystemCenter.OperationsManager.AM.DR.2007.mp
  

For information about how to import a management pack from a disk, see the How to Import an Operations Manager Management Pack topic on the Microsoft TechNet website

Note Management packs are included in the Server component updates in the following location:

%SystemDrive%\Program Files\System Center2012 R2\Operations Manager\Server\Management Packs for Update Rollups

UNIX/Linux Management Pack update

To install the updated monitoring packs and agents for UNIX and Linux operating systems, follow these steps:

1. Apply Update Rollup 12 to your System Center 2012 R2 Operations Manager environment.
2. Download the updated management packs for System Center 2012 R2 from the following Microsoft website:
   
     System Center Management Pack for UNIX and Linux Operating Systems
   
   
3. Install the management pack update package to extract the management pack files.
4. Import the updated management pack for each version of Linux or UNIX that you are monitoring in your environment.
5. Upgrade each agent to the latest version by using either the Update-SCXAgent Windows PowerShell cmdlet or the UNIX/Linux Agent Upgrade Wizard in the Administration pane of the Operations Console.
   
   

Uninstall information

To uninstall an update, run the following command:

msiexec /uninstall PatchCodeGuid /package RTMProductCodeGuid

Note In this command, PatchCodeGuid is a placeholder that represents one of the following GUIDs.

Additionally, the RTMProductCodeGuid placeholder represents one of the following GUIDs:

The following is a list of files that have changed in this update rollup. If you don't have all previous update rollups installed, files other than those listed here may also be updated. For a complete list of files that are updated, see the "Files Updated in this Update Rollup" section of all update rollups that were released after your current update rollup.

The following is a list of files that have changed in this update rollup. If you do not have all previous update rollups installed, files other than those listed here may also be updated. For a complete list of files that are updated, see the "Files updated in this update rollup" section of all update rollups that were released after your current update rollup.