System Center Operations Manager, version 1807

Applies to: System Center Operations Manager, version 1807

This article describes the issues that are fixed and the improvements that are included in System Center Operations Manager, version 1807. This article also contains the installation instructions for this update.

• Fixes an issue that sometimes cause the Performance widget in the web console to throw an ArgumentException message.
• Fixes an issue that prevented the Alert view URL in the notification channel from to pointing to the new drill-down Alert page.
• Fixes an issue that causes the web console to throw an ArgumentException message when the state widget is added to a dashboard or scoped to a specific group.
• Improvement to the web console so that is now supports nondefault ports.
• Fixes an issue that causes the pseudo file system to be enumerated.
• Fixes an issue that caused the DNS 2016 Management Pack to throw false alerts for "DNS unused Zone Detected."
• Fixes an issue that caused the MySQL version to be listed as "for," "on," or NULL in Detail view for some platforms.
• Improvement that enables Monitoring Solaris 10 Agents (x86) to provide heartbeat alerts and configuration errors about the SSL certificate.
• Fixes an issue that prevented the Operations Manager console, the Service Manager console and PowerShell modules to coexist on the same server.
  
  Note Both Operations Manager and Service Manager must be upgraded to version 1807 to resolve this issue.
• Fixes an issue in which Active Directory Integration rules were not visible or editable in an upgraded 2016 Management Group. This issue prevented the ongoing management of Active Directory integration assignment in the upgraded Management Group.
• Fixes an issue that caused the system and MonitoredBy information to be displayed incorrectly in the Unix/Linux Computers view when the UNIX host name on the server is lowercase.
• Fixes an issue that caused Active Directory integrated agents not to display correct failover server information.
• Fixes an issue in Performance views in the web console that caused the selection of counters not to persist after a web console restart or refresh.
• Fixes an issue in which the PowerShell cmdlet Get-SCXAgent fails and returns a “This cmdlet requires PowerShell version 3.0 or greater” error.
• Fixes an issue in which a group name is changed through the operations console, the Get-SCOMGroup cmdlet does not retrieve the group data that includes the changed group name.
• Fixes an issue that causes error HTTP 500 to occur when you access Diagram view through the web console.
• Improvement in which the SQLCommand Timeout property is exposed so that it can be dynamically adjusted by users to manage random and expected influx of data scenarios.
• Fixes an issue that caused the MonitoringHost process to crash and throw the exception "System.OverflowException: Value was either too large or too small for an Int32."
• Fixes an issue when company knowledge is edited by using the Japanese version of Microsoft Office through the Operations Manager console, you receive the following error (translated into English): "Failed to launch Microsoft Word. Please make sure Microsoft Word is installed. Here is the error message: Item with specified name does not exist.”
• Fixes an issue that causes Microsoft.SystemCenter.ManagementPack.Recommendations to log errors on instances of Microsoft SQL Server that have case-sensitive collations.

Important You must have System Center Operations Manager, version 1801 installed to apply this update.

Operations Manager packages 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. Select Start, and then select Control Panel.
2. In Control Panel, double-click Windows Update.
3. In the Windows Update window, select Check Online for updates from Microsoft Update.
4. Select Important updates are available.
5. Select the update package, and then select OK.
6. Select Install updates to install the update package.

If your computer is running Windows Server 2016 or a later version, follow these steps:

1. Select Start, and then select Settings.
2. In Settings, select Updates & Security.
3. On the Windows Update tab, select Check Online for updates from Microsoft Update.
4. Select Important updates are available.
5. Select the update package, and then select OK.
6. Select Install updates to install the update package.

Manual download

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

• Important You must have System Center Operations Manager, version 1801 installed before you install this update.
• This update package (offered as Server ENU and non-ENU) is available in the following languages from Microsoft Update:
  • Chinese Simplified (CHS)
  • Chinese Traditional (CHT)
  • Czech (CSY)
  • Dutch (NLD)
  • English (ENU)
  • French (FRA)
  • German (DEU)
  • Hungarian (HUN)
  • Italian (ITA)
  • Japanese (JPN)
  • Korean (KOR)
  • Polish (POL)
  • Portuguese (Brazil) (PTB)
  • Portuguese (Portugal) (PTG)
  • Russian (RUS)
  • Spanish (ESN)
  • Swedish (SWE)
  • Turkish (TUR)

• Some components are multilanguage, and the updates for these components are not localized.

• You must run this update as an administrator.

• If you do not 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 the web console, clear the browser cache, and then restart the web console.

• Do not apply an update immediately after you install System Center Operations Manager, version 1807. Wait several hours after deployment of a new management group before you apply any updates.

• If User Account Control is enabled, run the .msp update files at 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 package in the following server infrastructure:
   • Management 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 package and extract the files that are contained in the update 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 Update Catalog.
2. Apply the appropriate MSP files on each computer.
   
   Note MSP files are included in the update 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 in the following path:
   %SystemDrive%\Program Files\Microsoft System Center\Operations Manager\Server\SQL Script for Update Rollups
4. Import the following management packs.
    

   MP	Version
   Microsoft.SystemCenter.Advisor.Internal.mpb	7.3.13261.0
   Microsoft.SystemCenter.HtmlDashboard.Library.CHS.mp	7.3.13246.0
   Microsoft.SystemCenter.HtmlDashboard.Library.CHT.mp	7.3.13246.0
   Microsoft.SystemCenter.HtmlDashboard.Library.CSY.mp	7.3.13246.0
   Microsoft.SystemCenter.HtmlDashboard.Library.DEU.mp	7.3.13246.0
   Microsoft.SystemCenter.HtmlDashboard.Library.ESN.mp	7.3.13246.0
   Microsoft.SystemCenter.HtmlDashboard.Library.FRA.mp	7.3.13246.0
   Microsoft.SystemCenter.HtmlDashboard.Library.HUN.mp	7.3.13246.0
   Microsoft.SystemCenter.HtmlDashboard.Library.ITA.mp	7.3.13246.0
   Microsoft.SystemCenter.HtmlDashboard.Library.JPN.mp	7.3.13246.0
   Microsoft.SystemCenter.HtmlDashboard.Library.KOR.mp	7.3.13246.0
   Microsoft.SystemCenter.HtmlDashboard.Library.mp	7.3.13261.0
   Microsoft.SystemCenter.HtmlDashboard.Library.NLD.mp	7.3.13246.0
   Microsoft.SystemCenter.HtmlDashboard.Library.PLK.mp	7.3.13246.0
   Microsoft.SystemCenter.HtmlDashboard.Library.PTB.mp	7.3.13246.0
   Microsoft.SystemCenter.HtmlDashboard.Library.PTG.mp	7.3.13246.0
   Microsoft.SystemCenter.HtmlDashboard.Library.RUS.mp	7.3.13246.0
   Microsoft.SystemCenter.HtmlDashboard.Library.SVE.mp	7.3.13246.0
   Microsoft.SystemCenter.HtmlDashboard.Library.TRK.mp	7.3.13246.0
   Microsoft.SystemCenter.Internal.mp	7.0.8438.7
   Microsoft.SystemCenter.Internal.UI.Tasks.mp	7.3.13261.0
   Microsoft.Unix.ConsoleLibrary.mp	7.7.1135.0

    

   For information about how to import a management pack from a disk, see the How to import, export, and remove 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\Microsoft System Center\Operations Manager\Server\Management Packs for Update Rollups

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>

Note The UpdateNanoServerScomAgentOnline.ps1 file is available here:

%SystemDrive%\Program Files\Microsoft System Center\Operations Manager\Server\AgentManagement\Nano\NanoServer

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

1. Apply System Center Operations Manager, version 1807 (this update) to your System Center Operations Manager, version 1801 environment.
2. Download the “Microsoft System Center 1807 MP for Unix and Linux.msi” file:
    
   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 either the Update-SCXAgent Windows PowerShell cmdlet or the UNIX/Linux Agent Upgrade Wizard in the Administration pane of the Operations Console.

To uninstall an update, run the following command:

Note The PatchCodeGuid placeholder represents one of the following GUIDs.

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

Learn about the standard terminology Microsoft uses to describe software updates.