Update Rollup 5 for System Center 2016 Operations Manager

Applies to: Microsoft 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.Internal management 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.

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. Select Start, and then select Control Panel.
  2. In Control Panel, double-click Windows Update.
  3. In the Windows Update window, select Check Online for updates from Microsoft Update.
  4. Select Important updates are available.
  5. Select the update rollup package, and then select Ok.
  6. Select Install updates to install the update package.

If your computer is running Windows Server 2016 or later, follow these steps:

  1. Select Start, and then select Settings.
  2. In Settings, select Updates & Security.
  3. On the Windows Update tab, select Check Online for updates from Microsoft Update.
  4. Select Important updates are available.
  5. Select the update rollup package, and then select OK.
  6. Select Install updates to install the update package.

Manual download

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

 Download the Operations Manager update package now.

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

PatchCodeGUID

Component

Architecture

Language

{48003625-B639-4ACF-A607-740AE4451E49}

Agent

amd64

en

{A9DD2725-A54F-4B9F-9D3F-3AA7C1B9BC7B}

ACS

amd64

en

{383CFB77-4913-4720-9993-2E7EFBEA6EE7}

Console

amd64

en

{CA0FD4E9-1BBF-48B4-AFBE-646390A51A48}

Reporting

amd64

en

{B8442D02-5240-45C7-B01C-4D892F385FDB}

WebConsole

amd64

en

{E3037D78-0BFB-47B9-BA75-2618483FED6F}

Gateway

amd64

en

{D44DF6F0-F5EC-4C5E-BAB1-13169E07A4CE}

Server

amd64

en

{DD078BBB-9C66-4AED-AE78-B01F09B97E0C}

Agent

x86

en

{DB0BDEA0-BA5A-4E66-A68A-7E4BB3139245}

Console

x86

en

{4F2443E6-24E8-4866-9E31-D4FAFA709EE5}

Agent

amd64

en

{B1720AF4-EC3D-4442-98E0-D637116C880A}

ACS

amd64

en

{FB20411C-F106-4B21-A09F-942A8BD91A26}

Console

amd64

en

{41EAD9BF-8B94-414D-85C3-F64FFFBFE4F2}

Reporting

amd64

en

{18284520-DFB8-4089-8B80-5106986DC15F}

WebConsole

amd64

en

{5F53E502-E1BE-4F95-8FE6-59AE521E0356}

Gateway

amd64

en

{60240ECB-E490-488C-BBC3-76CA3B000E01}

Server

amd64

en

{0CC2F57C-E928-4214-B011-FFF8309183CC}

Agent

x86

en

{22223C1D-073F-4ACF-8AE2-D9C2D8170681}

Console

x86

en

{EE191392-7A88-4D97-B89E-99DCB327562F}

ACS

amd64

cn

{1221DC27-D114-488E-90E9-7AAC60C961B3}

Console

amd64

cn

{8450FBB0-68D1-4CA9-B55D-94D034378722}

Reporting

amd64

cn

{8807EB97-A900-4A1D-8092-3410AE916862}

WebConsole

amd64

cn

{FBBD53D0-108A-4731-A61C-73C89B19BF22}

Console

x86

cn

{C5E34F02-4E55-427A-8B89-16CEE126297A}

ACS

amd64

cs

{B22A04BF-BD94-4FF1-810B-B431685EAC55}

Console

amd64

cs

{EB49064F-0A20-4B9C-82F2-CFF6FC4DA2B4}

Reporting

amd64

cs

{D4CC45D5-E4FD-4218-A0A9-C99A3DC5DEE4}

WebConsole

amd64

cs

{FE5D7B60-0717-4CC4-B956-5192E07CA526}

Console

x86

cs

{F454C6DE-1B4D-4910-AE11-99B2BA584C65}

ACS

amd64

de

{EAC40980-BEC2-447A-ABFB-951AE38897F7}

Console

amd64

de

{B7CB26C8-5CAB-40FE-9205-C09490D5D387}

Reporting

amd64

de

{AF5AC215-525A-4092-BF9D-A0E694449A24}

WebConsole

amd64

de

{65DAC186-B79C-4EAB-910E-467CADEF849C}

Console

x86

de

{7B27B42B-A8FB-4254-BF82-AA3441D596E9}

ACS

amd64

es

{466483DE-FA05-4B51-B709-D6B6B50190FC}

Console

amd64

es

{0687F06B-BDDD-4021-B191-C1AF6862AFF7}

Reporting

amd64

es

{57BE01ED-6ECB-45A7-917C-6833402D2236}

WebConsole

amd64

es

{DD70C0E7-3915-4858-B8DA-721E8D25E1D2}

Console

x86

es

{3A2185A4-D9E2-41F7-B412-E06DB80BB145}

ACS

amd64

fr

{B3C84C16-967B-45B7-B82C-D247A8598B05}

Console

amd64

fr

{016FCDED-EA7B-4E76-8C06-D69458C35EF3}

Reporting

amd64

fr

{57781F3F-2252-4255-BD3E-5464B71C48B0}

WebConsole

amd64

fr

{4E139B97-A501-44E7-9212-E81F13089D61}

Console

x86

fr

{F88A4C1D-DCDA-49E4-9639-04ED57B9A062}

ACS

amd64

hu

{A8C82B76-4321-4602-AE76-8097B7731835}

Console

amd64

hu

{35F5F98C-8EC9-48B6-A6F9-A963D8CDA048}

Reporting

amd64

hu

{125D1DD4-7037-4F3A-B9B3-B8602FD9DB9E}

WebConsole

amd64

hu

{C759F877-F8A1-4879-A8A1-14B0DE96116A}

Console

x86

hu

{EBF51B32-362D-49DA-87EC-E9474F4F4BE4}

ACS

amd64

it

{96512EC0-2FE1-4333-8D56-4099B1779438}

Console

amd64

it

{85681EE1-E59D-48F5-A4BC-83B739D14527}

Reporting

amd64

it

{1470E6B1-1F08-48C1-8F1E-6F0AF7C6DFDB}

WebConsole

amd64

it

{770CEC97-5BA4-4E77-9210-AB33AD2C90CB}

Console

x86

it

{CB2BE550-CF28-4801-8BDF-DA7A629476EE}

ACS

amd64

ja

{04547E98-C433-451D-A5C3-24638FDC590B}

Console

amd64

ja

{CC65C8ED-888E-49B4-9449-BD3E05ADC0F2}

Reporting

amd64

ja

{85FF01E7-6EAA-448A-AAEF-C711E6645234}

WebConsole

amd64

ja

{966D1BF7-EFEC-4F3A-BCF9-6E18BFBF1B33}

Console

x86

ja

{CDDD9DB0-2933-4FB3-A38C-7D620DEB71E8}

ACS

amd64

ko

{2EAEC2BF-0031-4C72-AE85-02125E5D5933}

Console

amd64

ko

{F0BE378C-7905-49BF-A0AE-0D40EA86C927}

Reporting

amd64

ko

{E663DF3C-31BC-4F3C-9838-7C0FF4B39934}

WebConsole

amd64

ko

{80A882DB-A11D-4C51-B7E6-680E7D81267B}

Console

x86

ko

{E7EFE5FA-5A51-4FD3-9964-15645CEA3E6B}

ACS

amd64

nl

{E698C12D-89BD-4032-8674-85141BC20DA1}

Console

amd64

nl

{5C82DD2D-C09C-4864-9420-37BBE2DADB65}

Reporting

amd64

nl

{A742C726-B967-4806-9CC2-FF833FF04BE1}

WebConsole

amd64

nl

{1BC49078-351C-4FD2-9403-2DFAD2830D3F}

Console

x86

nl

{D4300589-CB01-4C09-A446-664D46D0AA6A}

ACS

amd64

pl

{E1F5A23F-65D2-43A4-8B8B-BCA794A420F6}

Console

amd64

pl

{A5969383-D5C0-4E0D-8E4F-392B4CA6E3EB}

Reporting

amd64

pl

{5E65A8B0-3165-433D-BAD2-326D29B814E2}

WebConsole

amd64

pl

{39FECFB5-B272-4474-8FF7-13F331DA16C0}

Console

x86

pl

{25739314-B18C-41DA-A0E8-8F8463B7245A}

ACS

amd64

pt-br

{AE1427DA-D86F-4489-BA84-7E31E6F89AE8}

Console

amd64

pt-br

{C1BA99B8-F17F-4F57-AEA1-5717B3447269}

Reporting

amd64

pt-br

{BC3B5B0C-DBBF-4416-92DE-E59764F24A0B}

WebConsole

amd64

pt-br

{C1D67251-EC6A-42EF-AF13-D6968021BA47}

Console

x86

pt-br

{6B5BAFE2-65BD-4202-B119-F08F59C77B37}

ACS

amd64

pt-pt

{4A5BBACA-1371-4317-B134-4376BF4A80CE}

Console

amd64

pt-pt

{51EF061E-9D73-47A7-98E6-D860A8DDC010}

Reporting

amd64

pt-pt

{032089FF-ABFF-4AF9-AD92-BDDA17111A05}

WebConsole

amd64

pt-pt

{B1D70A91-357F-4609-B46B-EFA6014E454E}

Console

x86

pt-pt

{8144FA08-B990-4C8D-B282-3692677E9B89}

ACS

amd64

ru

{20220216-D2ED-4348-BF0E-5BDCEDBF51F8}

Console

amd64

ru

{1D06B47A-8F66-441F-A5BC-181E2F7F9831}

Reporting

amd64

ru

{9D93F86C-F748-446D-A66C-E87CAFF7EF72}

WebConsole

amd64

ru

{52E3279F-11C1-4315-A967-E15161348A55}

Console

x86

ru

{B73FC320-7B65-49B9-A015-72F1AC4E9393}

ACS

amd64

sv

{FC7F332C-5975-4C0C-B43D-D08448CEF1AC}

Console

amd64

sv

{13E99E5A-B7FB-404E-81CE-6BCF5F1332EE}

Reporting

amd64

sv

{3316DF69-C818-408B-801C-5A6BDB4B7F4B}

WebConsole

amd64

sv

{E72FCAF5-BF1E-48A0-9B10-560763A66452}

Console

x86

sv

{7CD26F0E-16A8-45AB-ABCD-73B383C14651}

ACS

amd64

tr

{7227E284-DD35-4147-8DA3-2100EC7B5501}

Console

amd64

tr

{E5817F02-96A3-4433-86D1-DA85870CC10E}

Reporting

amd64

tr

{9D8A3979-9C50-4CB7-82F5-C128B4A64840}

WebConsole

amd64

tr

{1FAB168F-88E9-4658-A79E-D79CB0F71C00}

Console

x86

tr

{B42B196C-9D26-4020-8DD0-8ABA5F33D7F6}

ACS

amd64

tw

{511A0A34-850D-4521-9C0E-E538746C8A22}

Console

amd64

tw

{86B74F13-C1BF-4D2B-9D46-43DB75FBCB21}

Reporting

amd64

tw

{05BBDB10-7891-4062-B92E-204509B4666E}

WebConsole

amd64

tw

{14A400DB-D9F6-422C-AC13-8B5AC8C2CD7B}

Console

x86

tw


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

Component

RTMProductCodeGuid

Agent Amd64

{742D699D-56EB-49CC-A04A-317DE01F31CD}

Agent X86

{430BF0E7-3BA7-49FF-8BD1-F34F6F1057A6}

Server

{1199B530-E226-46DC-B7F4-7891D5AFCF22}

Console Amd64

{E072D8FC-CD31-4ABE-BD65-606965965426}

Console X86

{AF337207-0486-4713-AE0F-5CE4110B2D24}

WebConsole

{676EB643-C22A-4EEC-A8CF-13A0719056A5}

Gateway

{B47D423B-580B-4D57-9AFD-D0325F839FE9}

ACS

{74EF4714-88C0-44D9-B8C7-19BABBFA4D6A}

Files updated in this update rollup