Update Rollup 8 for System Center 2016 Operations Manager

• 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\Microsoft Operations 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 SQL stored procedure “p_SelectForNewTypeCache” takes long time to complete, and SDK service fails to start. This is fixed and above SQL stored procedure will complete faster now.
  
  

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 notes

• 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. Run the following SQL scripts on the Database Server against the OperationsManagerDW database. 

1. 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

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

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 the UNIX/Linux Agent Upgrade Wizard in the Administration pane of the Operations Console.