Canberra, Australia
To be provided
To be provided

Installing System Center 2016 Operations Manager Step by Step – Part 1

Harmik Batth Tech Blog

Installing System Center 2016 Operations Manager Step by Step – Part 1

The purpose of this post is to go through guided installation of Microsoft System Center 2016 Operations Manager with agent installation and management pack importing as well.

As this is Microsoft product, I will be using Microsoft Documentation –

Microsoft has put lot of emphasis on Enterprise based Monitoring solution for infrastructure resources. In Today’s world, a resource can be Physical or Virtual, in DataCentre or in cloud. Everybody is worried about their business critical resources whether it is managing, monitoring or workloads.

System Center 2016 Operations Managers is supposed to be single solution for all your business needs and single point of health information. Few of the benefits that OpsMgr 2016 is delivering are Cross-Platform Monitoring, Data Visualization and Network Monitoring. For more information, please visit Microsoft System Center Monitoring Brief.


This post I will be covering SCOM 2016 official release installation. This will be multi-part series, where following information will be shared

  1. Part 1
    1. Operations Manager Overview
    2. System Center Requirements
  2. Part 2
    1. SQL 2016 Installation
  3. Part 3
    1. First Management Server Installation
  4. Part 4
    1. Second M Management Server Installation
  5. Part 5
    1. Gateway Installation
  6. Part 6
    1. Reporting Services Installation
  7. Part 7
    1. Installing Agents
  8. Part 8
    1. Conclusion

Part 1.a – Operations Manager Overview

For the purpose of this installation, following Server Operating systems are used:

  1. Windows Server 2012 R2 Standard as Base OS
    1. Active Directory or Domain Controller
    2. SQL Server
    3. 2 X Management Servers
    4. Gateway

Each Component has different VM or physical Server instance. So in Total, we will have at-least 5 VM’s.

Following Application components are used:

  1. SCOM 2016
  2. SQL 2016

Keep in mind that you can only install SCOM 2016 on Win 2012 R2 or above.

There are some pre-requisites

  1. PowerShell V2 or 3
  2. .Net Framework 4 or later
  3. Microsoft Report Viewer 2015 runtime or later

Make sure you install these on all Servers before installing SCOM Components.

For Installing SQL and SCOM Components, there are certain requirements of Users and permissions.

Please make sure you have all these accounts created in AD before starting installation

DASAccountUser Scom_da SCOM Action Account, SCOM Data Access/SDK Account, SQL Service Account & SQL Service Reporting Services Account
DataReaderUser Scom_dr SCOM SQL Reader
DataWriterUser Scom_dw SCOM SQL Writer
SCOMAdminsGroup Scom_admins SCOM Administrators Group

Here is snapshot of Installation and Configurations Steps:

  1. Configure domain controller
    1. Create the accounts.
  2. Install Prerequisites
  3. Install SQL Server 2016
  4. Install SCOM 2016
    1. Install First Management Server and Database Components
    2. Install Second Management Server
    3. Install Gateway Server
  5. Install the Reporting components on SQL Server
  6. Deploy Agents
  7. Import Management packs

[polldaddy poll=9587662]


Comments: 4

  1. Pankaj Chandel says:

    Hi Harmik,

    Thanks for such a informative blogs. It is a great effort.
    Please suggest an architecture as per bellow scenario
    No of Monitoring agents: 1000
    No of Monitoring N/W Devices: 500

    Required Features in my Scenario:
    URL monitoring
    Web Console
    ACS Database
    Data ware house (2VM)
    Operational database (2VM)
    Management Servers (2VM) (Active-Active or Load Balancing)
    Gateway Server (2Physical Server)
    Reporting Server (2VM)

    All will be in failover clustering with windows OS and SQL clustering (always on).

    Awaiting from your prompt reply.
    Thanks a lot again.

    Pankaj Singh Chandel

  2. harmikbatth says:

    Hi Pankaj

    Thanks for your question and it is really important to set things up properly from scratch.

    Microsoft has a “OpsMgr 2012 Sizing Helper”, which is still valid for SCOM 2016. I recommend you to use that tool.

    The OpsMgr 2012 Sizing Helper is an interactive document designed to assist you with planning & sizing deployments of System Center 2012 Operations Manager. It helps you plan the correct amount of infrastructure needed for a new OpsMgr 2012 deployment, removing the uncertainties in making IT hardware purchases and optimizes cost. A typical recommendation will include minimum hardware specification for each server role, topology diagram and storage requirement.

    I hope it answer your question.


  3. Hamid says:

    Hi, Harmik,
    as you told “we will have at-least 5 VM’s”
    can we setup all services in one Server or not?
    this is your suggestion 5VM or totally we can’t setup all services in one server.


    • harmikbatth says:

      Yes for your Lab environment, you can setup all services in one server.
      But for production and for best performance it is recommended to have roles distributed.

Add your comment