Update Rollup 3 for System Center 2016 Operations Manager

Introduction

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

Issues that are fixed

• When you run the Agents module version 1.6.2-337, you may receive the following alert:

Module was unable to convert parameter to a double value

• When you run System Center 2016 Operations Manager in an all-French locale (FRA) environment, the Date column in theCustom Event report appears blank.
• The Enable deep monitoring using HTTP task in the System Center Operations Manager console doesn’t enable WebSphere deep monitoring on Linux systems.
• When overriding multiple properties on rules that are created by the Azure Management Pack, duplicate override names are created. This causes overrides to be lost.
• When the heartbeat failure monitor is triggered, a “Computer Not Reachable” message is displayed even when the computer is not down.
• The Get-SCOMOverrideResult PowerShell cmdlet doesn’t return the correct list of effective overrides.
• When creating a management pack (MP) on a client that contains a Service Level (SLA) dashboard and Service Level Objects (SLO), the localized names of objects aren’t displayed properly if the client’s CurrentCulture settings don’t match theCurrentUICulturesettings. In cases where the localized settings areEnglish English, ENG, orAustralian English, ENA, there’s an issue when the objects are renamed.
• The Event ID: 26373 error, which may cause high memory consumption and affect server performance, has been changed from a “Critical” message to an “Informational” message.
• The Application Performance Monitoring (APM) feature in System Center 2016 Operations Manager Agent causes a crash for the IIS Application Pool that’s running under the .NET Framework 2.0 runtime. Microsoft Monitoring Agent should be updated on all servers that use the .NET Framework 2.0 application pools for APM binaries update to take effect. Restart of the server might be required if APM libraries were being used at the time of the update.

Important This issue is not completely resolved in Update Rollup 3. For more details of this issue, see the Update on APM fix for agent crashing issue shipped in UR3 blog on the Microsoft website.

• The UseMIAPI registry subkey prevents collection of processor performance data for RedHat Linux system. Also, custom performance collection rules are also impacted by theUseMIAPI setting.
• Organizational Unit (OU) properties for Active Directory systems are not being discovered or populated.
• The Microsoft.SystemCenter.Agent.RestartHealthService.HealthServicePerfCounterThreshold recovery task fails to restart the agent, and you receive the following error message:

LaunchRestartHealthService.ps1 cannot be loaded because the execution of scripts is disabled on this system.

This issue has been resolved to make the recovery task work whenever the agent is consuming too much resources.

• The DiscoverAgentPatches.ps1 script in Microsoft.SystemCenter.Internal.xml fails and you experience the following exception:

Exception:
Method invocation failed because [System.Object[]] does not contain a method named ‘op_Subtraction’.
At C:\bin\scripts\patch.ps1:37 char:35
+ for($count = 0; ($productList.Count-1); $count++)
+ ~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (op_Subtraction:String) [], RuntimeException
+ FullyQualifiedErrorId : MethodNotFound

• An execution policy has been added as unrestricted to PowerShell scripts in Inbox management packs.
• SQL Agent jobs for maintenance schedule use the default database. If the database name is not the default, the job fails.
• This update adds support for OpenSSL1.0.x on AIX computers. With this change, System Center Operations Manager uses OpenSSL 1.0.x as the default minimum version supported on AIX, and OpenSSL 0.9.x is no longer supported.

How to obtain Update Rollup 3 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 clickControl 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 a later version, follow these steps:
7. Click Start, and then clickSettings.
8. In Settings, clickUpdates & Security.
9. On the Windows Update tab, clickCheck Online for updates from Microsoft Update.
10. Click Important updates are available.
11. Select the update rollup package, and then click OK.
12. Click Install updates to install the update package.

Manual download

Go to the following websites to manually download the update packages from the Microsoft Download Center: 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 servicesMicrosoft 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 the System Center 2016 Operations Manager Server (KB4016126) 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 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.
• Install this update rollup package within a few hours after you install the System Center 2016 Operations Manager server.
• 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
   * Web console server role computers
   * Gateway
   * Operations console role computers
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 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 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.Visualization.ServiceLevelComponents.mpb
* Microsoft.SystemCenter.ACS.Internal.mp
* Microsoft.SystemCenter.DataWarehouse.Report.Library.mp
* Microsoft.SystemCenter.Visualization.ServiceLevelComponents.mpb
* Microsoft.SystemCenter.ACS.Internal.mp
For information about how to import a management pack from a disk, see How to Import an Operations Manager Management Pack 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 Update Rollup 2 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 3 to your System Center 2016 Operations Manager environment.
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
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 theUNIX/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
{DDBE1ED2-862B-4D34-B248-F1659BE6034F}	Agent	amd64	en
{C643876F-311B-451F-98D9-3FC433CDDFC4}	Console	amd64	en
{1D959DDF-C441-4C12-AAE6-5BEE5ABD6584}	WebConsole	amd64	en
{9182B3E8-C139-49A6-97CC-1B9310053053}	Gateway	amd64	en
{997B7B7E-01A2-460C-9F48-3F0BF3FE8622}	Server	amd64	en
{9D0DB2A0-92BA-41C9-8CDF-BA66101CDE5E}	Agent	x86	en
{EFD5D573-BA1E-424A-8CB7-B493C723E027}	Console	x86	en
{04627346-17C6-472B-808A-42BABA80CF3B}	Console	amd64	cn
{4626EC88-91DB-4B30-AE5F-05B7D2D20773}	WebConsole	amd64	cn
{90FC427B-A140-4B99-83A6-FE3E2FFE7B12}	Console	x86	cn
{E7FB686D-0F2C-4529-ACE5-705DEC4E58A9}	Console	amd64	cs
{CC8D4354-EE12-4C9C-9AA8-082BA64074B0}	WebConsole	amd64	cs
{7537035C-AEA2-491E-AD51-B87E15FB04EB}	Console	x86	cs
{E60D42B3-0B31-4B29-B6C7-44EBEE85162F}	Console	amd64	de
{AB340B8A-4942-4EBA-8E80-B4B8FD930983}	WebConsole	amd64	de
{EB6EE138-B77C-43E6-9085-01AE03BED1D2}	Console	x86	de
{2E2E59F6-C180-4656-864B-92E31734A803}	Console	amd64	es
{0F87E593-A789-4162-BE63-BB52C45E220E}	WebConsole	amd64	es
{6CC8563C-7736-4715-9667-21CCDCC34319}	Console	x86	es
{4FBF27D1-456A-47AA-834B-BBCF2BAE9133}	Console	amd64	fr
{C40ACCE4-BE36-45CC-B2E7-27B1D6C9C7DB}	WebConsole	amd64	fr
{EA38AF56-EFBF-4945-8F69-18B2ED06860D}	Console	x86	fr
{13A04A0C-8F3F-4249-B1A6-5C6171907DFD}	Console	amd64	hu
{E192DC3C-DFB3-4087-87D4-FA11C0B064CE}	WebConsole	amd64	hu
{298C3FE9-E240-4B24-BA84-3E4B5CB2C1CF}	Console	x86	hu
{32F57E40-042B-4F45-BA90-462D5F6CDBC6}	Console	amd64	it
{97399D24-700E-4E48-AB76-E43F86F537D3}	WebConsole	amd64	it
{799E9B77-EE76-407A-BE23-3B452DE5205A}	Console	x86	it
{53F443DE-87F3-4377-AB9E-692D4DD5D431}	Console	amd64	ja
{0AB70C9F-5AB9-4E8C-9557-5F466C8D9108}	WebConsole	amd64	ja
{94836C41-A235-499B-A58D-A84F4AD46FA5}	Console	x86	ja
{17D1A98A-A57C-49B5-88FD-44527BC28482}	Console	amd64	ko
{B2A6AE7A-7FC2-4D0D-AD0D-4440E5F29D11}	WebConsole	amd64	ko
{95783100-5FDB-47C9-AAFE-3A0F9540747D}	Console	x86	ko
{EEF63B1F-E2E5-4584-AE70-918A19522B0B}	Console	amd64	nl
{DBB1775C-391B-4F22-8D51-FBBE320FAF85}	WebConsole	amd64	nl
{F5319EE6-92AD-4A63-9673-463814890B1A}	Console	x86	nl
{8239C333-73EE-40A2-940D-77BBA0390848}	Console	amd64	pl
{C33CF210-9634-42CF-87AB-BA0B5EE1C24F}	WebConsole	amd64	pl
{FDB66706-AA98-4608-881E-4C33D02E8B2B}	Console	x86	pl
{5F4908B9-1B1D-4218-82A7-21B99A364761}	Console	amd64	pt-br
{E0632B27-079F-409E-B9C2-F95A8C3F7AFC}	WebConsole	amd64	pt-br
{74D5015B-E7F9-4B7E-A129-73F360E3A6EE}	Console	x86	pt-br
{AD1275DE-10A0-4718-9250-A0A674165993}	Console	amd64	pt-pt
{41768680-D07B-483B-AFB8-11B7DF316DE1}	WebConsole	amd64	pt-pt
{53228DEC-6EF4-47D3-8B55-9C9A170550E8}	Console	x86	pt-pt
{EEDA248F-661C-4159-8CBE-A73AEC4F8B74}	Console	amd64	ru
{7AE96FBE-C8BB-4D03-A216-E92ED37FCAA6}	WebConsole	amd64	ru
{0B966714-DF4B-412F-A124-107A0FA4B446}	Console	x86	ru
{06DFCFEF-67AD-4B2F-8227-D45170EDC799}	Console	amd64	sv
{5B51A031-9CE4-4057-8DD1-D6315842BE42}	WebConsole	amd64	sv
{81AE120B-2498-4D2C-8A5B-1F4FFA8DA3B1}	Console	x86	sv
{303B4F5B-9AA7-4DF1-8415-DD44118E51C1}	Console	amd64	tr
{41E91E0F-A285-4A3A-BBFD-4DB89CA7BAFE}	WebConsole	amd64	tr
{7A593F77-F90A-42B2-80A6-60ECF0337EF7}	Console	x86	tr
{53EE6DF1-4028-4F3F-8C57-5985DEF3BFA8}	Console	amd64	tw
{D326414D-1172-4BDC-96E0-E12A8502741E}	WebConsole	amd64	tw
{0D9C5AE1-116F-49BC-936A-B2CF1A2A1375}	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}

Files updated in this update rollup

__

Files that are updated in the Operations Manager update

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.Files updated	Version	File size in KB
Microsoft.SystemCenter.DataWarehouse.Report.Library.mp	7.2.11878.0	449
Microsoft.Mom.UI.Components.dll	7.2.11878.0	5649
Microsoft.EnterpriseManagement.Management.DataProviders.dll
*only updated on WebConsole	7.2.11878.0	588
Microsoft.SystemCenter.OperationsManager.AM.DR.2007.mp	7.2.11878.0	31
Microsoft.SystemCenter.OperationsManagerV10.Commands.dll	7.2.11878.0	678
Microsoft.SystemCenter.Visualization.ServiceLevelComponents.mpb	7.2.11878.0	108
Microsoft.EnterpriseManagement.DataAccessService.Core.dll	7.2.11878.0	692
MicrosoftInstrumentationEngine_x64.dll	15.0.0.189	1173
Microsoft.ApplicationInsights.ExtensionsHost_x64.dll	2.2.2.6537	304
Microsoft.ApplicationInsights.Extensions.Base_x64.dll	2.2.2.6536	701
MicrosoftInstrumentationEngine_x86.dll	15.0.0.188	1007
Microsoft.ApplicationInsights.ExtensionsHost_x86.dll	2.2.2.6543	252
Microsoft.ApplicationInsights.Extensions.Base_x86.dll	2.2.2.6542	540
Microsoft.InstrumentationEngine.Extensions.config		1
Microsoft.Diagnostics.Instrumentation.Extensions.Base.dll	2.2.2.6537	29
MomWsManModules.dll	8.0.10970.0	230
Microsoft.SystemCenter.Internal.mp	7.0.8437.7	62.7
Microsoft.SystemCenter.2007.mp	7.2.11878.0	245
Microsoft.SystemCenter.ACS.Internal.mp	7.2.11878.0	43.2
update_rollup_mom_db.sql		40

__

Files that are updated in the UNIX and Linux management packs update

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, refer to the “Files updated in this update rollup” section of all update rollups that were released after your current update rollup.MP/MPB Name	Size in KB	Version
Microsoft.AIX.Library.mp	31.39063	7.6.1076.0
Microsoft.HPUX.Library.mp	31.39063	7.6.1076.0
Microsoft.Linux.Library.mp	31.39063	7.6.1076.0
Microsoft.Linux.RedHat.Library.mp	15.39063	7.6.1076.0
Microsoft.Linux.RHEL.7.CHS.mp	55.39063	7.6.1076.0
Microsoft.Linux.RHEL.7.CHT.mp	55.39063	7.6.1076.0
Microsoft.Linux.RHEL.7.CSY.mp	71.39063	7.6.1076.0
Microsoft.Linux.RHEL.7.DEU.mp	75.39063	7.6.1076.0
Microsoft.Linux.RHEL.7.ESN.mp	67.39063	7.6.1076.0
Microsoft.Linux.RHEL.7.FRA.mp	71.39063	7.6.1076.0
Microsoft.Linux.RHEL.7.HUN.mp	71.39063	7.6.1076.0
Microsoft.Linux.RHEL.7.ITA.mp	67.39063	7.6.1076.0
Microsoft.Linux.RHEL.7.JPN.mp	63.39063	7.6.1076.0
Microsoft.Linux.RHEL.7.KOR.mp	63.39063	7.6.1076.0
Microsoft.Linux.RHEL.7.NLD.mp	71.39063	7.6.1076.0
Microsoft.Linux.RHEL.7.PLK.mp	71.39063	7.6.1076.0
Microsoft.Linux.RHEL.7.PTB.mp	67.39063	7.6.1076.0
Microsoft.Linux.RHEL.7.PTG.mp	71.39063	7.6.1076.0
Microsoft.Linux.RHEL.7.RUS.mp	75.39063	7.6.1076.0
Microsoft.Linux.RHEL.7.SVE.mp	67.39063	7.6.1076.0
Microsoft.Linux.RHEL.7.TRK.mp	67.39063	7.6.1076.0
Microsoft.Linux.RHEL.7.ZHH.mp	55.39063	7.6.1076.0
Microsoft.Linux.SUSE.Library.mp	15.39063	7.6.1076.0
Microsoft.Linux.Universal.Library.mp	15.39063	7.6.1076.0
Microsoft.Solaris.Library.mp	22.39063	7.6.1076.0
Microsoft.Unix.Library.CHS.mp	43.39063	7.6.1076.0
Microsoft.Unix.Library.CHT.mp	43.39063	7.6.1076.0
Microsoft.Unix.Library.CSY.mp	47.39063	7.6.1076.0
Microsoft.Unix.Library.DEU.mp	47.39063	7.6.1076.0
Microsoft.Unix.Library.ESN.mp	47.39063	7.6.1076.0
Microsoft.Unix.Library.FRA.mp	47.39063	7.6.1076.0
Microsoft.Unix.Library.HUN.mp	47.39063	7.6.1076.0
Microsoft.Unix.Library.ITA.mp	43.39063	7.6.1076.0
Microsoft.Unix.Library.JPN.mp	43.39063	7.6.1076.0
Microsoft.Unix.Library.KOR.mp	43.39063	7.6.1076.0
Microsoft.Unix.Library.mp	87.39063	7.6.1076.0
Microsoft.Unix.Library.NLD.mp	47.39063	7.6.1076.0
Microsoft.Unix.Library.PLK.mp	47.39063	7.6.1076.0
Microsoft.Unix.Library.PTB.mp	47.39063	7.6.1076.0
Microsoft.Unix.Library.PTG.mp	47.39063	7.6.1076.0
Microsoft.Unix.Library.RUS.mp	47.39063	7.6.1076.0
Microsoft.Unix.Library.SVE.mp	43.39063	7.6.1076.0
Microsoft.Unix.Library.TRK.mp	47.39063	7.6.1076.0
Microsoft.Unix.Library.ZHH.mp	43.39063	7.6.1076.0
Microsoft.AIX.6.1.mpb	23387.5	7.6.1076.0
Microsoft.AIX.7.mpb	22471.5	7.6.1076.0
Microsoft.HPUX.11iv3.mpb	16333.5	7.6.1076.0
Microsoft.Linux.RHEL.5.mpb	62967	7.6.1076.0
Microsoft.Linux.RHEL.6.mpb	62965	7.6.1076.0
Microsoft.Linux.RHEL.7.mpb	36434.5	7.6.1076.0
Microsoft.Linux.SLES.10.mpb	62964	7.6.1076.0
Microsoft.Linux.SLES.11.mpb	62964	7.6.1076.0
Microsoft.Linux.SLES.12.mpb	31373.5	7.6.1076.0
Microsoft.Linux.UniversalD.1.mpb	62943.5	7.6.1076.0
Microsoft.Linux.UniversalR.1.mpb	62943.5	7.6.1076.0
Microsoft.Solaris.10.mpb	92483.5	7.6.1076.0
Microsoft.Solaris.11.mpb	93340.5	7.6.1076.0