Microsoft Operations Manager

from Wikipedia, the free encyclopedia
System Center Operations Manager 2012: main parts of the product

The Microsoft Operations Manager (MOM or SCOM) is a server product from Microsoft . It offers performance monitoring, event displays and evaluations and application-specific log files for hardware and software. The current version is Microsoft System Center Operations Manager 2019 . The main focus of the product is the monitoring of Microsoft infrastructures. With the 2012 version, systems such as Linux and Solaris were also integrated.

The software is integrated into the manufacturer's System Center product family and has, among other things, interfaces to the System Center Configuration Manager (SCCM) and System Center Virtual Machine Manager .

Network management systems such as the System Center products are among the more complex products in the software sector. The implementation of the solutions can be correspondingly complex.

The so-called Management Packs (MPs) are a central point in SCOM . These are supplied preconfigured by Microsoft and other companies and contain a set of rules with limit values ​​for when the monitored software or the system reaches critical values. These can be reported to the administrator in various ways. For the problems reported, MPs also provide information on their possible causes and solutions as well as suggestions for tools that could be suitable for dealing with them. A list of all management packs that can be used by SCOM - number as of April 1, 2020 520 pieces - can be found on the external website Systemcenterwiki.


The product started out as a network management system called SeNTry ELM, which was developed by the UK company Serverware Group plc. was expelled. In June 1998, Mission Critical Software, Inc. acquired the intellectual property rights and renamed the product Enterprise Event Manager. Mission Critical undertook a complete rewrite of the product and named the new version OnePoint Operations Manager (OOM). Mission Critical Software merged with NetIQ in early 2000 and sold the rights to the product to Microsoft in October 2000. It was renamed Microsoft Operations Manager (MOM) - a few years later another version was released under the name Microsoft Operations Manager 2005. Microsoft renamed the product System Center Operations Manager and released the version under the name System Center Operations Manager 2007. System Center Operations Manager - or SCOM for short - 2007 was developed on the basis of new code and although it has similarities with Microsoft Operations Manager does not have an upgrade from previous versions.


A new management group is created when Operations Manager is installed . This management group is the basic functional unit. A management group consists of at least one management server, the operating database and a data warehouse database in which the report data is stored .

  • The management server is used as the central point for managing the management group and communicating with the database. When you open the Operations Console and connect to a management group, you are connected to a management server for that management group. Depending on the size of the computing environment, a management group can contain a single or multiple management servers.
  • The operational database is a SQL Server database that contains all of the configuration data for the management group and that stores all monitoring data that is collected and processed for the management group. The data is temporarily stored in the operating database. They are kept for 7 days by default.
  • The data warehouse database is a SQL Server database that stores monitoring and alerting data for historical analysis purposes. Data written to the Operations Manager database is also written to the data warehouse database so that the reports are always up to date. The data is permanently stored in the data warehouse database.

If the Operations Manager reporting feature is installed, the management group also contains a report server that reports and displays reports from the data in the data warehouse database. These core components of a management group can be installed on a single server or distributed across multiple servers.

Communication between agents and management servers

Software, the so-called Operations Manager Agent, is installed on the system to be monitored.

On a monitored computer, the Operations Manager agent is listed as a Microsoft Monitoring Agent service. The Microsoft Monitoring Agent service collects performance data, performs tasks, and so on. If the service cannot communicate with the management server to which the data is to be sent, the service continues to run and the data and events it collects are written to disk of the monitored computer is written to a queue. When the connection is re-established, the collected data and events are sent to the management server by the Microsoft Monitoring Agent service.

The Operations Manager agent sends the warning and discovery data to the primary management server and writes it to the operations database. The agent also sends event, performance, and health data to its primary management server, which it simultaneously writes to the operations database and the data warehouse database.

The data is sent according to the schedule parameters for each monitoring rule and monitor. With optimized collection rules, data is only transferred if an example of an indicator differs from the previous example by a specified tolerance, e.g. B. 10% differs. This reduces network traffic and the amount of data in the operational database.

In addition, a data packet called a heartbeat is sent from all agents to the management server at regular intervals (by default every 60 seconds). The heartbeat is used to check the availability of the agent and communication between the agent and the management server.

Operations Manager versions

  • Microsoft Operations Manager 2000
  • Microsoft Operations Manager 2005
    • Microsoft Operations Manager 2005 Service Pack 1
  • System Center Operations Manager 2007
    • System Center Operations Manager 2007 Service Pack 1
    • System Center Operations Manager 2007 R2
  • System Center Operations Manager 2012
    • System Center Operations Manager 2012 R2
  • System Center Operations Manager 2016
  • System Center Operations Manager 2019
    • System Center Operations Manager 2019 UR1

Web links

Individual evidence

  1. System Center Wiki - SCOM / SCSM Management Pack Catalog. Retrieved April 1, 2020 .
  2. ^ Mission Critical Software. Retrieved April 1, 2020 .
  3. ^ Mission Critical Software and NetIQ Plan $ 1.42 Billion Merger . In: The New York Times . February 29, 2000, ISSN  0362-4331 ( [accessed April 1, 2020]).
  4. ^ The Evolution of Microsoft's System Center Suite | IT Pro. January 2, 2018, accessed April 1, 2020 .
  5. Now available: Microsoft System Center 2019! March 7, 2019, accessed April 1, 2020 (American English).
  6. Update Rollup 1 for System Center Operations Manager 2019. Microsoft Corp, February 24, 2020, accessed April 1, 2020 .