Update Rollup 6 for System Center 2016 Operations Manager

Introduction

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

Improvements and issues that are fixed

• Application pool crashes and SharePoint application crashes because of APM agent and the profiler are now fixed. These occurred because the profiler was always on. This issue is fixed by disabling the profiler by default and enabling it only when APM is configured.
  
  Note If you’re using APM, restart IIS after you deploy the patches.

• Improved logging to display error messages and suggest that you check performance counters when PdhExpandWildCardPath fails.

• Fixed: Session Events tab in Application Diagnostics web console doesn't display any data.

• Fixed: Scheduled Maintenance Mode doesn't work in an availability group that uses SQL Always-On configuration. In case of a failover to a secondary node, the Maintenance Mode Schedules that are created on the primary node don't run. This has now been fixed. For details, see the "Enabling Schedule Maintenance Mode with SQL Always ON" section.

• Updated fix: The Get-SCOMGroup cmdlet is slow to query large (more than 2,000) groups. A previous fix has been improved for faster querying of any number of groups.

• Fixed: Users could not edit the Maintenance Schedule in the SCOM console if all the objects were removed. The schedule can now be edited. However, it cannot be saved unless it contains at least one object.

• Fixed: SCX cannot connect with Linux machine if the KEX algorithms are configured as any of the following: ecdh-sha2-nistp256, diffie-hellman-group-exchange-sha256, or diffie-hellman-group14-sha256.

• Fixed: Using MI APIs causes MonitoringHost.exe to crash. This event is logged in the Application log, but no crash events are reported in the Operations Manager event log. After this fix, MonitoringHost doesn’t crash even if the useMIAPI registry key is enabled.

• OMS (now Azure Log Analytics) connection onboarding wizard isupdated to communicate with the new APIs. This is because the OMS services were moved to the Azure Portal (link), and also because of the planned retirement of the OMS portal. This change will not affect any existing connection to OMS. However, for new connections or to reconfigure existing connections, the relevant management packs that are bundled together with this update rollup must be imported.

• This update rollup creates a new "omi" user (system account).

• XPlat support matrix changes:

  • SLES 10 is not supported.

  • CentOS 5 is not supported.

  • AIX 6.x is not supported.

Enabling Schedule Maintenance Mode with SQL Always ON

The Scheduled Maintenance Mode feature was shipped in Operations Manager 2016 RTM. Therefore, customers have Operations Manager deployments that have SQL always ON enabled for high availability. Multiple customers and blogs have reported that the Schedule Maintenance Mode capability does not work together with SQL Always On when the SQL Server failover occurs.

Schedules that are created by having SQL Always ON enabled were inaccessible when SQL Server fails over to another server.

The fix for this problem enables the schedules to work without any issues even in a SQL Server failover scenario.

We have resolved this problem in the following manner:

• Schedules that were already been created before this fix is deployed will also start working without any issues even in SQL Server failover scenarios.
  
  Note Existing schedules that have been created on the current server that is running SQL Server will be migrated. To migrate the existing schedules that are created on another server, follow the installation instructions.

• Any schedule that is created after you deploy this update together with the required configurations would be accessible even if the server that is running SQL Server fails over to a different server.

Verify that the required permissions are granted on all servers

• The accounts that are listed under the “Operational Database Account” profile should have “SQLAgentOperatorRole” and “db_owner“ permissions on the MSDB database.

• If any accounts that are listed under the “Operational Database Account” profile do not have access to the “SQLAgentOperatorRole” and “db_owner“ permissions on the MSDB database, assign the “SQLAgentOperatorRole” and “db_owner“ permissions on the MSDB database to each account under the "Operational Database Account" profile.

• If you do not have any accounts listed under the “Operational Database Account” profile, accounts that are available under the "Default Action Account" profile should have the “SQLAgentOperatorRole” and “db_owner“ permissions on the MSDB database.

Installation instructions

To install this update rollup, follow these steps:

1. Grant the required permissions, as described in the "Verify that the required permissions are granted on all servers" section.

2. Install the UR6 patch (deploying Management Server and agent components is mandatory).

3. Run the Update_rollup_mom_db.sqlSQL script on the server that is running SQL Server.
   
   Note Existing schedules are migrated to the new design only one time as part of the update rollup deployment. Migration of existing schedules will not occur again when you run the same script.

Guidelines

• Any failures that occur when existing schedules are migrated are captured in the following database table:
  
  [OperationsManager].[dbo].[MaintenanceModeSchedulesMigrationLogs]

• Existing schedules that have been created on a SQL Server-based server that is not the primary server are not migrated to the new design after you run the Update_rollup_mom_db.sql script. Corresponding failures are logged in the database table that is mentioned in the previous item.

• To migrate existing schedules to the new design, fail over your current database to the specific server that is running SQL Server, and run the following scripts against the Operations Manager database.
  
  To migrate a specific schedule to the new design:

EXEC [dbo].[p_MaintenanceScheduleMigrateSchedule] '<ScheduleIDOftheMMSchedule>'

Example:

EXEC [dbo].[p_MaintenanceScheduleMigrateSchedule] '1A6917C6-999C-E811-837B-02155DC77B3F'

To migrate all the existing schedules in the specific SQL server to the new design:

Delete [OperationsManager].[dbo].[MaintenanceModeSchedulesMigrationLogs]
EXEC [dbo].[p_MaintenanceScheduleMigrateExistingSchedules]

• You can run the scripts that are mentioned in the previous item on different servers that are running SQL Server to migrate existing schedules that are created on different servers.

• To prevent any similar issues from occurring, you can delete the existing schedule and re-create that same schedule after you apply the fix.

Note After you deploy this fix, maintenance schedules might be triggered and have a maximum delay of 5 minutes. This maximum delay is configurable by overriding the “Maintenance Mode” rule. The default value is 5 minutes to avoid causing a large performance decrease on the system.

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

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

Installation instructions for Operations Manager

Installation notes

• Important If you want to be able to uninstall this update rollup later, you must have the System Center 2016 Operations Manager Server (KB3209591) update installed before you install this System Center 2016 Operations Manager Server (KB4459897) 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 installation order

Use this procedure to follow all the necessary steps in the appropriate order to install the update rollup package:

1. Install the 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 and 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 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

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

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 placeholder represents one of the following GUIDs.

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

Files updated in this update rollup