Update Rollup 8 for System Center 2016 Operations Manager

Applies to: System Center 2016 Operations Manager

Introduction


This article describesthe issues that are fixed in Update Rollup 8 for Microsoft System Center2016 Operations Manager. This article also contains the installationinstructions for this update.


Improvements and issues that are fixed


  • Fixed: In a scenario where SCOM monitors 100s of virtual machines hosted on a single Hyper-v server; every hour the healthservice.exe of each Virtual machine write into the VM page file simultaneously. Due to this concurrent paging, every hour disk I/O increases and database becomes unresponsive. HealthService.exe now have Memory Trimming enabled by default on an hourly schedule. A registry key is provided to disable the memory trimming and control the duration.

          Registry key is: "HKLM\Software\Microsoft\MicrosoftOperations Manager\3.0\Setup\MemoryTrimming"

         Enable – 0 (Trimming is disabled); 1 (trimming is enabled)

         DelayInSeconds – Time period agent waits to start trimming (default is 120s)

         PeriodInSeconds – Recurring period at which the working set should be  trimmed(default is 3600s)

  • Fixed: Historical data do not appear, if input reporting end time is before group creation time. With this fix, historic data for a group (if data is available for objects in the group) would be displayed irrespective of group creation time.
  • Fixed: Maintenance mode state changes which are recorded in MaintenanceModeStage table requires grooming when table grows. If the table is large, grooming takes longer and the operation times out with SQLTimeOut exception.
  • Fixed: If a group is renamed in a Management pack, then console shows the new value but Powershell command Get-SCOMGroup returns the old name of group. Database Updates functionality was inconsistent for SCOM group renaming through MP and SCOM Console.
  • Fixed: CPU Spike issues because of workflows running on all agents at the same time is addressed through script optimization and removing the sync time.
  • Fixed: If the registry key under “Computer\HKey_Local_Machine\Software\Microsoft\Microsoft Operations Manager\3.0\Setup\UseMIApi” is set and a Unix/Linux Script task without a parameter is executed then this task fails. 
  • Improvement: Sometimes SQLstored procedure “p_SelectForNewTypeCache” takes long time to complete, and SDKservice fails to start. This is fixed and above SQL stored procedure willcomplete faster now.

How to obtain Update Rollup 8 for System Center 2016 Operations Manager


Update packages forOperations Manager are available from Microsoft Update or by manual download.

Microsoft Update

To obtain and install anupdate package from Microsoft Update, follow these steps on a computer that hasan 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 isrunning 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 followingwebsites to manually download the update packages from the Microsoft UpdateCatalog:

 Download the Operations Manager update packagenow.


For information abouthow to download Microsoft support files, click the following article number toview the article in the Microsoft Knowledge Base:

119591 How to obtain Microsoft support files from online services

Microsoft scanned thisfile for viruses. Microsoft used the most current virus-detection software thatwas available 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

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

  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 Managerupdate

To download the updaterollup package and extract the files that are contained in the update rolluppackage, 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 followingpath:

%SystemDrive%\ProgramFiles\System Center 2016\Operations Manager\Server\SQL Script for UpdateRollups

  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 abouthow to import a management pack from a disk, see the Microsoft TechNettopic How to Import an Operations Manager ManagementPack.

Note Management packs are included in theServer component updates in the following location:

%SystemDrive%\Program Files\System Center 2016\OperationsManager\Server\Management Packs for Update Rollups

Nano Agent update

To manually install theupdates to Nano Agent, download the KB3209591-8.0.10913.0-NanoAgent.cab file. You can install this update on aNano Agent system by using the following PowerShell script:

.\UpdateNanoServerScomAgentOnline.ps1

 -NanoServerFQDN <FQDNof target Nano Server>

 -BinaryFolder <Pathwhere the update .cab is already expanded OR path to one or more Nano-agentupdate .cab files>

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

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

 

UNIX and Linuxmanagement pack update

To install the updatedmonitoring packs and agents for UNIX and Linux operating systems, follow thesesteps:

  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 LinuxOperating 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 placeholderrepresents one of the following GUIDs.

 

PatchCodeGUID

Component

Architecture

Language

{E41AF276-3264-4779-B9DA-D0CEEF0DF9A3}

Agent

amd64

en

{9FA804EB-9878-4893-96C7-68A59466846A}

ACS

amd64

en

{C970A0CF-AD3D-46A6-B592-83E4B69FEC4B}

Console

amd64

en

{F9498F52-FAE9-498D-A49D-9D2C6EFEA99A}

Reporting

amd64

en

{A568E206-AF54-4537-94B1-DBC84E20EABA}

WebConsole

amd64

en

{D6D9C007-9827-41B0-AFBC-0D633CFE4952}

Gateway

amd64

en

{ED048F9D-0D7A-4AA3-BD95-3DDA11F4BE93}

Server

amd64

en

{C4C94E10-9D34-4EE9-B38C-589E4A120FBD}

Agent

x86

en

{605C3493-EF79-4A5E-A8B1-978B0D6517A3}

Console

x86

en

{3FDBCE33-7DA8-4053-8508-0A53E0F026BA}

ACS

amd64

cn

{11E82D8F-3FB2-4653-B998-E65080A1FD77}

Console

amd64

cn

{084FA720-4B3C-46DF-A575-597A22BA9F7F}

Reporting

amd64

cn

{420DF59E-36BA-4E68-88B7-554151C49675}

WebConsole

amd64

cn

{0325949C-5E14-48A9-91AC-9E7CEA642139}

Console

x86

cn

{7FA558E1-245F-4822-A911-02310D535419}

ACS

amd64

cs

{95DDC930-5284-49EA-883B-E1C716980F29}

Console

amd64

cs

{C54DDE27-36E3-454D-A3BD-12790D7D4C4E}

Reporting

amd64

cs

{8F82186B-FE57-4DE7-856F-C4BFF3182FFF}

WebConsole

amd64

cs

{E81B386E-8AE3-4CDB-948C-087D81B07FF2}

Console

x86

cs

{D1CDEB9F-3FA1-4703-AA79-131432076ED2}

ACS

amd64

de

{8F3D9D5E-5632-49E5-B33A-1F5F09297D2D}

Console

amd64

de

{8E6AD292-4063-47F3-B86B-181BD31E417B}

Reporting

amd64

de

{03ABC6AF-443A-461E-A837-0783C31BEF5B}

WebConsole

amd64

de

{42135016-60A7-4EB0-82D7-D4DF7E517D04}

Console

x86

de

{EF848C36-5281-4EDA-9C3B-785EE846844D}

Console

x86

es

{FF31A789-6120-4028-A4E0-156362F8CCEB}

ACS

amd64

fr

{73CE911E-19D4-41EC-93F7-2D3EF2635C86}

Console

amd64

fr

{B79F0AA5-7E94-4199-B6BF-540CD6D160D4}

Reporting

amd64

fr

{6FEE1199-4A63-4CBB-9E65-D53E74B3028F}

WebConsole

amd64

fr

{848B0B6B-E233-4D7E-8C25-8B399B0C4918}

Console

x86

fr

{A443578F-7187-429C-B755-11AA53A8F0EB}

ACS

amd64

hu

{339D7935-3D7A-42F1-B78F-12E4BEC15FBF}

Console

amd64

hu

{EB1A3504-3647-4AA1-A8C3-42779E86CAC7}

Reporting

amd64

hu

{EFBAA22B-2F95-4F3D-83F0-28814335112D}

WebConsole

amd64

hu

{A2EF1E08-67AC-45DE-B382-005977523810}

Console

x86

hu

{8C4C4B67-ABED-4487-BEF4-D0A844927040}

ACS

amd64

it

{F4B99ECF-308D-4E2C-9966-63420CC1E0B7}

Console

amd64

it

{0BBAFC2B-8F17-48F0-96D5-CFB028262C2D}

Reporting

amd64

it

{D201A750-E3ED-4B4A-B78D-3C5B460B8778}

WebConsole

amd64

it

{B765A1BA-C39F-4DC6-B710-1EB1E9102972}

Console

x86

it

{A05A83DA-3688-4424-924A-2926B744FAC7}

ACS

amd64

ja

{8F7C229F-54F9-4061-BFDE-AFBC2C633779}

Console

amd64

ja

{813C4EF5-A6B5-471D-ABFC-7C24A514CEF5}

Reporting

amd64

ja

{583A8720-7785-4995-92FA-A4C8D157D0A2}

WebConsole

amd64

ja

{B14CCFAF-2183-49FE-80A3-F8FD1302E06E}

Console

x86

ja

{7269EA35-23B6-4508-A85E-31F1424D1998}

ACS

amd64

ko

{63611995-D3B2-4AB5-8E6E-9EA30FF99CB1}

Console

amd64

ko

{01C4C59F-6CB5-4E3F-BBCB-821A6848CEB7}

Reporting

amd64

ko

{8E3ABB5F-6B16-48EE-85AD-DA836B971C4F}

WebConsole

amd64

ko

{97D5F2AB-9343-439A-9A32-174C2895FF23}

Console

x86

ko

{11DC424D-93A0-441D-BC70-99EE9C6E74EB}

ACS

amd64

nl

{4F9BE39D-FDBF-437E-86A2-8C1D0B2180C9}

Console

amd64

nl

{CFFA1511-0C88-49DF-AE46-6DC379DBF566}

Reporting

amd64

nl

{D0924E79-B433-4C9D-A83D-5ECE3A7C4BCE}

WebConsole

amd64

nl

{21C737E0-04DB-4A5D-BD1C-5DEC25DDF7F3}

Console

x86

nl

{CB9B4B82-8785-4112-9A77-BEB39D526F78}

ACS

amd64

pl

{2675F8A5-4389-45FD-B9E8-A1A0E96EA3A5}

Console

amd64

pl

{5FCDAFBD-6634-48BC-B390-CF61BAD0EB8A}

Reporting

amd64

pl

{06A8A417-FC42-43ED-85F3-89F49F699A2F}

WebConsole

amd64

pl

{11565148-C64B-4F88-B215-5924A6613FE6}

Console

x86

pl

{8B6B5451-33BE-4A1B-BDFA-E8B56E5AC667}

ACS

amd64

pt-br

{6797A82B-DD34-4B0F-8ACC-A0F7441FC5D7}

Console

amd64

pt-br

{C01B95E3-E68A-4DD1-89EC-73B95F925C0E}

Reporting

amd64

pt-br

{F540D3FA-8F55-44B2-9EA6-6A69127FB2F9}

WebConsole

amd64

pt-br

{EF71977A-1CDE-4D74-A876-67C16DC45C61}

Console

x86

pt-br

{B26B0B6D-053B-4447-BFFB-423793D6E1E6}

ACS

amd64

pt-pt

{5B61F0E0-3652-4279-83AA-C4E31B06E051}

Console

amd64

pt-pt

{CBE5464C-F44E-4C32-8088-9BA0DE9E6144}

Reporting

amd64

pt-pt

{D6F7BD29-B1CB-4625-B394-BD79C1589FE5}

WebConsole

amd64

pt-pt

{FAC8DC67-B67F-4BFA-8481-104D4240D21E}

Console

x86

pt-pt

{E435E6D3-483F-4055-85B1-F242E352907D}

ACS

amd64

ru

{2D140FDA-6179-4366-89DA-692C56D9A621}

Console

amd64

ru

{73055D8C-F7F4-4279-A264-1C7AD0A42DE1}

Reporting

amd64

ru

{B1519B09-BC69-47F9-96DE-20ED1F663FC9}

WebConsole

amd64

ru

{7E2F2477-AB9C-454F-AD12-0AE2B4562774}

Console

x86

ru

{2ECD71EA-459A-4EE1-8839-E3B86BBD416C}

ACS

amd64

sv

{E5DAE07D-F597-4180-A601-596FB459B744}

Console

amd64

sv

{33D46D7E-21EB-4E88-82B2-66F6E9E4A348}

Reporting

amd64

sv

{EFB87C12-34DB-46B4-B930-15C2F54DBBA6}

WebConsole

amd64

sv

{9479A5B7-6AD2-4787-811E-B3F2C66B8B1B}

Console

x86

sv

{296922F4-76F8-4F8B-B022-EFA2330D4F3A}

ACS

amd64

tr

{A96D9B1B-A39D-4BD9-8272-7422109A04F2}

Console

amd64

tr

{B4CAB769-2CEE-4CC5-9997-DD4B192910B7}

Reporting

amd64

tr

{8634260B-D2EB-45B8-836F-33C8F2F4B397}

WebConsole

amd64

tr

{F9CF04F5-F96B-4419-A953-1352DF3BB6B0}

Console

x86

tr

{DD35909F-E340-479D-B414-22C4B49E0026}

ACS

amd64

tw

{880C7CD3-2031-46AC-89B3-5EE786ABE2DD}

Console

amd64

tw

{D68798C9-1D50-4DD5-812E-EA737A5392E9}

Reporting

amd64

tw

{D696F1F0-AD87-4F59-A0AA-8B4FC7682AB1}

WebConsole

amd64

tw

{48DC0EC0-1E0F-4F5D-AEEF-04A70FE3632E}

Console

x86

tw

 

 

Additionally, the RTMProductCodeGuid placeholderrepresents 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 listof files that have changed in this update rollup. If you do not have allprevious update rollups installed, files other than those listed here may alsobe updated. For a complete list of files that are updated, see the"Files Updated in this update rollup" section of all update rollupsthat were released after your current update rollup.

Files Updated

Version

File Size

Microsoft.EnterpriseManagement.DataAccessLayer.dll 

7.2.12213.0

2.43MB

MomWsManModules.dll

8.0.11037.0

222KB

HealthService.dll

8.0.11037.0

3.02MB

UR_DataWarehouse.sql

 

54.7KB

update_rollup_mom_db.sql

 

268KB

Microsoft.SystemCenter.2007.mp

7.2.12213.0

242 KB