Update Rollup 2 for System Center 2016 Operations Manager

Issues that are fixed in Operations Manager

• When you use the Unix Process Monitoring Template wizard (adding a new template) to monitor processes on UNIX servers, the monitored data is not inserted into the database because of the following failure:
  
  

  Log Name: Operations Manager
  Source: Health Service Modules
  Date:
  Event ID: 10801
  Task Category: None
  Level: Error
  Keywords: Classic
  User: N/A
  Computer:
  Description: Discovery data couldn't be inserted to the database. This could have happened because of one of the following reasons:
  - Discovery data is stale. The discovery data is generated by an MP recently deleted.
  - Database connectivity problems or database running out of space.
  - Discovery data received is not valid.

  The following is the underlying exception that causes this issue:
  
  

• Exception type: Microsoft.EnterpriseManagement.Common.DataItemDoesNotExistException Message: ManagedTypeId = ccf81b2f-4b92-bbaf-f53e-d42cd9591c1c InnerException: StackTrace (generated): SP IP Function 000000000EE4EF10 00007FF8789773D5 Microsoft_EnterpriseManagement_DataAccessLayer!Microsoft.EnterpriseManagement.DataAccessLayer.TypeSpaceData.IsDerivedFrom(System.Guid, System.Guid)+0x385

  
  

• When a management server is removed from the All Management Servers Resource Pool, the monitoring host process does not update the TypeSpaceCache.

• When alerts are closed from the Alerts view after you run a Search, the closed Alerts still appear in the View when the Search is cleared.

• When you press Ctrl+C to copy an alert in Operations Manager Alert view and then press Ctrl+V to paste it to Notepad, the Created time is in UTC time, not local time.

• Groups disappear from Group view after they are added to a Distributed Application.

• IM notifications from Operating Manager to Skype fail when an incorrect exception causes NullReferenceException in the SipNotificationTransport.Send method.

• When the maintenance mode option for the dependency monitor is set to “Ignore,” and the group (consisting of the server to which this dependency monitor is targeted) is put in Maintenance mode, the state of the monitor changes to critical and does not ignore maintenance mode.

• Because of a rare scenario of incorrect computation of configuration and overrides, some managed entities may go into an unmonitored state. This behavior is accompanied by 1215 events that are written to the Operations Manager log.

• Recovery tasks on “Computer Not Reachable” Operations Manager Monitor generate failed logons on SCOM Agents that are not part of the same domain as the management groups.

• The ManagementGroupCollectionAlertsCountRule workflow fails and generates a "Power Shell Script failed to run" alert.

• Get-SCOMGroup cmdlet fails when thousands of groups are created in Operations Manager.

• Organizational unit properties for computers that are running Windows are not discovered or populated. This discovery is part of the System Center Internal Library MP. After this update, organizational unit properties will be discovered for all computers that are running Windows.

• When the Operations Manager Health Service agent starts, and the agent is configured for AD integration, if the agent cannot contact Active Directory at all, it immediately goes dormant and stops trying to connect and obtain the policy from Active Directory.
  

Issues that are fixed in the UNIX and Linux management packs

• SHA1 is deprecated, and SHA256 certificates are now supported on the management server that's used to sign the Unix/Linux OMI certificate.

• OMI does not work on Linux servers configured for FIPS compliance.

• Avg. Physical disk sec/transfer performance counters are not displayed for Hewlett Packard computers.

• OMI displays incorrect Memory information on Solaris 10 computers.

• Network adapter performance is not displayed for SLES 12 x64 platform in the Operations Manager Console.

• Cannot discover file systems on HPUX 11.31 IA-64 computers with more than 128 disks. Previously it supported only 128 VGs. Now support is extended to 256 VGs.

• Deep monitoring cannot be started successfully on some JBoss applications because the discovery of the JBoss application server sets the Disk Path for the JBoss server incorrectly. Deep monitoring was not being started in JBoss stand-alone mode when a nondefault configuration was used.
  

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 of the update package

Go to the following website to manually download the update package from the Microsoft Update Catalog:

 Download the Operations Manager update package now.

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

• Install this update rollup package within a few hours after you install the System Center 2016 Operations Manager server.

• 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

We recommend that you install this update rollup package by following these steps in the given order:

1. Install the update rollup package on the following server infrastructure:

2. • Management server or servers

   • Web console server role computers

   • Gateway

   • Operations console role computers

3. Apply SQL scripts.

4. Manually import the management packs.

5. Apply Agent updates.

6. Apply the Nano Agent update to manually installed agents, or push the installation from the Pending view in the Operations console.

7. 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. Or download from the Microsoft Download 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

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

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 from here. 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>

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 that are updated in the UNIX and Linux management packs 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, refer to the "Files updated in this update rollup" section of all update rollups that were released after your current update rollup.