This post I will be installing System Center Operations Manager 2019 (SCOM) RTM, Build Number 10.19.10050.
Here is some of the background information. As this post will concentrate on the installation of SCOM 2019, I am going to omit the setup and configuration of the Domain Controller, Windows Server 2019 for the SCOM Management Server. Also to note, I am using a PaaS instance of SQL 2017 (hosted on Azure), likewise the entire environment lives on Azure in an IaaS and PaaS configuration.
Service Accounts and Local Administrator:
|DomainAccount||Description||Local Admin on…|
|domainSCOM_AA||SCOM Action Account||SCOM|
|domainSCOM_DA||SCOM Data Access/SDK Account||SCOM|
|domainSCOM_SQL_READ||SCOM SQL Reader||n/a|
|domainSCOM_SQL_WRITE||SCOM SQL Writer||n/a|
|domainSCOM_Admins||SCOM Administrators Group||SCOM|
|domainSQL_SA||SQL Service Account||n/a|
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.
Since I am hosting SQL on a dedicated server, I will install SSRS (SCOM Reporting) on that server.
Well, that’s not new… Prerequisites. Since this is a clean, vanilla Windows 2019 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.
- 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.
You will need to apply the following using Command Prompt (as Administrator)). Yes, this is a screenshot from a previous post…Forgot to capture the screenshot when running it this time..
- “cd %WINDIR%Microsoft.NETFramework64v4.0.30319“
- aspnet_regiis.exe -r
- Reboot your server…
Once the server is back online, let’s try that Prerequisites check again….
Great! Now all of Prerequisites have been met!
Provide a meaningful Management Group Name (there’s no going back after this…)
SQL Server will be where your SCOM SQL instance(s) were installed. Remember, to either disable the Windows Firewall, or open SQL TCP Ports 1433.
I recommend always keeping this off, and manually updating your SCOM infrastructure.
One quick review. Looks good. Hit Install, and get some fresh air!
A few minutes later….
Sweet! All good. I hope this helps. If you have any questions or issues, please drop me a line.
Happy 2019 SCOM’ing!