AnnouncementSystem Center Operations Manager

Release Update: RAP as a Service for System Center Operations Manager – January 25, 2018

This service is available for System Center Operations Manager environments running any of the supported versions listed below. The environment must be in a single Management Group to include one or more Management Servers, one Operations Manager Database, and one Operations Manager Data Warehouse.

Please review the content below for details of this release that applies to both “RAP as a Service” and “Offline Assessment.”

New Supportability statements

With April 2017 release, Windows Server 2016 based tool machine are supported.

With April 2017 release, RAP as a Service for System Center Operations Manager is supported on environments running SQL Server Always On using virtual machines hosted on Azure.

With January 2017 release, we started officially supporting the new System Center 2016 Operations Manager.

Supported Versions

  • SCOM 2007 R2
  • SCOM 2012 RTM
  • SCOM 2012 SP1
  • SCOM 2012 R2
  • SCOM 2016 RTM

New Collectors

The “Speculation Control Settings” from the Base.SecurityUpdates.Collection package was added.

New Visualizers

  • NONE

New Analyzers

  • The “SecurityUpdates_SpeculationControl” from the Base.SecurityUpdates.Analysis package was added.

New Reports

  • NONE


  • NONE

Bug Fixing / Updates

  • Discovery:
    • NONE
  • Collectors:
    • Collector Generate datanode for MP Update check was update with the latest MP releases.


  • Content Definitions:
    • Corrected several grammar errors end typos.
  • Analyzers:
    • NONE
  • Visualizers:
    • NONE


  • Survey:
    • NONE


  • Reports:
    • NONE


  • Base Packages:
    • Windows Base Packages
    • SQL Base Packages
    • Monitoring Base Packages
    • Security Base Packages


  • Scom Packages:
    • Scom.UpgradeAdvisor

Known issues:

Here is the list of known issues we have in the current release package:

  • Analyzer “OpsMgr Server: Different Services Accounts” may raise false positive if the displayed name for the service accounts is using different formats (User Principal Name Vs Down-Level Logon Name). The probability of hitting this misfiring is exceedingly rare and if it is experienced, the workaround is to verify with the customer the service accounts and to exclude the issue from being visible and added to the report.


If you have feedback or an idea to share, please visit UserVoice.