Release notes for System Center Operations Manager

This article lists the release notes for System Center 2019 - Operations Manager. This article also includes the release notes for Operations Manager 2019 UR1 and 2019 UR2.

Operations Manager 2019 release notes

The following sections summarize the release notes for Operations Manager 2019, and include the known issues and workarounds. See also, 2019 UR1 and 2019 UR2 release notes.

Health Service with Log on type as Service by default

Description: With Operations Manager 2019, Log on as a Service feature is enabled by default. This change impacts all the service accounts and Run As accounts, they must have Log on as a Service permission.

Workaround: Enable log on as a service permission for these accounts. Learn more.

User experience changes in maintenance mode

Description: The following are the user experience changes with Operations Manager 2019 maintenance mode. These changes are applicable to both Windows and Linux\Unix monitoring:

  • As an entity enters the maintenance mode, monitor-based active alerts on it will be automatically resolved. In earlier releases, these alerts get automatically resolved when the entity exits the maintenance mode.

  • On-demand monitors and regular monitors now behave similarly when target entity enters and exits the maintenance mode.

Workaround: None

Support for x64 components

Description: Operations Manager 2019 supports only x64 components, x86 components aren't supported. If you try to push install the agent from the console to a x86 computer, the following error message appears:

The system cannot find the path specified.

Workaround: None

Upgrade to reporting server fails the prerequisites check

Description: While attempting to do an upgrade of System Center 2016/1801/1807 - Operations Manager reporting server to version 2019, the prerequisites check reports the following error: 

Management Server Upgraded Check - The management server to which this component reports, has not been upgraded. and the upgrade cannot proceed.

This error occurs in a distributed management group scenario, where the reporting server is on a server that is different from one or more management servers in the management group.

Workaround: Install the System Center 2016/1801/1807 - Operations Manager Operations console on the server that is hosting the reporting server role, and then retry upgrading the reporting server role to version 2019. Once the upgrade is successful, you can uninstall the upgraded Operations console from the reporting server.

Internet Explorer compatibility view

Description: The HTML5 Web console doesn't support Internet Explorer compatibility View.

Workaround: None

OpenSSL 1.1.0 version support

Description: On Linux platforms, OpenSSL 0.9.8 support is dropped.

Workaround: We have added support for OpenSSL 1.1.0.

Performance monitoring for VMM server fails with Access denied message

Description: Service users do not have permission to access VirtualMachineManager-Server/Operational event log. Workaround: Change the Security Descriptor for operational event log registry with the command below, and then restart event log service and health log service.

reg add HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-VirtualMachineManager-Server/Operational /v ChannelAccess /t REG_SZ /d O:BAG:SYD:(D;;0xf0007;;;AN)(D;;0xf0007;;;BG)(A;;0xf0007;;;SY)(A;;0x7;;;BA)(A;;0x3;;;NS)(A;;0x1;;;IU)(A;;0x1;;;SU)"

This command will add the service user to the list of allowed users, who can access VirtualMachineManager-Server/Operational event log.

Operations Manager 2019 does not support HPUX library

Description: Operations Manager 2019 does not support HPUX. However, HPUX library is available in the list of management packs delivered for Operations Manager 2019.

Workaround: Ignore this. HPUX is removed from the latest pack on the DLC, here.

Previous AD rules do not work after upgrading to Operations Manager 2019

Description: After you upgrade to Operations Manager 2019 from Operations Manager 2016 (or 2016 URs earlier to UR7), 1801 or 1807, previous AD rules do not work due to the change in Active Directory rules' format. Upgrade to Operations Manager 2019 from Operations Manager 2016 UR7 and UR8 does not have this issue.

Workaround: To resolve this, use the following steps:

  1. After you upgrade to 2019, export the default management pack to a folder.

  2. Open Microsoft.SystemCenter.OperationsManager.DefaultUser.xml from the exported folder.

  3. Rename all the AD rules to use instead of , example below.

    Note

    Domain name is case-sensitive.

    Example:

    Before: Rule ID="_smx.net_MS1_contoso.com" Enabled="true"

    After: Rule ID="_SMX_MS1_contoso.com" Enabled="true"

  4. Import the updated management pack.

    The rules are now visible on the console.

    For detailed information about this issue, see update an active directory integration with Operations Manager.

    Note

    This issue is fixed in 2019 UR2.

REST API in Operations Manager does not return required values for classes

Description: When called from Operations Manager 2019, REST API does not return className, path and fullname, information returned is empty. Also, ID is returned as className.

Workaround: None

Note

This issue is fixed in 2019 UR2.

Operations Manager 2019 UR1 release notes

The following sections summarize the release notes for Operations Manager 2019 UR1, and include the known issues and workarounds.

For the problems fixed in UR1, and the installation instructions for UR1, see the KB article.

Pending management after patching

Description: After you apply the 2019 update rollup (UR1), the agents to be updated are not listed in Pending Management, console view.

Workaround: You need to identify the agents and update them manually. To do this, go to Administration> Device Management>Agent Managed, and update the agents that are of the older version. To view the correct version of the agent, after applying the management server patch, import the management pack as mentioned in the KB article for Operations Manager 2019 UR1.

Version display

Description: Version display does not show UR1 in areas such Help>About and Device Management view.

Workaround: To check if the Operations Manager components are successfully updated for UR1, see the version number of respective components in Administration> Operations Manager Products.

Error while exporting reports post gMSA migration

Description: Post migration to gMSA, while exporting a report in Word, PowerPoint, or Excel format, You may encounter the following error: An error occurred during rendering the report.

This is specifically observed for SQL Server Reporting Services on SQL Server 2017. This error appears to be a persistent issue with SSRS in SQL Server 2017.

Workaround: To resolve this, use the following steps:

  • Grant admin access to Execution account on the report server
  • Restart the reporting service and wait for 5 minutes
  • Try to export the reports again

Note

From SQL Server Reporting Services (SSRS) 2017 version 14.0.600.1274 and later, the default security settings do not allow resource extension uploads. This leads to ResourceFileFormatNotAllowedException exceptions in Operations Manager during deployment of reporting components.

To fix this, open SQL Management Studio, connect to your Reporting Services instance, open Properties>Advanced, and add *.* to the list for AllowedResourceExtensionsForUpload. Alternatively, you can add the full list of Operations Manager's reporting extensions to the allow list in SSRS.

Replacement of previously used service accounts with gMSA fails

Description: Replacement of previously used Operation Manager's service accounts with gMSA fails, leading to Operations Manager's console issues (Console fails to open). This occurs if the data access service is not initialized.

Workaround:

  1. Add the account running the SDK service to builtin\Windows Authorization Access Group.

  2. Run the PowerShell script as detailed here.

  3. If this is a fresh installation of Operations Manager, wait for 24 hours, and then apply the Update Rollup. This is applicable to all roles in Operations Manager.

Note

Ensure that DW and DR accounts are members of the Operations Manager Report Security Administrators group, so the issue does not recur. See gMSA accounts for more information. .

Operations Manager 2019 UR2 release notes

No known issues in Operations Manager 2019 UR2.

For the problems fixed in UR2, and the installation instructions for UR2, see the KB article.

Important

This version of Operations Manager has reached the end of support, we recommend you to upgrade to Operations Manager 2019.

This article lists the release notes for System Center 1807 - Operations Manager.

Operations Manager 1807 release notes

The following sections summarize the release notes for Operations Manager 1807 and include the known issues and workarounds. For more information about version 1807 and what issues are addressed, see KB4133779.

Log rotation for Linux agent

Description: Under certain scenarios, the SCX logs fill up frequently, which eventually consumes all available free space on the system disk. As a result, the system becomes unresponsive unless the logs are cleaned up manually. To address this issue, we have introduced a logrotate feature for SCX agent. This will help you rotate old logs and save disk space.

Prerequisite: Logrotate is located in /usr/sbin/logrotate by default on Linux platforms.

Workaround: During scxagent installation we push the following logrotate conf file to /etc/logroate.d location.

/var/opt/microsoft/scx/log/*/scx.log
{	 
rotate 5
missingok
notifempty
nodatext
compress
size 50M
copytruncate
postrotate
/usr/sbin/scxadmin -log-rotate
all
}

You can change the default values to support your requirements. The default configured values will rotate the scx.log file if scx.log file size reaches 50 MB. We have included one cron config file at /etc/cron.d location. With this configuration, the logrotate process executes every four hours. To customize the configuration, you need to modify these two files. Review the man page for cron and logrotate for further details.

Note

If SELinux is already installed, SCX installer pushes a SELinux module that will enable logrotate. For scenarios where SElinux is enabled after agent installation, you have to import SELinux module for logrotate to work.

Support for SQL Server 2017

Description: With version 1807, SQL Server 2017 is supported only if it is upgraded from SQL Server 2016. A fresh installation of SQL Server 2017 with version 1807 is not supported. If you already have version 1801 deployed with SQL Server 2016, you need to apply Operations Manager version 1807 before performing an upgrade to SQL Server 2017.

Workaround: Before upgrading to SQL Server 2017, review the following article about the upgrade process - Upgrade Operations Manager 1807 databases to SQL Server 2017.

Note

From SQL Server Reporting Services (SSRS) 2017 version 14.0.600.1274 and later, the default security settings do not allow resource extension uploads. This leads to ResourceFileFormatNotAllowedException exceptions in Operations Manager during deployment of reporting components.

To fix this, open SQL Management Studio, connect to your Reporting Services instance, open Properties>Advanced, and add *.* to the list for AllowedResourceExtensionsForUpload. Alternatively, you can add the full list of Operations Manager's reporting extensions to the allow list in SSRS.

Supportability with Internet Explorer Compatibility View

Description: The HTML5 Web console does not support Internet Explorer Compatibility View.

Workaround: None

Support for Operations Manager and Service Manager console coexistence

Description: With System Center version 1801, installing the Service Manager console on a Operations Manager management server wasn't supported. This would cause the SDK service to prematurely stop.

Workaround: To co-locate the Operations Manager and Service Manager console on the same computer, they must be running version 1807.

Upgrade to Operations Manager version 1807

To understand the requirements and steps to successfully upgrade your Operations Manager version 1801 management group to version 1807, review How to upgrade to Operations Manager version 1807.

OpenSSL 1.1.0 version support

Description: On Linux platforms, OpenSSL 0.9.8 support is dropped.

Workaround: We have added support for OpenSSL 1.1.0.

This article lists the release notes for System Center 2016 - Operations Manager.

Operations Manager 2016 release notes

The following sections summarize the release notes for Operations Manager 2016 and includes the known issues and workarounds.

SharePoint integration with Operations Manager has to be recreated

Description: While using SharePoint to view Operations Manager data, the existing Web Console Dashboard URLs provided will not work and these Web parts have to be recreated with the steps below.

Workaround: Perform the following steps to set up SharePoint to view Operations Manager data:

  1. Create a new page on SharePoint in which you want to display the Dashboard.
  2. Open the page and click edit and insert a new Web Part.
  3. In Web Part, under categories select “Media and Content” and under that select “Page Viewer” and click add.
  4. Edit the Web Part and select Web Page and enter the URL of the Operations Manager Web console dashboard.
  5. Append “&disabletree=true” at the end of the dashboard URL for disabling the tree view getting displayed on the SharePoint page
  6. Configure the appearance, layout, and Advance attribute of the SharePoint page.

Web Console might not work due to IIS becoming corrupt

Description: Web Console might throw an error “Could not load type ‘System.ServiceModel.Activation.HttpModule”.

Workaround: Add “HTTP Activation” to the role services of the OS. Then, on Server 2012 – run the following in an elevated command prompt: “C:\Windows\Microsoft.NET\Framework64\v4.0.30319>aspnet_regiis.exe -r”.

Anomalies in handling tables and bullets in Knowledge Articles

Description: If tables are inserted in a knowledge article, when re-editing the knowledge article the borders are not applied to the table. Similarly, if bullets are added in the knowledge article it gets converted to numeric bullets while re-editing. And, if there is a single bullet in the article then the article doesn’t get saved in the MP and the console throws error.

Workaround: None.

MSI-based installation does not work for Nano agent

Description: MSI-based installation is not supported for Nano agent. The agent can be installed from Discovery Wizard\PowerShell installer scripts.

Workaround: None.

Issues with uninstalling an update for Nano agent

Description: Uninstalling an update to Nano agent is not possible.

Workaround Only option is to uninstall the Nano agent, then install the RTM version + desired update.

Issues with updates of Nano agent

Description: Updates to Nano agent will not be pushed from Windows Update. To update Nano agent, you need to either download the available update and install using the PowerShell update scripts; or trigger a repair from an updated Management server.

Workaround: None.

Unable to override the path or folder for Nano agent installation

Description: Nano agent is always installed to the following path: ‘%SystemDrive%\Program Files\Microsoft Monitoring Agent’; the agent installation folder cannot be overridden.

Workaround: None.

Inconsistencies in push install experience of Nano agent

Description: The Discover Wizard status dialog closes but agent stays in pending state in console for some time until the installation fails or completes successfully. Installation may fail, and to help troubleshoot, refer to the setup log file.

Workaround: None.

Inconsistencies in push uninstall experience of Nano agent

Description: When performing a Push uninstall from the Operations console, the status dialog (which shows progress status) shows the uninstall completed successfully, but the agent uninstall is still being performed. Uninstall may fail and refer to the setup log file for further information to troubleshoot.

Workaround: None.

ACS is not working for Nano agent

Description: ACS is not working for Nano agent, in some cases. There are issues in certain scenarios.

Workaround: None.

Client-side monitoring (CSM) alerts might stop flowing from the System Center Operations Manager management server

Description: The update sequence of System Center Operation Manager management server may cause an issue with the client-side monitoring alerts collection from the management server. System Center Operations Manager agents are not affected. Likelihood of occurrence: Medium.

Workaround: Restart the "Microsoft Monitoring Agent" service on System Center Operations Manager management server.

If after updating System Center Operations Manager server or agent, Application performance monitoring (APM) events, client-side monitoring (CSM) events, and APM alerts might stop flowing from the monitored hosts

Description: The update sequence of System Center Operations Manager agent may cause an issue with the following:

• Client-side monitoring (CSM) events and alerts collected on the host.

• Application Performance Monitoring (APM) events and alerts collected on the host. System Center Operations Manager management server is not affected.

Workaround: Restart the "Microsoft Monitoring Agent" service on the System Center Operations Manager agent-managed computer that is experiencing the issue.

Application performance monitoring (APM) for Windows services is not supported in System Center - Operations Manager on computers where Application Insights Status Monitor is installed.

Description: Application performance monitoring (APM) workflow fails to process monitoring configuration for .NET Windows services on the computer if Application Insights Status Monitor and the System Center - Operations Manager agent are both installed.

Workaround: Uninstall Application Insights Status Monitor.

Namespace values for performance tracking will be ignored

Description: Setting the Namespace value for performance tracking when tracking a custom namespace in .NET Applications Performance Monitoring (APM) will be ignored.

Workaround: Set both the exception tracking and performance tracking settings to include the same custom namespaces.

When using sudo elevation with Solaris operating systems, it requires a configuration change if sudo executable is not in an expected path

Description: If you want to use sudo elevation on a computer running Solaris, and the sudo executable is not in the expected path, you need to create a link to the correct path. Operations Manager will look for the sudo executable in the path /opt/sfw/bin, and then in the path /usr/bin. If sudo is not installed in one of these paths, a link is required.

Workaround: The UNIX and Linux agent installation script creates the symbolic link /etc/opt/Microsoft/scx/conf/sudodir to the folder expected to contain sudo. The agent uses this symbolic link to access sudo. The installation script automatically creates the symbolic link, so no action is needed for standard UNIX and Linux configurations. However if sudo is installed in a non-standard location, you should change the symbolic link to point to the folder where sudo is installed. If you change the symbolic link, its value is maintained for uninstall, re-installation, and upgrade operations with the agent.

Operations Manager Console will stop responding if you attempt to resolve a dependency while importing a management pack

Description: When you click Import Management Packs from the Administration workspace of the Operations Manager Operations console, the console will display the Resolve button if the Management Pack is dependent on another Management Pack. If you click Resolve, you see the Dependency Warning. If you click the Resolve button in the Dependency Warning dialog, the Operations console will stop responding.

Workaround: Install the Update for System Center 2016 - Operations Manager. See the Knowledge Base article 3117586 for specific instructions.

Telemetry data may be erroneously sent when the "Usage and Connectivity Data" setting is set to "False"

Description: If two operators have Operations Manager consoles open and one sets the Usage and Connectivity Data setting to "Do not send data" data may continue to flow to Microsoft until the second user closes and reopens their instance of the Operations Manager console.

Workaround: Restart all Operations Manager console sessions after making changes to the Usage and Connectivity setting.

Description: When a new component such as a management server or gateway server are added to an existing Operations Manager environment, usage information about the setup process is sent to Microsoft even though the Usage and Connectivity Data setting is set to "Do not send data". After the component is added, no further usage data will be sent to Microsoft from the component.

Workaround: None

Namespace values for performance tracking will be ignored

Description: Setting the Namespace value for performance tracking when tracking a custom namespace in .NET Applications Performance Monitoring (APM) will be ignored.

Workaround: Set both the exception tracking and performance tracking settings to include the same custom namespaces.

Operations Manager web console is not compatible with Microsoft Edge web browser

Description: When you open the Operations Manager web console from the Windows 10 Start Menu the console will open in the Microsoft Edge web browser. This will result in an error.

Work around: Open the Operations Manager web console with Internet Explorer. Internet Explorer is available from Windows Accessories sub-menu.

Launching the Operations Manager Web Console may result in a blank screen

Description: When you first open the Operations Manager web console you may encounter a blank screen.

Work around: To resolve the issue:

  1. Click on "Configure" button.
  2. When prompted to Run or Save SilverlightClientConfiguration.exe, click Save.
  3. Run SilverlightClientConfiguration.exe.
  4. Open the file properties of exe (right-click) and open the Digital Signatures tab.
  5. Select the certificate with Digest Algorithm as sha256 and click on Details.
  6. In the Digital Signature Details dialog box, Click on View Certificate.
  7. In the dialog box which appears next, click on Install Certificate.
  8. In the Certificate Import Wizard, Set store location as - Local Machine. Click Next.
  9. Select the option - "Place all certificates in the following store" Browse to Trusted Publishers.
  10. Click Next and then Finish.
  11. Refresh the Browser

Important

This version of Operations Manager has reached the end of support, we recommend you to upgrade to Operations Manager 2019.

This article lists the release notes for System Center 1801 - Operations Manager.

Operations Manager 1801 release notes

The following sections summarize the release notes for Operations Manager 1801 and includes the known issues and workarounds.

Telemetry for HTML5 dashboards

Description: System Center Operations Manager collects diagnostics and usage data about itself, which is used by Microsoft to improve the installation experience, quality, and security of future releases. With the release of the new HTML5 dashboards, usage telemetry is collected with Application Insights, not from the Usage and Diagnostic feature in the management group. For more information on what user telemetry is collected by Application Insights, see Usage analysis with Application Insights.

Workaround: Disable the Diagnostic and Usage data collection setting in the Operations console from the Administration workspace under Settings\Privacy.

Edit Company Knowledge

Description: If the company knowledge of an alert/monitor/rule is already saved while editing in the Operations console and then the company knowledge of the same alert/monitor/rule is edited and saved using the new HTLM5 dashboards in the Web console, the content that was saved originally using the Operations console is overridden with the content saved through the Web console.

Workaround: None

Access Silverlight dashboards in Web Console using a different URL

Description: With HTML5 dashboards in Operations Manager 1801, the entire Web console is HTML based. Silverlight dashboards cannot be displayed in the Web console. To access existing Silverlight dashboards, you have to access using the following URL using Internet Explorer with Silverlight enabled - http(s)://<Servername>/dashboard.

Attempting to upgrade Reporting server fails prerequisites check

Description: While attempting to perform an upgrade of System Center 2016 - Operations Manager Reporting server to version 1801, the prerequisites checker will report the following error: Management Server Upgraded Check - The management server to which this component reports has not been upgraded. and the upgrade cannot proceed. This error occurs in a distributed management group scenario where the Reporting server is on a server separate from one or more management servers in the management group.

Workaround: Install the System Center 2016 - Operations Manager Operations console on the server hosting the Reporting server role and then retry upgrading the Reporting server role to version 1801. Once the upgrade is successfully completed, you can uninstall the upgraded Operations console from the Reporting server.

Application Performance Monitoring (APM) agent-component can crash IIS App Pools

Description: The Application Performance Monitoring (APM) feature in System Center Operations Manager version 1801 agent can cause a crash with IIS Application pools and may crash the SharePoint Central Administration v4 application pool running .NET Framework 2.0 and prevent it from starting. This behavior can occur on an IIS web server even if the APM feature has not been enabled and configured after the agent is installed.

Workaround: If the APM feature is not required on the server, reinstall the agent and include the NOAPM=1 parameter on the setup command line to prevent the APM feature from being included. Alternatively, you can reconfigure the agent already installed using Windows Installer repair option and remove the APM component - msiexec.exe /fvomus "\MOMagent.msi" NOAPM=1. For IIS web servers where the agent is already installed but the APM feature has not been enabled and configured, grant the application pool account Read access permission to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\System Center Operations Manager\12\APMAgent. This permissions issue prevents the APM feature from being able to read that key and may cause the application pool process to crash.

In-place upgrade from Operations Manager 2016 will fail if ACS Linux/UNIX MP installed

Description: If you have already installed the Audit Collection Services (ACS) Linux/UNIX management packs, and you are attempting to upgrade from Operations Manager 2016 RTM to the latest update rollup, the upgrade will fail and results in removal of the management server role.

Cause: There is an issue with the installer package during the upgrade process, where setup tries to upgrade the ACS management pack but it has a dependency on the Microsoft.Linux.Universal.Library.MP. If this dependency management pack is not upgraded, importing the ACS MP will fail during the process and the following error is displayed:

Error:Found error in 2|Microsoft.ACS.Linux.Universal|7.7.1124.0|Microsoft.ACS.Linux.Universal|| with message:  
Could not load management pack <ID=Microsoft.Linux.Universal.Library, KeyToken=31bf3856ad364e35, Version=7.7.1103.0>. The management pack was not found in the store.  
: Version mismatch. The management pack (<Microsoft.Linux.Universal.Library, 31bf3856ad364e35, 7.6.1064.0>) requested from the database was version 7.7.1103.0 but the actual version available is 7.6.1064.0.  

The upgrade failure will cause setup to roll back and leave the management server in an inconsistent state where the feature will need to be reinstalled.

Workaround: Before performing the upgrade of the management server, upgrade Microsoft.Linux.Universal.Library management pack or delete the ACS management pack in the management group.

Next steps

What's new in Operations Manager