This post I will be installing System Center Operations Manager 2016 (SCOM) – Technical Preview 5 (TP5). Technical Preview for both System Center 2016 and Windows Server 2016 was recently released, April 27th.
Here is some of the background information. As this post will concentrate on the installation of SCOM 2016 TP5, I am going to omit the setup and configuration of the Domain Controller, Windows Server 2012R2 for both SCOM Management Server and SQL Server (Please note, I am using SQL Server 2014 SP1, both servers on Windows 2012R2).
Environment: Virtual; ESX 5.5 Hypervisor
SCOM Management Server:
- Windows Server 2012 R2 — SCOM2016TP5
- 4 vCPU (2.00GHz)
- 12 GB memory
- 100GB Diskspace
- 1GB vNIC
SQL Server:
- Windows Server 2012 R2 — SCOMSQLTP5
- SQL Server 2014 SP1
- 4 vCPU (2.00GHz)
- 12 GB memory
- 200GB Diskspace
- 1GB vNIC
Service Accounts:
| Domain\Account | Description |
| RAVILOCAL\scom_aa | SCOM Action Account |
| RAVILOCAL\scom_da | SCOM Data Access/SDK Account |
| RAVILOCAL\scom_sql_read | SCOM SQL Reader |
| RAVILOCAL\scom_sql_write | SCOM SQL Writer |
| RAVILOCAL\scom_admin | SCOM Administrators Group |
| RAVILOCAL\sql_sa | SQL Service Account |
| RAVILOCAL\sql_ssrs | SQL Service Reporting Services Account |
Let’s begin:
I will not be installing Reporting on this server, as I will install this on the SQL Server (I will create a post for this later…)
Well, looks like I will need to install the Report Viewer Controls and need to install some IIS components for the Web Console.
- For the Reports Viewer Controls prerequisites, you can visit the following post for the instructions, HERE.
- For the Web Console/IIS components prerequisites, you can visit the following post for the instructions, HERE.
Looks like I still need to meet a few more prerequisites…
You will need to apply the following commands (unfortunately I could not execute in PowerShell, so you will need to use Command Prompt (as Administrator)).
- “cd %WINDIR%\Microsoft.NET\Framework64\v4.0.30319\“
- aspnet_regiis.exe -r
- IISRESET
- Reboot your server…
Back to to installation…..
Since this is a lab, I installed the databases on the same SQL instance. Best practice, use dedicated instances or better yet, dedicated servers…
Whoops, I forgot to add the SCOM service accounts as local administrators on the SCOM Management Server….
Okay, back to the installation…
I recommend always keeping this off, and manually updating your SCOM infrastructure.
Let this run, go for a break, coffee, smoke, whatever….
Yay! All good!
Right off the bat, looks like there are a new features, like, “Tune Management Packs” I will get into this in another post…
Thoughts: As you may have noticed, the install is almost identical to the 2012R2 and it appears not much has changed in terms of the install.
Lastly, SQL before the install, and after:
Before:
After:
SCOM & Other Geeky Stuff 
Thank you, just setup my SCOM 2016 today, first time install SCOM, you post helps a lot.
LikeLike
That is terrific, Sandy! I am glad my blog post could help you through the setup!
LikeLiked by 1 person
Hi,
i’m installing SCOM 2016 , as SQL server SQL 2014, i have a problem to configure the rigth ports to allow in Windows Firewall. i can’t connect SCOM 2016 to the Instance in SQL 2014, but if turn off Windows Firewall , i cant connect them .
can you tell me wich port i allow , i tried(1433.1434.135.445.80)
LikeLike
hi Rami, port 1433 is a SQL default. what exactly is the error? have you enabled named pipes under ths sql configuration? have you deleted any entries for dynamic ports? does the scom data access account have rights to the sql server (locally)? do the scom service accounts have the correct access to the sql instance(s)?
LikeLike
HI Ravi,
The problem is when i activate windows Firewall, if i disable Windows Firewall , i can connect to the instance SQL, but i should enable windows Firewall.
i enabled named pipes under SQL configuration, SCOM data account have rights locally to th SQL .
i suppose to add exceptions to Windows Firewall , what do you think
LikeLike
Hi Rami, have a look here: https://msdn.microsoft.com/en-us/library/cc646023.aspx?f=255&MSPPError=-2147217396
LikeLike
Reblogged this on Cloud & Virtualization Complete Guide.
LikeLike
Thanks for helping Us!
LikeLike
You are most welcome!
LikeLike
I am curious why is there SQL Service Reporting Services Account? I couldn’t find it mentioned on any other guide including technet, and usually SCOM SQL Reader account is used for Reporting Services. On Technet, under Data Reader account is says that it has to have this assignment:
Applications: Windows service Database/Role: SQL Server Reporting Services Role/Account: Logon account
https://docs.microsoft.com/en-us/system-center/scom/plan-security-accounts
Please correct me if I’m wrong.
LikeLike
I come from an auditing/governing background, and I like to not only implement with dedicated accounts for all types of services, but also push that as best practice. Ultimately, it is up to you. Use one account for everything, or dedicated accounts, or use Microsoft’s recommendations.
LikeLike