Applies ToSystem Center 2016 Operations Manager

Introduction

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

Improvements and issues that are fixed

  • Fixed: Cannot use SQLOleDB.dll to probe databases like Oracle/MySQL.

  • Improved the performance of SCOM console in listing the groups.

  • Operations Manager grooms out the alert history only on an alert closure.

  • Agents by Health State report shows duplicate agent names.

  • Users of a scoped group are not able to use the Console.

  • Fixed an issue that prevented addition of a group in the Storage Spaces Direct 2016 management pack dashboard.

  • SCOM Network Device Re-Discovery now probes for SNMP V3 devices too.

  • Fixed re-registering for SNMP Traps in the Proxy Management Server.

  • Windows Computer Property "NetbiosDomainName" is not discovered properly.

  • SCOM console crashes while trying to connect to Azure Log Analytics and Azure Monitor.

  • Linux agent is not able to get the correct version and port details for JBoss EAP 7.1.

  • An issue that lead to creation of multiple empty temp files in the /tmp directory of Linux servers has been fixed.

  • Fixed the formatting issue with the output for the task ‘Top10 CPU Processes' when using Windows Management Infrastructure (MI) APIs.

  • XPlat agent now supports monitoring of SUSE-11 SP4 platform with Security Module installed on it for TLS 1.2 compliance.

  • Fixed an issue that caused the corruption of /etc/login.cfg file on AIX 7 machines during install/upgrade of the agent.

  • AIX Agent is now transitioned to 64-bit package to accommodate more stack and heap space if needed to avoid any stack/heap overflow which occasionally leads to heartbeat failure.

  • Free memory calculation accommodated appropriately on RHEL-7 platform.

How to obtain Update Rollup 7 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. 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.

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

  1. Click Start, and then click Settings.

  2. In Settings, click Updates & Security.

  3. On the Windows Update tab, 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

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

 Download the Operations Manager update package now.

For information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to obtain Microsoft support files from online services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Installation instructions for Operations Manager

Installation notes

  • Important You must have the System Center 2016 Operations Manager Server (KB3209591) update installed before you install this System Center 2016 Operations Manager Server (KB4492182) update.

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

  • Some components are multi-language, 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 on 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. Alternatively, download the packages 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 at the following path:

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

  1. 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 Microsoft TechNet topic How to Import an Operations Manager Management Pack.

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>

 

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 to your System Center 2016 Operations Manager environment.Note There are no UNIX/Linux MP updates in Update Rollup 6.

  2. Download the updated management packs for System Center 2016 from the following Microsoft website:

System Center Management Pack for UNIX and Linux Operating Systems

  1. Install the management pack update package to extract the management pack files.

  2. Import the updated management pack for each version of Linux or UNIX that you are monitoring in your environment.

  3. Upgrade each agent to the latest version by using 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

{92FB3F6D-03E6-4BA2-AA13-389BD60C6A9E}

Agent

amd64

en

{18C0C757-4AC1-4E97-9261-C44D8AE46790}

ACS

amd64

en

{4A925E5B-9330-45BB-BD17-B5786AA5DA56}

Console

amd64

en

{8DA62CA9-D3E0-416A-BE13-1AE331EC2D98}

Reporting

amd64

en

{2905B128-6A9E-4326-89A9-E06752B2E31D}

WebConsole

amd64

en

{CA163F5B-CF66-4A59-BE70-6F0195F32F7C}

Gateway

amd64

en

{9EA273F5-9438-46DD-99CD-0DC6C675C6D1}

Server

amd64

en

{E8431260-7D43-4587-A037-AF58D5D499EF}

Agent

x86

en

{9F3794A4-03D0-4770-9A56-3A5CDEE779A9}

Console

x86

en

{E4775734-61F2-4256-A8F4-9123619F0120}

ACS

amd64

cn

{720DE04A-29FE-40DC-9AD0-E2980E8C6C24}

Console

amd64

cn

{82C5D596-EB73-4495-8B63-4A24EF4893BC}

Reporting

amd64

cn

{DA890938-5FBD-4AE5-9158-CB3733F38778}

WebConsole

amd64

cn

{9D5DCEFA-C833-4A35-A172-94B011F46910}

Console

x86

cn

{71F2CAEC-24AF-4978-9F9C-FCED359BBDAE}

ACS

amd64

cs

{52B5666B-3FDD-49FD-BFE9-1C30D91CAB79}

Console

amd64

cs

{96A6681C-12B0-4007-B465-D0CF339253C5}

Reporting

amd64

cs

{9687F4FD-AEC6-427E-99B2-8327F340DC43}

WebConsole

amd64

cs

{F5E68F98-4E76-4814-9E53-6DADC8ED57DA}

Console

x86

cs

{5379FCFF-3123-4A1D-9881-75A1F6DDD7FA}

ACS

amd64

de

{F0B1D2C2-BB37-4792-BE51-7281E1462F75}

Console

amd64

de

{FE96EA70-A32E-425C-B0EC-822B4B85DC7C}

Reporting

amd64

de

{BCC6B144-CC60-4BF4-901A-0F9F78910F24}

WebConsole

amd64

de

{2F5BF895-0F42-4480-A756-31651BDEBD74}

Console

x86

de

{B3DC12E7-4D2C-44D4-99FD-013DF567C0F7}

ACS

amd64

es

{A0306B2B-26BD-4160-B6B2-F2A959332F2C}

Console

amd64

es

{A92488C6-AEAE-458D-9268-707A35165225}

Reporting

amd64

es

{0245F177-DE96-4D77-91B6-37EFC0F671C8}

WebConsole

amd64

es

{EB32FC5A-8FD3-4D13-9A90-0EC1A1E9153C}

Console

x86

es

{D7097B7A-1048-4C5B-B47D-AF07F837DCF9}

ACS

amd64

fr

{6A059005-67D5-442D-AE52-C40C6674460D}

Console

amd64

fr

{4DD8B05D-D91D-439E-80D8-88F57BBFAC86}

Reporting

amd64

fr

{3947A585-593F-4750-AEC5-585063F086E1}

WebConsole

amd64

fr

{8AA81FE1-D9EA-4D28-BDD0-F200B2AF73DB}

Console

x86

fr

{F405CF87-36AD-4DE5-A00E-1085730C2ECE}

ACS

amd64

hu

{4CED3228-0665-4101-9D2C-EA0AFDF79EC3}

Console

amd64

hu

{E42B7A3B-0CD2-4016-9721-7B5CB23F6F7E}

Reporting

amd64

hu

{7F09FB5C-253F-47DB-A8E4-447A01CC2A23}

WebConsole

amd64

hu

{3F54E24C-062D-4A92-9514-80EB52D354B2}

Console

x86

hu

{126EA85B-9DE8-4C7C-A55E-0550A3F50E55}

ACS

amd64

it

{B0AF0FBA-8BA6-4862-A48D-F57934508BC0}

Console

amd64

it

{6ABFC5EA-44EF-4245-834D-244C7B737BCD}

Reporting

amd64

it

{9737907E-D87F-4A11-9960-0F8964F061A6}

WebConsole

amd64

it

{C3751CFE-197F-487F-A5E8-4B7B3A899867}

Console

x86

it

{DA1D4855-86DA-429D-A7F3-C771959B3120}

ACS

amd64

ja

{40C8AA97-22CB-443C-AA0B-D262C25AF74B}

Console

amd64

ja

{25AE59EB-1D84-4CCF-9FEC-D2C609AF55C9}

Reporting

amd64

ja

{5F1799CC-3021-44A6-88C0-D82107FABBF0}

WebConsole

amd64

ja

{8E06E101-594A-4A63-BE8F-5927A924BEA2}

Console

x86

ja

{0F58A854-0323-4059-80B4-AEAEEF50EB98}

ACS

amd64

ko

{F9430A87-4525-4DA0-BACF-60F149948A34}

Console

amd64

ko

{CBF196B9-8FCB-4979-80E7-480D4ED77A97}

Reporting

amd64

ko

{DAB4C798-8D3A-48A8-96F3-196E34B3BE9F}

WebConsole

amd64

ko

{34257163-2358-4AEB-99B7-C3CF5C23677D}

Console

x86

ko

{08AFCF02-2E37-4DCD-AA40-E8789954DEB3}

ACS

amd64

nl

{44276F8A-3F50-4A0A-BD0A-A7AC279BC914}

Console

amd64

nl

{57DA4C3E-21C2-4B06-BA33-4382A79F1EC9}

Reporting

amd64

nl

{856CB503-288D-4D40-B7D4-40F9594CDD0F}

WebConsole

amd64

nl

{849F2C56-93F6-4449-B333-2674162CEC1F}

Console

x86

nl

{BCC2CB9E-32A7-44F8-8210-0D58DD298B8B}

ACS

amd64

pl

{D703F64D-FEC9-48BF-9626-E868B4C77F88}

Console

amd64

pl

{ED5DCCC8-323F-4051-9FE4-0BD360347556}

Reporting

amd64

pl

{49AD085E-F47B-4201-9C9E-EE91CCF256CD}

WebConsole

amd64

pl

{D75803D4-0336-4938-B1DD-04C7B7E71A67}

Console

x86

pl

{0B08DA9A-C364-41C5-9CAD-28B5D071C732}

ACS

amd64

pt-br

{92211D6F-4869-4197-AAF8-F547703F14F9}

Console

amd64

pt-br

{DB64686F-F555-45AA-ACD6-0B488C67F317}

Reporting

amd64

pt-br

{17A76E27-B4E6-4E5F-A934-18FF980F46FB}

WebConsole

amd64

pt-br

{32B1E6EF-0B28-40C5-931C-490922E85372}

Console

x86

pt-br

{9AA7C1A7-7598-458A-94CB-649B4A28BE8D}

ACS

amd64

pt-pt

{7E508DD5-2C3C-4461-B1A3-A07A0248BD83}

Console

amd64

pt-pt

{DDA6F1AE-2604-40B8-8558-0479715AB638}

Reporting

amd64

pt-pt

{89D57A97-E507-4D58-824E-CE1D0529AA62}

WebConsole

amd64

pt-pt

{F894DEE6-7E74-445C-96E6-A93AB9EE54D3}

Console

x86

pt-pt

{5365553A-519A-40B5-BB7B-E8F09F0C091F}

ACS

amd64

ru

{04301913-52DC-4AB1-B472-F7B779067F8C}

Console

amd64

ru

{54B3829E-31AF-4927-940D-8BF1F49B4110}

Reporting

amd64

ru

{522CA22F-8CDB-4ED7-B81C-2549ECED4CDD}

WebConsole

amd64

ru

{1ED42F48-68EE-44EE-93A2-8FB174717F1F}

Console

x86

ru

{14B03ED1-17E3-4606-8115-CC139FC8A07C}

ACS

amd64

sv

{82EB1C92-A8DB-46CA-B992-603A49245EE7}

Console

amd64

sv

{56ACD16A-6BAB-4BC8-B37F-65340809CCFC}

Reporting

amd64

sv

{ACA4B185-4248-486E-BF48-179BA1EA84F0}

WebConsole

amd64

sv

{F3C2FB56-0A66-45C7-B985-C806100443D9}

Console

x86

sv

{2440EFF7-E0DC-4210-92AF-56A5C49EA487}

ACS

amd64

tr

{F510DAEC-1216-4748-9644-0D4981B72436}

Console

amd64

tr

{BE09E4E2-206F-484B-92A3-B9C52675FFB2}

Reporting

amd64

tr

{EDC35C70-13A2-4696-AFEC-1FE1A8176536}

WebConsole

amd64

tr

{5815D57E-585A-4CC1-BE48-AD6EDB9BC0BC}

Console

x86

tr

{C80CBF84-A81B-4164-B5D8-74DA5546769F}

ACS

amd64

tw

{14C63D54-05B4-43C6-B80C-D57416030D6C}

Console

amd64

tw

{92AE769D-9724-4479-AAF5-EAC6228BE9C1}

Reporting

amd64

tw

{5EFE9E83-0484-48C1-8A3A-73878C56FA8E}

WebConsole

amd64

tw

{A28A2162-ACF1-4565-AD0B-52D984907C5F}

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

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.

Files Updated

Version

File Size

MomNetworkModules.dll

8.0.11025.0

737KB

SnmpModules.dll

8.0.11025.0

464KB

MomWsManModules.dll

8.0.11025.0

230KB

Microsoft.EnterpriseManagement.DataAccessService.Core.dll

7.2.12150.0

694KB

Microsoft.EnterpriseManagement.DataAccessLayer.dll

7.2.12150.0

2501KB

Microsoft.EnterpriseManagement.DataAccessLayer.QueryCache.dll

7.2.12150.0

2239KB

sm-auto-discovery.dll

7.2.12150.0

4387KB

UR_DataWarehouse.sql

 

 15KB

Microsoft.SystemCenter.Advisor.mpb

7.2.12150.0

 584KB

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.