SCOM 2016 STEP BY STEP INSTALLATION

GUIDE

DANIELE CATANESIHTTP://BLOG.HELOCHECK.COM

This small e-book aims to be a quick guide to help you deploy System Center Operations Manager 2016 from scratch.

The book assumes you will be deploying in a lab environment so some choices will be made that go against security best practices.

Book is not intended as in depth guide but wants to be an easy to follow guide to help you quickly deploy a new SCOM environment for learning purposes.

To follow along the book you will need the following:

• Virtualization Host• Windows 2016 ISO• SQL 2016 ISO• System Center Operations Manager 2016 ISO

ABOUT THE E-BOOK

i

The first step to deploy System Center Operations Manager 2016 (SCOM) is installing the SQL for the OnePoint and data warehouse databases.

The version used to write this e-book is SQL 2016 Standard version. A fully functional 180 days trial can be downloaded from Microsoft website.

INSTALL SQL DATABASE SERVER

1

2

Once downloaded simply launch SQL setup and chose Installation / New SQL Server Stand-alone installation

Once accepted the license agreement SQL Setup program will check for updates which should be downloaded and installed

3

Next Install Rule checks will be run to warn you in case something with the server configuration would case setup to fail, you will most likely see a Warning message about Windows Firewall configuration which usually can be safely ignored.

In the Feature Installation page you need to select• Database Engine Services• Full-Text and Semantic Extractions for Search• Reporting Services - Native

4

In the Instance Configuration page you chose to install on a default instance which fits most situations

In the Server Configuration make sure to set the Startup Type for Sql Service Agent service to Automatic, in a lab environment you can leave all other settings to their default values.

5

Note: While a full review of Default vs Named instances is out of scope you can read more at the following address https://msdn.microsoft.com/en-us/library/ms143531.aspx

In the Database Engine Configuration at least specify the account used for installation as SQL Administrator. In my lab I already created required service accounts and groups so I have added them to the SQL Administrator.

6

Review the summary information making any change as necessary and finally click on Install

While not strictly necessary for SCOM functionality it is advisable to install SQL Management Studio which makes configuring database services much easier.

7

SQL Management Studio is not part of the installation media anymore and needs to be downloaded separately. Clicking on the Install SQL Server Management Tools link will open a webpage where necessary components can be downloaded.

SQL Server Management tools can also be downloaded beforehand at this address.

SQL Server Management Tools is trivial so I will not cover it here, simply accept all defaults and click Next till setup is complete.

8

Before SCOM can be installed there are a number of prerequisites that need to be satisfied.

The first step is installing necessary Windows features and components leveraged by SCOM Server. I will start describing required service accounts and then move to the required Windows features.

SCOM SERVER INSTALLATION

2

9

SCOM SERVICE ACCOUNTS CREATION

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 according to this list

10

ACCOUNT NAME DESCRIPTION LOCAL ADMIN ON

SCOM_DA SCOM Data Access Account SCOM and SQL Server

SCOM_AA SCOM Action Account SCOM and SQL Server

SCOM_SQL_WRITE SCOM SQL DB Write Account SQL Server

SCOM_SQL_READ SCOM SQL DB Read Account SQL Server

SQL_SA SQL Service Account SQL Server

SQL_SRRS Reporting Services Account SQL Server

SCOM_Admins SCOM Administrative Group SCOM Server

If you don’t want to create Service Accounts manually I have created a script that will take care of this part for you.

You can find the post describing the script here or download it from TechNet gallery here.

The second and final step before installing the SCOM Server is installing required Windows features. Simply open an elevated PowerShell session and paste the following code, just keep in mind the server will automatically reboot

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

11

WINDOWS FEATURES INSTALLATION

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

O p e n a n e l e v a t e d c o m m a n d p r o m p t , c h a n g e t o the  %WINDIR%\Microsoft.NET\Framework64\v4.0.30319\ path and finally issue the aspnet_regiis.exe -r command followed by an IISRESET

Next you need to download SQL ReportViewer and SQL CRL Types. To install them simply click on the MSI file and click next till setup is complete.

It’s finally time to install SCOM, simply download the ISO file and, if necessary, extract binaries in a convenient location.

12

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

13

INSTALL SCOM SERVER

As this is a lab installation all components will be installed on the same server. This is usually 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

14

15

16

In the Configure Operations Manager accounts use the accounts previously created manually or via my SCOM Service Account creation.

17

18

Once installation is complete open the Operations console to confirm everything is working as intended

19

Also open the Services console to make sure all SCOM related services have been correctly started

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 e-book.

20

Shortly after the publishing of this guide Microsoft made available, through the October updates release, SCOM 2016 Update Rollup 1.

This chapter will focus on the installation of Update Rollup 1 on a RTM SCOM deployment, details about the release and issues fixed can be found in KB3190029.

While installation can be carried on through Microsoft Update there are steps that still need to be manually executed for this reason in the ebook the whole manual

UPDATE ROLLUP 1 INSTALLATION

3

21

installation procedure will be described which gives more control over the whole process.

Before describing the actual installation steps it is necessary to note the following requirements and best practices:

• Update Rollup installation must be performed as an administrator• SCOM Console should be closed before applying the update (this is to avoid

server’s reboot)• If User Account Control is enabled run the .msp file from an elevated command

prompt• The account used to install the update must have the System Administrator

rights both on the Operational and Data Warehouse Databases

Further to the above list Microsoft recommends installing the update as soon as possible after SCOM Deployment, while I have no hard proof of this I think it has to do with a compatibility issue between SCOM 2016 and October 2016 Cumulative Update for Windows Server 2016.

22

ROLLUP UPDATE 1 INSTALLATION

The high level installation steps are as follows with point number 1 applying mainly to multi system deployments which should not the case in a lab environment

1. Update Rollup package should be installed in the following order on infrastructure servers

• Management Server(s)

• Web Console Server role

• Operations Console Role computer(s)

2. Apply SQL Script (described below) 3. Import Updated Management Packs4. Apply the nano agent update to manually installed agents or push the

installation from the Pending view in the Operations Console (this of course only applies if you’re using Nano servers)

Once ready to perform installation download necessary files from Microsoft Update Catalog

Update is multi-language which means when downloaded and extracted you will have multiple files with the various supported language files but of course you only need to install language files supported/needed in your deployment. I generally just delete unneeded files.

23

Open an elevated PowerShell or Command Prompt session, navigate to the folder where files have been downloaded and launch the .msp file (again order is management server, web console and operation console)

Installation will start but keep in mind there will be no success/failure message, I wonder if Microsoft will ever implement such feature for us mortals to know what’s going on, so just go through the installation of all update files.

Once all update files have been installed open SQL Management studio and run the script that can be found under %SystemDrive%\Program Files\System Center 2016\Operations Manager\Server\SQL Script for Update Rollups

Script needs to be run against the OperationsManager database and NOT the OperationsManagerDW one

24

Once the SQL Script has been executed successfully updated management packs need to be imported. Updated MPs can be found under %SystemDrive%\Program Files\Microsoft System Center 2016\Operations Manager\Server\Management Packs for Update Rollups\

Open the Operations Console and navigate to [Administration] / [Management Packs] right-click on the node and finally select Import Management Packs

25

26

Now navigate to the Pending Management Node and update all server’s agents to the latest SCOM release.

Congratulations you’ve just updated your SCOM 2016 to Update Rollup1!

27