The Microsoft/System Center Operations Manager (SCOM) team has just released the Windows Storage Spaces Direct (S2D) Management Pack (MP). Click HERE for the Management Pack.
Launch the PowerShell console, and Run as Administrator:
Import-Module OperationsManager Set-SCOMLicense -ProductId "XXXXX-XXXXX-XXXXX-XXXXX-XXXXX" Start-Sleep -s 10 Restart-Service healthservice, omsdk, cshost
Don’t forget, in order for the Product Key to be applied, you will need to restart all SCOM Services, (or you can run the code above (there is a 10 second delay after the key is applied before the services are restarted)):
- Microsoft Monitoring Agent (healthservice)
- System Center Data Access Service (OMSDK)
- System Center Management Configuration (cshost)
The following PowerShell code is to install all the necessary IIS components for System Center Operations Manager (SCOM) 2016 Web Console on Windows Server 2016.
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, web-asp-net -restart
You can also find this in Microsoft’s TechNet Gallery, HERE.
The following is a guide on how to install SQL 2016 for your System Center Operations Manager (SCOM) 2016 environment. I will be installing SQL 2016 on a brand-new server with Windows Server 2016 installed.
To begin, I am going to set the following accounts as a Local Administrator on the server. Also, I am going to be creating two SQL instances, one for the Operations database, and the other for the Data Warehouse. Since this is for my personal lab, I am not dedicated storage/drives for the databases.
|domain\SCOM_AA||SCOM Action Account|
|domain\SCOM_DA||SCOM Data Access/SDK Account|
|domain\SCOM_SQL_READ||SCOM SQL Reader|
|domain\SCOM_SQL_WRITE||SCOM SQL Writer|
|domain\SQL_SA||SQL Service Account|
Next, let’s run the setup wizard as the SQL_SA account to make life easier down the road…
First thing I noticed, between SQL 2012/2014 and SQL 2016, a few changes/features have been removed/added. One that stands out is, the SQL Server Management Studio (SSMS) console is no longer here. Hmm.. I guess we can always connect to the databases from a console on another server/PC.
As mentioned, I am dedicated an instance for the Operations DB, and one for the Date Warehouse DB.
Setting the SQL Server Agent to Automatic, and specifying the service accounts for the two services.
Keeping the database engine collation as default, “SQL_Latin1_General_CP1_CI_AS“.
Here, I am adding all the SCOM/SQL service accounts and SQL service accounts as SQL server administrators.
Nice! This is new for SQL 2016 — being able to create TempDB‘s. Since my VM has 8 vCPU’s, looks like SQL 2016 picked up on that, and has decided to create a one-to-one relationship. Great, let’s get started within the installation…
Perfect! No errors. Keep in mind, we will need to repeat these steps to create the Data Warehouse instance.
Great! Now we can go ahead with the SCOM 2016 installation! See HERE, for that post.
If you need to install the SQL Server Management Studio (SSMS), continue reading…
Just a quick reminder, next week, November 16th, I will be hosting a SCOM 2016 and OMS meetup. It will be hosted at the University of Toronto, Nov 16, 2016. Please see the link below for more details!
Seating is free (but limited!), so RSVP your spot soon!! For more details on the Meetup, please see HERE.
See you all there!
I had some free time so, I figured let’s test out the SCOM 2016 Web Console with respect to HTML5…
In my test, I tested the following browsers. Please note, metrics/data collected was within the built-in browser development tools.
- Internet Explorer 11 (Obviously)
- Chrome (v 54.0.2840.71 m)
- Firefox (v 49.0.2)
I tested out the following views within each browser:
- Alerts View
- State Views
- Performance Views
- Diagram Views
- Dashboard Views
Let’s get started:
First, let’s try my default (go-to) browser, Chrome…
Verdict: Well, that’s a bummer… All but the dashboard view worked. I suspect Silverlight is still required… But good to know most, or at least in this exercise 80% of the functionality tested works in Chrome.
Next, let’s test Firefox.
Verdict: (See Chrome…)
Lastly, Internet Explorer (not Edge).
Verdict: Well, there you have it, the SCOM 2016 Web Console is not all HTML5, as it still requires Silverlight. Maybe the MOM team will step their game up, and have this fully integrated in SP1 or maybe R2 versions — After all, HTML5 was released in 2014. Or maybe, this is Microsoft’s gentle way of pushing users to OMS (Operations Management Suite).
Also, Google Chrome was notably faster than Firefox and IE.
|OpsMgr Page View; Browser||Google Chrome||Firefox||Internet Explorer (11)|
|Alerts View||1.84 s||2.73 s||2.73 s|
|States View||2.62 s||2.13 s||2.12 s|
|Performance Views||2.88 s||4.68 s||5.50 s|
|Diagram Views||0.87 s||2.97 s||1.76 s|
|Dashboard Views||1.96 s||1.40 s||2.18 s|
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
- 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.
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)
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.
You will need to apply the following using Command Prompt (as Administrator)).
- “cd %WINDIR%\Microsoft.NET\Framework64\v4.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. For me, I have built two instances on my SQL2016 server (SCOM_OPSMGR & SCOM_DW).
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.
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!