From the high level overview of the project, this post will detail how to create the SCOM01 and SCOM02 servers. This post requires a working SQL server database, set up in the previous post.
TechNet Recommended Reading :
Getting Started with System Center 2012 – Operations Manager
System Center 2012 Operations Manager Survival Guide
What’s New in Operations Manager
Documentation Library for System Center Operations Manager
Supported Configurations for Operations Manager
Deployment Guide for Operations Manager
Pre-configuration tasks:
Create the following accounts and groups in Active Directory:
Domain\OMAA Operations Manager server action account
Domain\OMDAS Operations Manager and Data Access service account
Domain\OMSQL Operations Manager SQL Service account
Domain\OMAdmins Operations Manager Administrators Security Group
Nest the admin SMSadmin in the local administrators group on each of the servers.
Make sure all servers have dns entries on your server running DNS services.
Prereqs to getting SCOM consoles on servers SCOM01 & SCOM02:
Microsoft System CLR Types for SQL Server 2012
Reports viewer 2010 is installed http://www.microsoft.com/en-us/download/details.aspx?id=6442
On servers SCOM01 & SCOM02 that will run the management server web console:
Run PowerShell as an Administrator and use the following:
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
Restart the servers after the installation of IIS.
Creation of the SCOM01 server
Log in with an account with domain admin access.
Insert the Operations Manager 2012 w SP1 ISO, Select Setup.exe. Select Install.
Operations Manager Autoplay screen
- Select the following, and then click Next:
- Management Server
- Operations Console
- Web Console
Operations Manager Selection screen
Keep the default path and select Next. It will peform a verification on your system after selecting next.
Operations Manager default path
Pre-req’s passed. If there are any errors, go back and fix them before installing Operations Manager. Select Next to continue.
Prerequisites
On the specify an installation screen – choose to create the first management server in a new management group. Give your management group a name. Don’t use any special or Unicode characters, just simple text. Select Next to continue.
Installation option
Agree to the terms and select Next to continue.
Terms and conditions
On the Configure the Operational Database screen, enter in the name of your SQL database server name and instance. In this case I am using DB01. Leave the port at default unless you are using a special custom fixed port. If necessary, change the database locations for the DB and log files. Leave the default size of the logs at 1000 MB for now. Select Next to continue.
Operations Manager Database Selection
On the Web Console screen, choose the default web site, and leave SSL unchecked. If you have already set up SSL for your default website with a certificate, you can choose SSL. Select Next to continue.
Specify web site
On the Web Console authentication screen, choose Mixed authentication and click Next.
Authentication method
On the accounts screen, change the accounts to Domain Account for ALL services, and enter in the unique DOMAIN\OMAA, DOMAIN\OMDAS, accounts created previously. It is a best practice to use separate accounts for distinct roles in OpsMgr, although you can also just use the DOMAIN\OMDAS account for all SQL Database access roles to simplify your installation (Data Access, Reader, and Writer accounts). Click Next to continue.
Operations Manager accounts
Select No to send Customer Experience and Error reports. Select Next to continue.
Improvements and error reporting
On the Microsoft Update screen – choose to use updates or not. Updates are manged by SCCM but in case anything is missed On is selected here. Select Next to continue.
Add screenshot.
The Installation Summary is presented. Select Install.
Installation Summary
Close when completed.
The Management Server will be very busy (CPU) for several minutes after the installation completes. Before continuing it is best to give the Management Server time to complete all post install processes, complete discoveries, configuration, etc. 45 minutes is typically sufficient.
Creation of the Secondary Operations Management Server (SCOM02)
Log on using your domain user account that is a member of the OMAdmins group.
Run Setup.exe. Click Install
Select the following, and then click Next:
- Management Server
Operations Console
Management server and Operations console
Keep the default path and select Next. It will peform a verification on your system after selecting next.
default path
If there are any errors, go back and fix them before installing Operations Manager. Select Next to continue.
Prerequisites check
Select “Add a management server to an existing management group” and click Next.
Selection options
Accept the license terms and click Next.
License
Enter the servername\instance hosting the Operations Manager Database. Select the correct database from the drop down.In this case the server is called DB01, the database is called OperationsManager. Select Next to continue.
Configure the database
On the accounts screen, choose Domain Account for ALL services, and enter in the unique DOMAIN\OMAA, DOMAIN\OMDAS accounts we created previously. Select Next to continue.
Domain accounts
Choose No to send Customer Experience and Error reports. Next.
Turn Microsoft Updates on or off for SCOM, Next.
Click Install.
Close when complete.
You have now installed Operations Manager for SCOM01 and SCOM02. Now we will install SQL Reporting for Operations Manager on the DB01 Server.