Update Rollup 5 for System Center 2016 Operations Manager

Introduction

This article describes the issues that are fixed and the improvements that are included in Update Rollup 5 for Microsoft System Center 2016 Operations Manager. This article also contains the installation instructions for this update.

Issues that are fixed and improvements that are included

• SCOM console and Service Manager console for PowerShell modules can now coexist on the same server.
  
  Note Both SCOM Update Rollup 5 (this update) and Service Manager Update Rollup 5 (update KB 4093685) must be installed to resolve this issue.

• Active Directory Integration rules are not visible or editable in an upgraded 2016 Management Group. This prevents the ongoing management of Active Directory integration assignment in the upgraded Management Group.

• When the UNIX host name on the server is in lowercase, the OS and MonitoredBy information is displayed incorrectly in the Unix/Linux Computers view.

• Active Directory integrated agents do not display correct failover server information.

• Performance views in the web console do not persist the selection of counters after web console restart or refresh.

• The PowerShell cmdlet Get-SCXAgent fails with error “This cmdlet requires PowerShell version 3.0 or greater.”

• During the upgrade from SCOM 2016 to SCOM 1801, if the reporting server is installed on a server other than the management server, the upgrade fails. Additionally, you receive the error message, "The management server to which this component reports has not been upgraded."

• If a group name has been changed through the operations console, the Get-SCOMGroup cmdlet does not retrieve the group data that includes the changed group name.

• Error HTTP 500 occurs when you access Diagram view through the web console.

• When you download a Linux management pack after you upgrade to SCOM 2016, the error "OpsMgr Management Configuration Service failed to process configuration request (Xml configuration file or management pack request)" occurs.

• The SQLCommand Timeout property is exposed so that it can be dynamically adjusted by users to manage random and expected influx of data scenarios.

• The MonitoringHost process crashes and returns the exception "System.OverflowException: Value was either too large or too small for an Int32."

• When company knowledge is edited by using the Japanese version of Microsoft Office through the SCOM console, the error (translated in English) "Failed to launch Microsoft Word. Please make sure Microsoft Word is installed. Here is the error message: Item with specified name does not exist" occurs.

• Accessing Silverlight dashboards displays the "Web Console Configuration Required" message because of a certificate issue.

• Microsoft.SystemCenter.ManagementPack.Recommendations causes errors to be logged on instances of Microsoft SQL Server that have case-sensitive collations.

• Deep monitoring displays error “Discovery_Not_Found” if the installation of JBoss application server is customized.

• Adds support for the Lancer driver on IBM Power 8 Servers that use AIX.

• The ComputerOptInCompatibleMonitor monitor is disabled in the Microsoft.SystemCenter.Advisor.Internalmanagement pack. This monitor is no longer valid.

How to obtain Update Rollup 5 for System Center 2016 Operations Manager

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

Installation instructions for Operations Manager

Installation notes

• Important You must have for System Center 2016 Operations Manager Update Rollup 2 or a later version installed before you install Update Rollup 5, if you want to be able to uninstall this update rollup.

• This update rollup package is available from Microsoft Update in the following languages:

  • Chinese Simplified (CHS)

  • Chinese Traditional (CHT)

  • Czech (CSY)

  • Dutch (NLD)

  • English (ENU)

  • French (FRA)

  • German (DEU)

  • Hungarian (HUN)

  • Italian (ITA)

  • Japanese (JPN)

  • Korean (KOR)

  • Polish (POL)

  • Portuguese (Brazil) (PTB)

  • Portuguese (Portugal) (PTG)

  • Russian (RUS)

  • Spanish (ESN)

  • Swedish (SWE)

  • Turkish (TUR)

• Some components are multilanguage, and the updates for these components are not localized.

• You must run this update rollup as an administrator.

• If you don't 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 apply an update rollup immediately after you install System Center 2016 Operations Manager. Wait several hours after deployment of a new management group before you apply any update rollup.

• 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.

Supported installation order

1. Install the update rollup package in the following server infrastructure:

   • Management server or servers

   • Audit Collection Services

   • Web console server role computers

   • Gateway

   • Operations console role computers

   • Reporting

2. Apply SQL scripts.

3. Manually import the management packs.

4. Apply Agent updates.

5. Apply the Nano Agent update to manually installed agents, or push the installation from the Pending view in the Operations console.

6. Update Unix/Linux MPs and Agents.

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 Update 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 relate 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. Execute the following Database SQL script on the Database server against the OperationsManagerDB database:
   
   Update_rollup_mom_db.sql
   
   Note This script is located in the following path:

   %SystemDrive%\Program Files\System Center 2016\Operations Manager\Server\SQL Script for Update Rollups

4. Import the following management packs:

   • Microsoft.SystemCenter.Internal.mp

   • Microsoft.SystemCenter.2007.mp

   • Microsoft.SystemCenter.Advisor.Internal.mpb

   • Microsoft.SystemCenter.OperationsManager.Library.mp

   • Microsoft.SystemCenter.Image.Library.mp

   • Microsoft.SystemCenter.Visualization.Library.mpb

   • Microsoft.SystemCenter.Advisor.mpb

   • Microsoft.Windows.InternetInformationServices.CommonLibrary.mp

   • Microsoft.SystemCenter.AlertAttachment.mpb

   • Microsoft.SystemCenter.IntelliTraceProfiling.mpb

   • Microsoft.SystemCenter.SyntheticTransactions.Library.mp

   • Microsoft.SystemCenter.OperationsManager.AM.DR.2007.mp

   • Microsoft.SystemCenter.OperationsManager.SummaryDashboard.mp

   • Microsoft.SystemCenter.Advisor.Resources.(LANGUAGECODE_3LTR).mpb

   • Microsoft.SystemCenter.DataWarehouse.Report.Library.mp

   • Microsoft.SystemCenter.ACS.Internal.mp

   • Microsoft.SystemCenter.Visualization.ServiceLevelComponents.mpb

   • Microsoft.SystemCenter.Library.mpb

   • Microsoft.SystemCenter.Apm.Infrastructure.mpb

   • Microsoft.Windows.Cluster.Library.mp

For information about how to import a management pack from a disk, see the How to import, export, and remove 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 Center 2016\Operations Manager\Server\Management Packs for Update Rollups

Nano Agent update

To manually install the updates to Nano Agent, download the KB3209591-8.0.10913.0-NanoAgent.cab file. You can install this update on a Nano Agent system by using the following PowerShell script:

.\UpdateNanoServerScomAgentOnline.ps1
 -NanoServerFQDN <FQDN of target Nano Server>
 -BinaryFolder <Path where the update .cab is already expanded OR path to one or more Nano-agent update .cab files>
 -IsCabExpanded <$true if BinaryFolder path is to an expanded .cab, $false if it is for a packed .cab file(s)>
 -RemoveBackup <$true to remove the previous binaries from the agent machine>

Note The UpdateNanoServerScomAgentOnline.ps1 file is available here:

%SystemDrive%\Program Files\Microsoft System Center 2016\Operations Manager\Server\AgentManagement\Nano\NanoServer

UNIX and 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 5 (this update) to your System Center 2016 Operations Manager environment.

2. Download the “Microsoft System Center 2016 MP for Unix and Linux.msi” file:
   

   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 The PatchCodeGuid placeholder represents one of the following GUIDs.

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

Files updated in this update rollup