Microsoft made System Center 2016 available so it is time to upgrade your lab and start playing with it. In this article I will illustrate how to install SCOM step by step.
I will assume you already have deployed a server with SQL that will be used to host the SCOM database. You can refer to this article till I publish a version for SQL 2016 it will do.
[su_note note_color=”#ffff96″ text_color=”#000000″ radius=”5″]Note: An offline version of this article in PDF format is available through TechNet Gallery which also covers SQL 2016 Installation [/su_note]
Install SCOM pre-requisites
Before SCOM can be installed there are a number of prerequisites that need to be satisfied.
SCOM carries on tasks like agent installation, workflows, data access through authenticated user accounts. While some service accounts, like Run As ones, can be created after product is deployed there are some accounts that need to be created beforehand.
|Account Name||Description||Local Admin Rights|
|SCOM_AA||SCOM Action Account||SCOM & SQL|
|SCOM_DA||SCOM Data Access/SDK Account||SCOM & SQL|
|SCOM_SQL_READ||SCOM SQL Reader||SQL|
|SCOM_SQL_WRITE||SCOM SQL Writer||SQL|
|SCOM_Admins||SCOM Administrators Group||SCOM|
|SQL_SA||SQL Service Account||SQL|
|SQL_SSRS||SQL Service Reporting Services Account||SCOM|
If you don’t want to create Service Accounts manually I have created a script that will take care of this part for you.
Next step is installing required Windows OS features required by SCOM which is easily accomplished opening an elevated PowerShell session and the paste the following command
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-Asp-Net, 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 need to manually register ASP.Net
Open an elevated command prompt, change to the %WINDIR%Microsoft.NETFramework64v4.0.30319 path and finally issue the aspnet_regiis.exe -r command followed by an IISRESET
It’s finally time to install SCOM, simply download the ISO file and, if necessary, extract binaries in a convenient location.
Install SCOM Server
To start SCOM installation double click the setup.exe file, as the installation wizard is straightforward I will just paste mages with my comments as necessary
In a lab installation all components can be installed on the same server. Usually this is not a best practice in a production environment where various roles/components are split among servers for redundancy and performance reasons
If there are issues with any of the prerequisites, if you followed up to this point that should not be the case, you will be asked to either join an existing Management Group or create a new one. Chose to create a new Management Group using a descriptive name
In the Configure Operations Manager accounts use the accounts previously created manually or via my SCOM Service Account creation.
Once installation is complete open the Operations console to confirm everything is working as intended
Congratulations you just deployed a fully functional SCOM Server. Next steps would involve creating necessary Run-As accounts and importing Management Packs but that’s material for another article.