System Center Operations Manager 2016 Step by Step–Part 4

I saw today  that I wrote last post almost a month ago. It took me almost a month to go back to what I started to do. Installing SCOM 2016. In last blog post we prepared SQL server for installation. Yesterday I was checking on event logs for SQL, and there was some errors. So please install CU 4 for SQL 2016 RTM to suppress these errors.

Lets continue. I want to prepare for SCOM installation. What I need to install beforehand? All prerequisites you can find on TechNet System Center guide page but I will simple it up. 

First thing is Management server. You will install SCOM console there and you need to  install the Report Viewer controls to any server that will receive a SCOM console.  There is a prereq for the Report View controls which is the “Microsoft System CLR Types for SQL Server 2014” (ENU\x64\SQLSysClrTypes.msi) available here:   https://www.microsoft.com/en-us/download/details.aspx?id=42295.

Install that first and after that install Report Viewer.

image

So we finish prereq one. Lets go prereq two. To install web console on any server you will need to install IIS with all of this options.

Internet Information Services: IIS 7.5 and later versions, with the IIS Management Console and the following role services installed:

  • Static Content
  • Default Document
  • Directory Browsing
  • HTTP Errors
  • HTTP Logging
  • Request Monitor
  • Request Filtering
  • Static Content Compression
  • Web Server (IIS) Support
  • IIS 6 Metabase Compatibility
  • ASP.NET (both the 2.0 and 4.0 versions of ASP.NET are required.)
  • Windows Authentication

Just run this PowerShell command any it is done.You put you path in source parameter for Windows Server OS installation source or if your computer has access to Internet you don’t need it. It is required for asp.net 2.0 activation (correct me if I am wrong)

Add-WindowsFeature NET-WCF-HTTP-Activation45,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Request-Monitor,Web-Filtering,Web-Stat-Compression,Web-Mgmt-Console,Web-Metabase,Web-Asp-Net,Web-Windows-Auth -Restart -Source D:\sources\sxs

image

Restart computer after this. Recommended by Kevin Holman. After that you will probably get new updates so update computer before continuing.

Lets prepare service accounts. You need next accounts

  • Local System                      SCOM Server Action Account (you can create domain one, I use local system)
  • DOMAIN\scomcdas            SCOM Config and Data Access Account
  • DOMAIN\scomdwreader    SCOM Data warehouse Reader Account
  • DOMAIN\scomdwriter     SCOM Data warehouse Write Account
  • DOMAIN\scomsql              SQL Service Account
  • DOMAIN\ScomAdmins       SCOM Administrators security group

Add scomcdas, scomdwreader,scomdwriter and Scom server action account if you created domain one to ScomAdmins group. Add the “SCOMAdmins” domain global group to the Local Administrators group on each server.

This is basic prerequisites for running setup of SCOM. See you tomorrow I hope.

Advertisements

System Center Operations Manager 2016 Step by Step–Part 3

Hi again

after some work problems I get back to new SCOM 2016 installation. I mentioned last time that we will today install SQL server. There were some questions about which version to use. I wanted to install SQL 2016 SP1 but I get notice it is not yet supported (see comments on this post by Kevin Holman.  You can get the list of last supported databases with SCOM 2016 UR1 on this TechNet link

image

You can use version you choose, because if you remember SQL license is free for System Center products. With only one rule, just use it for System Center products databases and nothing else.

Did you create SQL service account. If you didn’t, do it now. I created only two. One for SQL service account and one for SQL Reporting services account. So lets start. Choose new SQL server installation

image

After entering product key, accept license terms of use. I skipped Microsoft updates because I don’t want to end up with SP1 I don’t need for this SCOM installation. 

image

If everything is green you are good even windows firewall scream for attention here. You choose next features needed for SCOM SQL installation

 image

Choose default instance if you don’t need better that that

image

Enter you domain service accounts for SQL services and give services automatic startup. Also check Volume Maintenance Task privilege to use this new SQL feature

image

You need to use this SQL collation. In any case it is by default in SQL installation sou you will not miss it

image

Specify Windows authentication mode (do not use Mixed mode)

image

You setup your database and log files as you can, but rule of the thumb is to format those drives with 64K allocation unit sizes, and if you have possibility put your tempdb database and log on SSD drive. It is best to leave that volumes only for databases.

image

On Reporting Services page choose Install and Configure

image

Click next on Feature Configuration Page if everything is green  and then Install on Ready to Install page.

After everything is done, we are free to go further. Until next time

image

System Center Operations Manager 2016 Step by Step– Part I

As you know SCOM 2016 is published last year. Like many others I also have a task to upgrade my SCOM environment to new version. That’s why I get idea to document my path and maybe help other on all problems that can occur. Probably there is some people that are installing this product  for the first time. I will not write to much about theory of how SCOM works but focus mainly on all steps required to have functional and working SCOM environment. Especially I will take some time to explain configuration of some different management packs both Microsoft, vendor and community published.

So lets start. For all of you newbies, I will recommend first some reading you can do besides this blog. There is not so much books about SCOM 2016 but there is no much change when you compare it to 2012 R2 version. You can use 2012 R2 books and articles if you have it already. This is the list of latest books, new and old links you can use:

There is more, but lets stop here. It is more then enough to start with. So what is the first step. PLANNING!

To have functional SCOM environment you need to carefully plan your workloads. How to size your environment? You can do it by experience from your previous deployments, but if you are new then you use System Center 2012 Operations Manager Sizing Helper Tool Excel sheet. It is made for SCOM 2012 version, but it is usable for SCOM 2016. Only thing I saw is wrong in excel sheet is number of Linux/Unix computers you can manage with one management server. If I am not wrong number is doubled in SCOM 2016 so take that in account.

image

I will not walk you on Excel sheet. You will need to go for yourself to discover your needs. Please be extra careful with designing database server. It is crucial in SCOM design. If you have some good SQL admin ask his advise. If you don’t know how to calculate IOPS requirements you can test them on you server. For that best thing to use lately (besides IOmeter) is using DiskSpeed Powershell script together with  Diskspd Utility: A Robust Storage Testing Tool (superseding SQLIO). Be careful to put script into right folder with diskspd.exe file to get it running. When you succeed you get something like this. 

image

I need to run to other task that are waiting for me, but we will see each other very soon. Go thru this subjects and next time I will show you my imagined future configuration on almost purely experience basis. 

See you