Update Rollup 10 for System Center 2016 Operations Manager

Applies to: System Center Operations Manager

Introduction


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

Improvements and issues that are fixed


  • ManagementPack Import is now compatible for SCOM 2007 --> SCOM 2016 Upgrade version whenupgraded directly or Indirectly.
  • Theexception which blocked further progress when the user attempted to configureweb application availability monitoring has been fixed.
  • Thesecurity issue regarding reverse tabnabbing has been fixed in the operations managerweb console.
  • Fixedthe Cross-site Scripting (XSS) related security issue in the operations managerweb console.
  • Thecmdlet Export-SCOMEffectiveMonitoringConfiguration has been fixed to give acorrect summary of the applicable monitors, rules and overrides on an object.
  • Quarterlyreport end date will be shown correctly for the first quarter when the “From”field is selected as "First day of previous quarter" and “To” fieldis selected as "Last day of previous quarter”.
  • Reportshave been fixed to not show objects which have been deleted before the selectedstart time.
  • VBscripts for partition and grooming, calculate operations manager free space anddetecting duplicate agent will now run without failure even if SNAC orMSOLEDBSQL are not installed.
  • Theissue regarding the TLS 1.2 compatibility in the OleDB module has been fixed. It is no longer mandatory for the providerelement to be the first reference in the connection string.
  • Fixhas been provided for when the monitor erroneously turned critical due to the URLmodule incorrectly parsing the charset header value.
  • The  .NET API  issue regarding scheduling reportsvia the schedule management wizard has now been fixed.  
  • Performanceimprovement: Added "Recompile" hint to the stored procedures"p_SelectForTypeCache" and "p_SelectForNewTypeCache" thatrun frequently on SCOM DB.

How to download and install Update Rollup 10 for System Center 2016


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

Microsoft Update

To obtain and install an update package from MicrosoftUpdate, follow these steps on a computer that has an Operations Managercomponent 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 forupdates 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 updatepackage.

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

  1. Click Start, and then click Settings.
  2. In Settings, click Updates & Security.
  3. On the Windows Update tab, click CheckOnline 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 updatepackage.

Manual download

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

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

119591 How to obtain Microsoft support files fromonline services.

Microsoft scanned this file forviruses. Microsoft used the most current virus-detection software that wasavailable on the date that the file was posted. The file is stored onsecurity-enhanced servers that help prevent any unauthorized changes to thefile.

Installation instructions for Operations Manager


 Installation notes

  • This update rollup packageis 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 aremulti-language, and the updates for these components are not localized.
  • You must run this updaterollup as an administrator.
  • If you don't want to restartthe computer after you apply the console update, close the console before youapply the update for the console role.
  • To start a new instance ofMicrosoft Silverlight, clear the browser cache in Silverlight, and then restartSilverlight.
  • Do not apply an updaterollup immediately after you install System Center 2016 OperationsManager. Wait several hours after deployment of a new management groupbefore you apply any update rollup.
  • If User Account Control isenabled, run the .msp update files from an elevated command prompt.
  • You must have SystemAdministrator rights on the database instances for the Operational Database andData warehouse to apply updates to these databases.

Supported installation order

  1. Install the update rollup package on the following serverinfrastructure:
    • Management server orservers
    • Audit Collection Services
    • Web console server rolecomputers
    • Gateway
    • Operations console rolecomputers
    • 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 pushthe 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 thefiles that are contained in the update rollup package, follow these steps:

  1. Download the update packages that Microsoft Update provides foreach computer. Microsoft Update provides the appropriate updates according tothe components that are installed on each computer. Alternatively, downloadthe packages from the  Download the Operations Manager update package now.
  2. Apply the appropriate MSP files on each computer.

    Note MSP files are included in the update rollup package. Apply allMSP files that relate to a specific computer. For example, if the web consoleand console roles are installed on a management server, apply the MSP files onthe management server. Apply one MSP file on a server for each specific rolethat the server holds.
  3. Run the following SQL scripts on the Database Server against theOperationsManagerDW database. 

UR_Datawarehouse.sql

  1. Execute the following Database SQL script on the Database serveragainst the OperationsManagerDB database:

Update_rollup_mom_db.sql

Note This script islocated at the following path:

%SystemDrive%\Program Files\System Center2016\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
    • Microsoft.SystemCenter.OperationsManager.Reports.2007.mp
    • Microsoft.SystemCenter.OperationsManager.Infra.mp

 For information about how to import a management packfrom a disk, see the Microsoft TechNet topic How to Import an Operations Manager Management Pack.

Note Management packsare included in the Server component updates in the following location:

%SystemDrive%\Program Files\SystemCenter 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 byusing the following PowerShell script:

.\UpdateNanoServerScomAgentOnline.ps1

 -NanoServerFQDN <FQDN of target NanoServer>

 -BinaryFolder <Path where the update.cab is already expanded OR path to one or more Nano-agent update .cabfiles>

 -IsCabExpanded <$true if BinaryFolder path isto an expanded .cab, $false if it is for a packed .cab file(s)>

 -RemoveBackup <$true to remove the previousbinaries from the agent machine>

 UNIX and Linux management pack update

To install the updated monitoring packs and agents forUNIX and Linux operating systems, follow these steps:

  1. Apply Update Rollup 5 to your System Center 2016 OperationsManager environment.

Note There are noUNIX/Linux MP updates in Update Rollup 10.

  1. Download the updated management packs for System Center 2016 fromthe following Microsoft website: System Center ManagementPack for UNIX and Linux Operating Systems
  1. Install the management pack update package to extract themanagement pack files.
  2. Import the updated management pack for each version of Linux orUNIX that you are monitoring in your environment.
  3. Upgrade each agent to the latest version by using the Update-SCXAgent WindowsPowerShell cmdlet or the UNIX/Linux Agent Upgrade Wizard inthe 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

{73F2FE7D-249A-48DA-AD81-FC4321320294}

Agent

amd64

en

{0F4D869C-70AE-40A6-BC46-D0133764E09B}

ACS

amd64

en

{C97A6520-9DEC-4346-B21D-A308AFB8D637}

Console

amd64

en

{F312FDC0-2B99-48C7-8F35-8772EA97D1FF}

Reporting

amd64

en

{0DE603C9-4641-473C-A13E-AF61DE993E22}

WebConsole

amd64

en

{80A701DC-F582-4D4F-AA84-2977608EF82B}

Gateway

amd64

en

{2CD72205-EF20-423A-B3D3-B07DD4174037}

Server

amd64

en

{0BE3AF97-AAD9-48D8-A55D-F714E771CF6F}

Agent

x86

en

{3CD79BA1-E9DC-492A-A234-9EE1318B39C9}

Console

x86

en

{11630D67-5D20-4FD4-9E03-DF436A9256E0}

ACS

amd64

cn

{10994FB9-714A-4076-A441-6A4E0F1CABAA}

Console

amd64

cn

{4AD1381A-7D7D-46CC-A25E-5BC3F0D802FE}

Reporting

amd64

cn

{E211B7C3-009F-42AA-83E6-FD976AEC4CE9}

WebConsole

amd64

cn

{0767EBE9-1522-43FA-A29F-C09F943BAB40}

Console

x86

cn

{70544437-F03A-469B-AC23-ACF0C84FEBA6}

ACS

amd64

cs

{FD8D1BB3-C15C-41B3-ADFE-3FB8C412D1F8}

Console

amd64

cs

{B0681518-AA0C-4DDF-A719-292C6DCDC394}

Reporting

amd64

cs

{866D9C3A-4549-4E54-BACE-53D574C0E078}

WebConsole

amd64

cs

{D30DAEF3-EC89-4D88-93BF-B4C9954BE99A}

Console

x86

cs

{D816170F-F754-4780-96DF-3C00161D8CC4}

ACS

amd64

de

{A73E3E86-6CB5-49F8-8B00-C5E435410A8A}

Console

amd64

de

{6E0A8572-4428-4CBD-9127-E9D374F724C4}

Reporting

amd64

de

{D21721B2-9D8E-4C73-8FF7-73EFD302106B}

WebConsole

amd64

de

{A0DB4EF0-A109-43C9-A3DB-5CCE54C8A7DD}

Console

x86

de

{70CA5FB0-502F-4887-B797-1CDDA87370DF}

ACS

amd64

es

{6456DFEE-364C-4DF2-838A-7A7EB58CCC12}

Console

amd64

es

{971562A9-7DC5-4104-9B51-B534070B6058}

Reporting

amd64

es

{961A652D-B553-480B-8152-349E5B2370E2}

WebConsole

amd64

es

{57DD194A-6AEA-4F39-80F3-DE2E35011CC3}

Console

x86

es

{9EBC87BC-579B-4369-B386-12284F39B5B7}

ACS

amd64

fr

{CAB8D79E-A61B-4ACD-8978-683309B338B5}

Console

amd64

fr

{6DB33DBE-1771-47C6-B57C-D5EF03E4B7A9}

Reporting

amd64

fr

{3141560C-88AE-4A50-A3EE-A4B618E2DF60}

WebConsole

amd64

fr

{06C3793C-6B52-41F2-866B-96C048481273}

Console

x86

fr

{AAA0E4F9-7B09-4FE9-A035-7140A6B31F06}

ACS

amd64

hu

{C8A789F1-2FEA-4ECA-8E57-25CBC2B1E3F6}

Console

amd64

hu

{1DCC8112-6876-4E36-9960-11DB0C324F51}

Reporting

amd64

hu

{C1C98C6C-0017-49E9-8A5A-FBAA741E9B56}

WebConsole

amd64

hu

{169A2A95-98F3-4196-93C7-15835B21B254}

Console

x86

hu

{394DEAC6-DF93-49BD-BCE8-270C5E7CE2FE}

ACS

amd64

it

{002F2EC0-50F3-4590-9FC3-BEB629373D34}

Console

amd64

it

{D88A1E84-BEEE-484A-B936-5A80E1CA7877}

Reporting

amd64

it

{56044DA9-D967-40AE-9A1A-F3760CA173FB}

WebConsole

amd64

it

{AF212A1E-E197-4EE1-A462-BF88803A7E3C}

Console

x86

it

{B02FC47E-7A0A-4B0E-A21F-658F4D817560}

ACS

amd64

ja

{253B70F1-5796-486C-8A17-84944C88C5EA}

Console

amd64

ja

{F5F09D6B-EC5A-42AB-8B6F-14F9F1272BC1}

Reporting

amd64

ja

{F35110B7-874D-46FA-9357-A139616F5849}

WebConsole

amd64

ja

{063686BA-6317-4788-B65F-2F8960DC12F2}

Console

x86

ja

{D07D9486-470C-4DBB-BBDD-5C6658F1C98E}

ACS

amd64

ko

{546210EE-1E01-429C-B62E-4A745C984959}

Console

amd64

ko

{106CC72A-37AF-4EA5-BB03-F7B5E2760AAD}

Reporting

amd64

ko

{ED56ECB1-5A01-48BE-B456-3EC5E1FCDBA2}

WebConsole

amd64

ko

{08CFD54B-2B27-479D-B5D3-35651D5122A7}

Console

x86

ko

{C697A0C1-93FC-496C-A96C-B4FE4BA4ED12}

ACS

amd64

nl

{2EE7FE00-F4DD-40BE-80FE-ACFB18B55831}

Console

amd64

nl

{2191F11E-0D90-45B5-8E6B-19C46DCF611A}

Reporting

amd64

nl

{EE52DB9A-6090-4FCA-9E41-41A8444DCBAC}

WebConsole

amd64

nl

{5CB93132-98F1-45DE-A13E-280523C143C9}

Console

x86

nl

{DF02E6AE-CEEC-4D32-BE5C-8610F1EC9DB9}

ACS

amd64

pl

{0D5F1138-46F3-43FD-9821-0B6279DD2D9C}

Console

amd64

pl

{6D7AE0D2-4951-4D2D-9C7E-7A161BCA9ABB}

Reporting

amd64

pl

{89BC4B42-DFB1-42BE-B545-EB09043337AC}

WebConsole

amd64

pl

{2F1D6380-D006-48D0-8BA4-3EE02E9BE44E}

Console

x86

pl

{B423A3BB-CF30-4D02-8BAB-D6C20225CF50}

ACS

amd64

pt-br

{A716345F-07C1-4E7B-A20B-E806C58F9EF8}

Console

amd64

pt-br

{3970A4E7-630D-4F5A-AE82-A2F6CF4ECC7C}

Reporting

amd64

pt-br

{3C3C2C8B-D06F-4DE7-84C2-F892AD96D9C3}

WebConsole

amd64

pt-br

{A51FB22C-72E2-4E63-B9DF-1247D6295698}

Console

x86

pt-br

{FEC88AE8-DBD8-4E17-A85A-9C496C0A288C}

ACS

amd64

pt-pt

{165C631A-6D3E-4C1C-ADE5-61EC170FF268}

Console

amd64

pt-pt

{6378CCEC-F6BE-43FE-8DC2-EE701CD779AF}

Reporting

amd64

pt-pt

{4B8E3C67-97DB-4E16-83D2-71AF5967FDE9}

WebConsole

amd64

pt-pt

{D4E2FF5E-CEB9-49C8-BFAB-5008276203F9}

Console

x86

pt-pt

{4E8A64AB-4207-4FF0-8145-4BA4BD6D4B6A}

ACS

amd64

ru

{3CFCB4DE-5268-45C6-A3AF-C87F83F4DF58}

Console

amd64

ru

{015A180A-EB6A-4FF3-987E-E61AE8597A9D}

Reporting

amd64

ru

{960C1512-1C6E-41F1-BC08-97D97D90E9EF}

WebConsole

amd64

ru

{B9A18969-72A8-4FBE-A764-23C226125056}

Console

x86

ru

{FF8CB88D-CFC7-4F4E-B826-2F011F7A1718}

ACS

amd64

sv

{EE89091A-D6D0-47E2-A027-61B020A4ADA7}

Console

amd64

sv

{0C07A777-DA3D-45E5-AEEE-13BC1AB1B296}

Reporting

amd64

sv

{FAF9A432-1800-4F66-88BE-4B03AF6A71C5}

WebConsole

amd64

sv

{9A9E231A-2D54-4366-A20A-036506A36AC6}

Console

x86

sv

{26C73101-2B38-4A49-BFBB-0DB072485F1B}

ACS

amd64

tr

{0789D765-B58C-497B-BF78-D43332D0C47C}

Console

amd64

tr

{4626BE86-58FA-4AB5-A87D-CA3C8C7C3ECA}

Reporting

amd64

tr

{11E8029C-1990-40E1-8E29-C8C95F39F3AE}

WebConsole

amd64

tr

{CFD745BB-5546-45F2-B245-FAB1F5A063CE}

Console

x86

tr

{B227F96C-F954-4353-AEA5-A6846A3C44BC}

ACS

amd64

tw

{C82CAA59-E37F-4B2D-9017-1E21AAEB9A71}

Console

amd64

tw

{054925B3-EF7B-4937-BCBA-B9F0031E0118}

Reporting

amd64

tw

{96D1D3DA-D6C5-473D-B6C8-60B48668BE43}

WebConsole

amd64

tw

{4722827C-5506-463A-A887-DA8392C43ECF}

Console

x86

tw

  

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

Component

RTMProductCodeGuid

server

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

ACS

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

Console amd64

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

reporting

{8BA0D6E8-6A38-4330-AA6F-CF047DD4DC95}

webconsole

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

Agent amd64

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

gateway

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

Agent X86

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



Files updated in this update rollup


The following is a list of files that have changed inthis 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 offiles that are updated, see the "Files Updated in this updaterollup" section of all update rollups that were released after yourcurrent update rollup.


FileName

Version

File Size

ARViewer.dll

7.2.12324.0

911KB

Microsoft.EnterpriseManagement.Reporting.Code.dll

7.2.12324.0

44.9KB

Microsoft.MOM.UI.Common.dll

7.2.12324.0

2.21MB

Microsoft.EnterpriseManagement.DataAccessService.OperationsManager.dll

7.2.12324.0

570KB

MOMNetworkModules.dll

8.0.11057.0

729KB

Microsoft.EnterpriseManagement.DataAccessLayer.dll

7.2.12324.0

2.43MB

Microsoft.EnterpriseManagement.OperationsManager.MonitoringViews.dll

7.2.12324.0

1.75 MB

ViewTypeOverview.aspx

7/8/2020

9.23KB

update_rollup_mom_db.sql

10/27/2020

388KB

Microsoft.SystemCenter.WebApplicationSolutions.Library.mpb

7.2.12324.0

280KB

Microsoft.SystemCenter.DataWarehouse.Report.Library.mp

7.2.12324.0

442KB

Microsoft.SystemCenter.OperationsManager.Infra.mp

7.2.12324.0

66.9 KB