This blog post is designed to get you from nothing to an All-In-One Operations Manager 2016 environment running in Azure on Windows 2016 with SQL 2016 in a couple of hours from start to finish. The following are the major steps involved:

  1. Creating the IaaS system in Azure
  2. Configure IaaS and the Operating System
  3. Configuring the system as a Domain Controller
  4. Installing Operations Manager 2016 pre-requisites
  5. Installing Operations Manager 2016
  6. Configuring Operations Manager 2016

Creating the IaaS system in Azure:

Start with Azure and use the existing Windows Server image:

The best option for this is “Windows Server 2016 Datacenter” (then you get to test out Windows Server 2016 at the same time!)

Use the Resource Manager deployment module:

Operating System Configuration:

After it is created, log into the system and verify that it’s functioning as expected.

In Azure assign a static IP address in Azure (set under Network Interfaces, IP Configurations, ipconfig1)

Configure as a domain controller:

Next configure this system as a domain controller for a new domain through add roles and features.

The installation still does not see the virtual as having a static IP address since it’s actually using DHCP and just assigning that address to the system. If you want to avoid the message below you can hard-code the value on the network settings in the Operating System.

Next promote the system to be a domain controller for your new domain.

Install everything to the C drive, not the D drive as that’s a temporary storage drive.

Installing Operations Manager 2016 pre-requisites:

Download media for System Center Operations Manager 2016, UR1, Windows Server 2016 (for the pre-req checker), SQL 2016 and store them on the C drive (downloads as an example).

After reboot and re-log in and install SQL server.

Next install the OpsMgr pre-requisites (use to make this much quicker. [I ended up having to uncomment the line which started with “Add-WindowsFeature Web-WebServer” so that it does add the features which are missing.]

Pre-requisite installation Tip:

The following is a PowerShell one-liner that my colleague Mick worked up for provisioning all the required Windows Server, IIS and .NET Roles, Role Services and Features for the Microsoft System Center 2016 Operations Manager Web Console role.

The Add-WindowsFeature cmdlet will attempt to find the installer binaries and download them automatically via Windows Update if an Internet connection is available, but if you are installing in an isolated network environment or in a high-security environment that restricts outbound Internet access to Windows Update, you’ll need to mount the Windows Server installation media (ISO/DVD) to provide the .NET 3.5 installation binaries, and include this argument on the cmdlet:

Add-WindowsFeature -Source <path to Windows Server installation media, sxs folder>

Web-WebServer, Web-Static-Content, Web-Default-Doc, Web-Dir-Browsing, Web-Http-Errors, Web-Health, Web-Http-Logging, Web-Request-Monitor, Web-Stat-Compression, Web-Filtering, Web-Basic-Auth, Web-Windows-Auth, Web-Mgmt-Console, Web-Metabase, Web-ISAPI-Filter, Web-ISAPI-Ext, Web-Asp-Net, Web-Net-Ext, Web-Net-Ext45, Web-Asp-Net45, NET-Framework-Core, NET-WCF-HTTP-Activation45

Documentation Note:

While researching this in mid-November, the TechNet documentation did not list .NET 2.0 (included with .NET 3.5) as required, so I tried installing without the .NET 3.5 role service “.NET Extensibility 3.5”, and the installation failed. When I went back to add this role service, it of course requires the .NET Framework 3.5, which is deprecated and not installed by default on Windows Server 2012 R2 and Windows Server 2016. But the PowerShell one-liner above will attempt to install the .NET Framework 3.5 as well as the required “.NET Extensibility 3.5” component.

Install Operations Manager 2016:

The installation process for Operations Manager 2016 is very similar to how it was in 2012 R2.

Be sure to install UR1 for System Center Operations Manager 2016 after your installation completes (available at

Operations Manager installs as evaluation so you need to go to PowerShell and add the key so that it doesn’t expire.

For details on adding the key see:

Once the key is added it should appear as follows in PowerShell.

Configuring Operations Manager 2016:

Once you have Operations Manager 2016 installed, you can now configure management packs, multihome agents and integrate with Microsoft OMS.

Management Packs

Once Operations Manager is installed go to updates and recommendations to find relevant (not currently installed) management packs:

Add the various updates and recommendations with the “Get All MPs” option.

Get All MPs will show you additional management packs which you should update or add which finishes the process of installing this environment.


You can multi-home your existing Operations Manager agents so that they report to your original Operations Manager environment and this new all-in-one environment. For details on this see this previous post:

Note: Web console issue

Early on there was an issue with the web console. Details are available at:,

Integrate Operations Manager with OMS

Add OMS integration and you are ready to roll with this! (details are available at:


Good reference on this topic:

Thank you to Mick Talbott for your help on this blog post especially around the installation of pre-requisites!

Summary: From start to finish was about two hours of actual work to create a new system, make it a domain controller, install pre-requisites (including SQL 2016), install Operations Manager and get configuration of Operations Manager completed!