Step-by-Step – Installing System Center Operations Manager (SCOM) 2016 on Windows Server 2016 with SQL 2016

This post I will be installing System Center Operations Manager 2016 (SCOM) RTM, Build Number 7.2.11719.0.

Here is some of the background information. As this post will concentrate on the installation of SCOM 2016, I am going to omit the setup and configuration of the Domain Controller, Windows Server 2016 for both SCOM Management Server and SQL Server (Please note, I am using SQL Server 2016, both servers on Windows 2016).

If you need help setting up SQL 2016 for SCOM 2016, please visit HERE.

Environment:  Virtual; ESX 6.0 Hypervisor

SCOM Management Server:

  • Windows Server 2016
  • 4 vCPU (2.00GHz)
  • 12 GB memory
  • 100GB Diskspace
  • 1GB vNIC

SQL Server:

  • Windows Server 2016
  • SQL Server 2016
  • 4 vCPU (2.00GHz)
  • 24 GB memory
  • 300GB Diskspace
  • 1GB vNIC

Service Accounts and Local Administrator:

Domain\Account Description Local Admin on…
domain\SCOM_AA SCOM Action Account SCOM & SQL
domain\SCOM_DA SCOM Data Access/SDK Account SCOM & SQL
domain\SCOM_SQL_READ SCOM SQL Reader SQL
domain\SCOM_SQL_WRITE SCOM SQL Writer SQL
domain\SCOM_Admins SCOM Administrators Group SCOM
domain\SQL_SA SQL Service Account SQL
domain\SQL_SSRS SQL Service Reporting Services Account SCOM

 

Now, if you’re lazy like me, or are tired of doing this setup for environments, I have scripted the automation of these accounts. You can find that link here, Microsoft TechNet Gallery.


Let’s Begin:

2

3

For completeness, let’s install all the features of SCOM 2016. (I am hosting a default SQL 2016 instance on the SCOM Management Server for SSRS)

4

5

Well, that’s not new… Errors. Since this is a clean, vanilla Windows 2016 server, we will need to install all the necessary Web Console components, along with Report Viewer Controls (probably SQL CLR Types too..).

  • For the Report Viewer Prerequisites, go HERE.

Note, oddly I was unable to install with CLR SQL 2016, Reports Viewer still complained and required CLR SQL 2014.

  • Here is the PowerShell command I ran to install the necessary IIS features/roles:
Import-Module ServerManager
Add-WindowsFeature Web-Server, Web-WebServer, Web-Common-Http, Web-Default-Doc, Web-Dir-Browsing, Web-Http-Errors, Web-Static-Content, Web-Health, Web-Http-Logging, Web-Log-Libraries, Web-Request-Monitor, Web-Performance, Web-Stat-Compression, Web-Security, Web-Filtering, Web-Windows-Auth, Web-App-Dev, Web-Net-Ext45, Web-Asp-Net45, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Mgmt-Tools, Web-Mgmt-Console, Web-Mgmt-Compat, Web-Metabase, NET-Framework-45-Features, NET-Framework-45-Core, NET-Framework-45-ASPNET, NET-WCF-Services45, NET-WCF-HTTP-Activation45, NET-WCF-TCP-PortSharing45, WAS, WAS-Process-Model, WAS-Config-APIs -restart

 

Once the server is back online, you will need to register ASP.Net.

6

You will need to apply the following using Command Prompt (as Administrator)).

  1. cd %WINDIR%\Microsoft.NET\Framework64\v4.0.30319\
  2. aspnet_regiis.exe -r
  3. IISRESET
  4. Reboot your server…

Once the server is back online, let’s try that Prerequisites check again….

7

Great! Now all of Prerequisites have been met!

8

Provide a meaningful Management Group Name (there’s no going back after this…)

9

SQL Server will be where your SCOM SQL instance(s) were installed. For me, I have built two instances on my SQL2016 server (SCOM_OPSMGR & SCOM_DW).

10

11

12

13

14

15

16

17

I recommend always keeping this off, and manually updating your SCOM infrastructure.

18

One quick review. Looks good. Hit Install, and get some fresh air!

19

A few minutes later….

20

Sweet! All good. I hope this helps. If you have any questions or issues, please drop me a line.

Please note, it is STRONGLY ADVISED to install the Update Rollup 1 once you have deployed SCOM 2016. For that walk-through, please visit the following post, HERE.

Happy 2016 SCOM’ing!

21

22

Advertisements

31 thoughts on “Step-by-Step – Installing System Center Operations Manager (SCOM) 2016 on Windows Server 2016 with SQL 2016

    1. Hi Alessandro,

      Did you follow the steps as mentioned above?

      You will need to apply the following using Command Prompt (as Administrator)).

      1. “cd %WINDIR%\Microsoft.NET\Framework64\v4.0.30319\“
      2. aspnet_regiis.exe -r
      3. IISRESET
      4. Reboot your server…

      Like

  1. Hi Ravi,

    I will be soon building a SCOM 2016 environment and have read you need to have SQL installed prior to setting up SCOM. I am planning to use SQL 2016 and noticed above that you were going to add a guide with instructions for SQL 2016. Are you any closer to releasing this as it would be very useful to use as a guideline as the rest of your post is very good?

    Thanks.

    Like

      1. Thank you for the prompt reply Ravi. I have just seen your SQL 2016 guide attached. I appreciate you posting it sooner than anticipated. I’ll proceed with the build and let you know how it goes.

        ps – The script for the automated accounts for SCOM looks awesome so I’ll be trying that out as well 🙂

        Like

  2. Powershell script create a account SCOM_OMS….why this account being created in script as it seems not used in the setup ?

    Like

  3. Thanks for the great guide. When running the setup the option to select Management sever is not selectable (grayed out). Any ideas?

    Like

      1. Thanks for the quick response. The server had a 2012 SCOM agent installed. Once removed. It allowed me to select Management server.

        Like

  4. Ran into another issue. I installed a default SQL 2016 instance on my management server, however when running through the setup it does not show up as an option when prompted to select the SQL server instance for reporting services. The list is blank. Any ideas?

    Like

    1. Hi Tom, Was SSRS installed during the SQL instance install? Did you select the option to install only, or install and configure? I would advise, go into SSRS and re-configure the setup. Then try running the SCOM install again.

      Like

      1. Hi Ravi, SSRS was not installed, after installing it, the server shows up as an option. Now there’s an error that it’s configured incorrectly. I’m in the Reporting services configuration manager. Do you know what needs to be done to get past the error?

        Like

  5. The error is “The specified SQL Server instance is not valid.
    *SSRS has not been configured correctly
    *SSL is configured for the SQL server Report Server
    *A proxy server is configured for the SQL Server Report Server

    Like

      1. Yes thanks, I finally got past the SSRS errors however SCOM still fails during the install phase. The install appears to be much more complicated than I expected. I think it may be due to the SQL server configuration. Is there a reason you’re using two instances?

        Like

      2. Typically in production environments, I suggest to my customers to have the SCOM OpsDB and DW (Data Warehouse) on separate instances and also on separate servers. This is due to the IPOS and workloads the DW commands. If you choose, you can always install both DBs on on server and a single instance.

        Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s