Update Rollup 4 for System Center 2016 Operations Manager

Introduction

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

Issues that are fixed and improvements

• When a log file is being monitored by SCOM, Monagent locks the file and won’t allow it to be renamed.
• Adds support for TLS 1.2. For more information about how to set up, configure, and run your environment with TLS 1.2, see the following article in the Microsoft Knowledge Base:4051111 TLS 1.2 Protocol Support Deployment Guide for System Center 2016
• Addresses an issue in which the APM AppDiagnostics console fails to create a Problem Management rule due to a FormatException. The appropriate string is now used for formatting, and theProblem Management wizard can run without issues.
• Resolves an issue that causes a crash of IIS application pools that are running under CLR 2.0 when the APM feature is installed on the server as part of SCOM Agent. The code now uses appropriate memory instructions that are based on the CLR version.
• Failure of GetOpsMgrDBWatcherDiscovery.ps1 script causes the Monitoring Host to crash.
• WMI Health monitor doesn’t work if WINRM is configured to use https only.
• SCOMpercentageCPUTimeCounter.ps1 script generates WMI errors that are caused by Service Principle Name (SPN) configuration issues.
• WMI Health monitor doesn’t work if SPN http://servername is set to a user account.
• Product knowledge of “Windows Cluster Service Discovery” includes an incorrect reference to “Windows NT.”
• After a network outage, the management server doesn’t reconnect to the gateway server if the gateway server was installed with the /ManagementServerInitiatesConnection=True option.
• A configuration change to the network device triggers a rediscover of the device, and this process changes the SNMP agent address.
• The UseMIAPI registry subkey prevents collection of custom performance rules data for all Linux servers.

Known issues

• During Audit Collection Services (ACS) update or removal, the Audit Collection Services Collector Setup wizard is incorrectly titled “System Center Operations Manager 2012 Audit Collection Server.”
• When you access Silverlight dashboards, a “Web Console Configuration Required” message is displayed.

To work around this issue, follow these steps:

1. Click **Configure** in the dialog box.
2. When you are prompted to run or save the SilverlightClientConfiguration.exe file, click **Save**.
3. Run the SilverlightClientConfiguration.exe file.
4. Right-click the .exe file, click **Properties**, and then select the**Digital Signatures** tab.
5. Select the certificate that has Digest Algorithm as SHA256, and then click **Details**.
6. In the **Digital Signature Details** dialog box, click**View Certificate**.
7. In the dialog box that appears, click **Install Certificate**.
8. In the **Certificate Import Wizard**, change the store location to**Local Machine**, and then click**Next**.
9. Select the **Place all certificates in the following store** option and then select**Trusted Publishers**.
10. Click **Next** and then click**Finish**.
11. Refresh your browser window.

• After the Update Rollup 4 Agent update is installed, the event log and console view still display “Update Rollup 3” or the Update Rollup 3 Agent version.To verify that the Update Rollup 4 Agent update was installed successfully, verify the version of one of the following binaries:
  • HealthService.dll
  • MomWsManModules.dll
  • MOMModules.dll
    If the binary version is 8.0.10977.0, Update Rollup 4 Agent update is installed.

How to obtain Update Rollup 4 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 later, 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 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 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 this System Center 2016 Operations Manager Server (KB4024941) 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.

• 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
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 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 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 3 to your System Center 2016 Operations Manager environment.

Note There are no UNIX/Linux MP updates in Update Rollup 4.
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 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
{03B1EE57-56A4-487C-BBA9-D0C373DA799A}	Agent	amd64	en
{ADC038C2-FE5B-4FCD-A930-072B69AA5A53}	ACS	amd64	en
{79C3A6E4-C45C-4E87-87DC-FDB623866ACF}	Console	amd64	en
{7585EEC4-7306-410B-B363-0E31636A46C4}	WebConsole	amd64	en
{A661A699-FF2D-47D6-9BF5-E972F0AAB0C9}	Gateway	amd64	en
{6585F585-C61F-4C5B-B4F1-2520FE147E2F}	Server	amd64	en
{1972ADF6-4028-48A8-AFF7-DCD58210578D}	Agent	x86	en
{AD09E4FE-6687-4B50-AB4F-34B5FCD8BA8C}	Console	x86	en
{9FBFD9CC-DD4F-4D77-B7DF-52471ED089DD}	ACS	amd64	cn
{047E7728-53E6-48F4-BA9C-635A4880F154}	Console	amd64	cn
{9C867154-1051-4698-8F4B-B5AFE92E70E4}	WebConsole	amd64	cn
{5729EA9F-8B2C-4161-8FD4-362B894F12E0}	Console	x86	cn
{F595B327-28ED-417C-870D-C6B76C05820B}	ACS	amd64	cs
{AFB16801-8472-4089-B901-89D24E6E6C94}	Console	amd64	cs
{2C6B56B0-4AED-45B6-B6D6-8A6F3072500B}	WebConsole	amd64	cs
{5BE918ED-B832-42C4-A030-0B7E70A1943E}	Console	x86	cs
{828D2174-F04F-49EA-98B4-3F195CD998F1}	ACS	amd64	de
{3A50EA3D-F68E-4166-AE2B-639540351DCB}	Console	amd64	de
{4F70DE98-88A8-4019-8C2C-CA782BA053A3}	WebConsole	amd64	de
{84C2AB97-0EFA-4D1D-891B-138E625E58E2}	Console	x86	de
{719D0A89-0111-486C-B56D-7BCD508B61DA}	ACS	amd64	es
{57A8F663-60F3-4B60-B04F-1FF317CB7101}	Console	amd64	es
{500CECBD-1EAA-4C66-9015-8C408857BEEA}	WebConsole	amd64	es
{0BFCDAD0-DC27-43F7-B5E5-C195DB9FFC88}	Console	x86	es
{6A309F55-C603-4687-B3EE-0D4F337A02F5}	ACS	amd64	fr
{FB7A9E02-FFE4-43EF-81F9-1434A581C50B}	Console	amd64	fr
{B03156EA-E843-4188-BFA9-235D3879DAD4}	WebConsole	amd64	fr
{8659A2F9-93C5-4A4F-B911-90E68A229CCA}	Console	x86	fr
{598EA1BC-1A6F-49C2-BF7B-E299856CE789}	ACS	amd64	hu
{1D123F85-135A-42D4-8871-25BDF5C72A4C}	Console	amd64	hu
{1FDA9CA7-555A-42C0-AEBC-C5F9D4570E36}	WebConsole	amd64	hu
{5B67FA3E-AA8A-4850-AA41-25F26A8B2547}	Console	x86	hu
{569DD1B4-5BAA-4E78-B572-DA88346C370C}	ACS	amd64	it
{2EF98FE7-F734-4266-B81D-8181084423DA}	Console	amd64	it
{CEAF73DF-EE15-4986-AFB5-75A44C3E493B}	WebConsole	amd64	it
{FACBB335-05B9-4DFB-87DD-A8A28AE47B16}	Console	x86	it
{76333BA8-1AC7-47F3-9796-BBCD1DF2043E}	ACS	amd64	ja
{DE4606BB-8672-41F0-A83C-0F47E77F5A80}	Console	amd64	ja
{A662599A-13CE-47C0-91C5-57B2A41F415C}	WebConsole	amd64	ja
{B78219DC-3B8A-46A0-A428-0049476BA5D3}	Console	x86	ja
{27436EA8-E668-4D9D-9CE4-44DE114C26D0}	ACS	amd64	ko
{0A7651AA-540F-4905-BF3F-D7264598F9E7}	Console	amd64	ko
{256EF6CE-A332-4B6E-B2A9-EA56D7BB2F62}	WebConsole	amd64	ko
{7166F8A4-C22A-4239-9BCA-80895CD9850B}	Console	x86	ko
{C8F48244-07D5-48BC-96D4-F86D72DB0D46}	ACS	amd64	nl
{BAC5E2D8-050A-4073-AE99-54FD362B6185}	Console	amd64	nl
{E9EB8556-28A2-4D6E-961C-CD15208CE32E}	WebConsole	amd64	nl
{FA072A3D-775F-4A6A-9C86-1F54904E48F4}	Console	x86	nl
{EE5CBCFF-517D-4666-A2B8-33B2BA9E0E0E}	ACS	amd64	pl
{4711F1BC-BC61-4956-91D3-E9184935B657}	Console	amd64	pl
{0C330D37-48AC-4944-8F63-F8B9DAD85497}	WebConsole	amd64	pl
{01D916F4-A614-48E1-8177-C405B413652E}	Console	x86	pl
{AC0E7859-19D3-462C-BDCA-48CABBA313C9}	ACS	amd64	pt-br
{6AB7CF74-D6BC-44D0-96C6-60F9DD9F022B}	Console	amd64	pt-br
{0058179E-7AEF-42EE-84AD-FD981859ED40}	WebConsole	amd64	pt-br
{2C299005-85E8-4538-B662-0FDC17A76086}	Console	x86	pt-br
{4FE66AB2-BDE0-4950-8D90-F66E0CC1FCA6}	ACS	amd64	pt-pt
{268CD2C7-C288-42DA-8EDC-9325C6F17AE3}	Console	amd64	pt-pt
{6FACB9B9-FA54-442F-9D2D-B0A4BFBD0003}	WebConsole	amd64	pt-pt
{8C4712CA-A1DA-4294-A8B6-73183C714A80}	Console	x86	pt-pt
{B464B1CD-C576-4A4A-B3B0-6F2ECF29E8A3}	ACS	amd64	ru
{E73084CB-3B02-4F91-BE00-F0368C87E385}	Console	amd64	ru
{09D8BC3F-C5E0-4062-9542-8F148D3B9549}	WebConsole	amd64	ru
{53A8C62D-CF6B-42F5-8123-AEF2E640D4F1}	Console	x86	ru
{B7E982BF-BCA1-4A29-A3A9-3D9F9D41E7F2}	ACS	amd64	sv
{1A22F3E7-39E3-4689-A057-2006972E28E7}	Console	amd64	sv
{8DBC82FC-0241-4A30-BD9A-3572675BD098}	WebConsole	amd64	sv
{7015286A-ACB3-48A8-BEEB-3006A1043CFE}	Console	x86	sv
{A0F68DE9-7BC8-493C-A509-F1E0597896B8}	ACS	amd64	tr
{0408A0F6-1DCB-40A1-A481-A8CC28B80704}	Console	amd64	tr
{1A0B0333-4050-4B9F-995B-4FE4B8CF6231}	WebConsole	amd64	tr
{6291D3C3-06FC-4AC4-85BC-C311D87C5138}	Console	x86	tr
{E5C76D0F-DB7C-44B2-8B26-2D347F65DB7D}	ACS	amd64	tw
{D6B36A82-B345-4F49-AB92-C54DB669DC85}	Console	amd64	tw
{32F9F639-E3AD-4135-9274-6D25102494E6}	WebConsole	amd64	tw
{B2699733-E1D6-4487-B15F-116C973D3273}	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

__

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 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
MomWsManModules.dll	8.0.10977	229KB
MOMModules.dll	8.0.10977	2.34MB
Microsoft.Mom.Sdk.Authorization.dll	7.2.11938.0	191KB
AdtSrvDll.dll	7.2.11938.0	490KB
MomNetworkModules.dll	8.0.10977.0	735KB
AX5OleDb.dll	7.2.11938.0	60.7KB
Microsoft.Mom.ServiceCommon.dll	7.2.11938.0	36.2KB
Microsoft.SystemCenter.Library.mpb	7.0.8437.10	184KB
Microsoft.SystemCenter.Apm.Infrastructure.mpb	7.2.11938.0	1208KB
AX5Base.dll1	7.2.11938	81.2KB
SEMWebViewer.dll	7.2.11938	1.68MB
PerfMon.dll	8.0.10977	1.96MB
PerfMon64.dll	8.0.10977	2.98MB
Microsoft.SystemCenter.Internal.mp	7.0.8437.10	63.7KB
Microsoft.SystemCenter.2007.mp	7.2.11938.0	249KB
Microsoft.Windows.Cluster.Library.mp	7.0.8437.10	28KB
momconnector.dll	8.0.10977	659KB
SEMCore.dll	7.2.11938.0	1MB
ARCore.dll	7.2.11938.0	701KB
sm-auto-discovery.dll	7.2.11938.0	4.28MB
1 Only updated on the Web Console