Let’s continue our series for installing Microsoft System Center 2012 Operations Manager, in the first part we have discussed some of the new features in SCOM 2012 and we have seen how to do a proper sizing for your deployment using the Tool provided by Microsoft, and today we will go through planning for a clean deployment for SCOM 2012.
Please visit the first part before you continue reading the below steps, you can access it from here Installing Microsoft System Center Operations Manager “SCOM” 2012. Step by Step guide- Part 1- Introduction
Planning for a clean Installation of SCOM 2012
When deploying your SCOM Servers there are two possible scenarios, a Single Server or a Distributed Servers deployment, a Single Server deployment is only good for POCs, Evaluation or Management Packs development, not for production environments where you need to achieve a highly available and reliable deployment.
Distributed deployment on the other hand is distributing the Load among a number of servers that share the same Resource Pool “which i will talk about later”, it allows for features distributions among multiple servers. In this lab we will be installing a total of Five Servers to achieve high availability, the servers will hold the following roles:
- 2 Servers assigned as Management Servers with work load distributed among them along with the Console Server installed on both nodes.
- 2 Servers for a SQL Cluster the will host both the Operations Manager and the Data Warehouse databases.
- 1 Server that will be the Report Server with an SRS installed and will also host the Web Console Server.
You should always have two management servers in ANY environment. A second management server allows for failover and easy restore. All management servers are members of the All Management Servers Resource pool, which balances the monitoring load of your management group as new management servers are added, and provides automatic failover for monitoring.
A resource pool is a collection of management servers or gateway servers used to distribute work among themselves and to take over work from a failed member.
Due to the introduction of resource pools it is recommended that all management servers be connected by a low latency network. This means that if you are currently using management servers in multiple Data-centers or sites it is recommended that you move all management servers to a single data center and use gateway servers at the other sites.
Administrator Role Assignment
Operations Manager handles assignment of the Operations Manager Administrators role differently than previous versions. In System Center 2012 – Operations Manager, Setup automatically assigns the Administrators group on the local computer to the Operations Manager Administrators role. You must be logged on with an account that has local Administrator rights to run Setup on the first management server that you install; this ensures that you can open the Operations console after Setup is completed.
Required Accounts .. Reference (http://technet.microsoft.com/en-us/library/hh298609.aspx)
During setup, you are prompted for two accounts,you can use the same account for both services:
- Management server action account “This account is used to carry out actions on monitored computers across a network connection.”
- System Center Configuration service and System Center Data Access service “This account is one set of credentials that is used to update and read information in the operational database. Operations Manager ensures that the credentials used for the System Center Data Access service and System Center Configuration service account are assigned to the sdk_user role in the operational database.“
If you install Reporting, you are prompted for two additional accounts,these accounts are created as domain user accounts and added to the local Administrators group on the target server:
- Data Warehouse Write account “The Data Warehouse Write account writes data from the management server to the Reporting data warehouse and reads data from the operational database“
- Data Reader account “The Data Reader account is used to define which account credentials SQL Server Reporting Services uses to run queries against the Operations Manager reporting data warehouse.“
If you create a specific account for installation, this account must be a member of the sysadmin server role for Microsoft SQL Server, but also have access to the master database.
If you install multiple management servers, you are prompted for a management server action account and a System Center Configuration service and System Center Data Access service account each time you add a management server. You must provide the same account.
as i always do in my labs i will be using a single user for the deployment.
SQL Server Requirements
System Center 2012 – Operations Manager requires access to an instance of a server running Microsoft SQL Server 2008 SP1, SQL Server 2008 R2, or SQL Server 2008 R2 SP1. This instance can be located on a separate computer from the management servers in a distributed installation or on the first management server in the management group. In either case, the instance of Microsoft SQL Server 2008 SP1, SQL Server 2008 R2, or SQL Server 2008 R2 SP1 must already exist and be accessible before you start your first management server installation. The SQL Server Collation setting must be a supported value, and SQL Full Text Search must be enabled.
Preparing the Servers
Following we will be preparing each server for the deployment:
Management Servers and Operations Console.
- Operating System must be Windows Server 2008 R2 SP1.
- Important if you are going to install the web console on the Management server Please note that you must install IIS before installing .NET Framework 4. If you installed IIS after installing .NET Framework 4, you must register ASP.NET 4.0 with IIS. Open a Command prompt window by using the Run As Administrator option, and then run the following command:
- Both .NET Framework 3.5 Service Pack 1 (SP1) and .NET Framework 4
- Install .Net Framework 3.5 Sp1 using Server Manager
- Download and Install .Net Framework from here http://www.microsoft.com/en-eg/download/details.aspx?id=17851
- Download and Install Microsoft Report Viewer 2010 Redistributable Package
- Install and Download Microsoft .NET Framework 3.5 SP1 hotfix
The page tells you to contact Microsoft to obtain the Microsoft, i searched online and i found the hotfix with the same KB ID, you can obtain it from here The Thread pool do not work as expected
Operations Database and Data Warehouse Servers
- Operating System: Windows Server 2008 SP2 or Windows Server 2008 R2 SP1.
- Microsoft SQL Server: SQL Server 2008 SP1, SQL Server 2008 SP2, SQL Server 2008 SP3, SQL Server 2008 R2, SQL Server 2008 R2 SP1, SQL Server 2008 R2 SP2, SQL Server 2012, or SQL Server 2012 SP1.
- SQL Server Full Text Search is required.
- Both .NET Framework 3.5 SP1 and .NET Framework 4 are required.
I have Deployed SQL Server 2008 R2 on a cluster of 2 servers and enabled SQl Server Full text search during the installation.
Make Sure to the account used for installation is a member of the sysadmin role as mentioned before and also has access to the master database.
- Note Although SQL Server Reporting Services is installed on the stand-alone server, Operations Manager reports are not accessed on this server; instead, they are accessed in the Reporting workspace in the Operations console. If you want to access published reports via the web console, you must install the Operations Manager web console on the same computer as Operations Manager Reporting server.
- Both .NET Framework 3.5 SP1 and .NET Framework 4 are required
- Microsoft SQL Server: SQL Server 2008 SP1, SQL Server 2008 SP2, SQL Server 2008 SP3, SQL Server 2008 R2, SQL Server 2008 R2 SP1, or SQL Server 2008 R2 SP2.
- The Remote Registry service must be enabled and started.
- Microsoft SQL Server Reporting Services: Microsoft SQL Server: SQL Server 2008 SP1, SQL Server 2008 SP2, SQL Server 2008 SP3, SQL Server 2008 R2, SQL Server 2008 R2 SP1, or SQL Server 2008 R2 SP2.
- System Center 2012 – Operations Manager supports SQL Server Reporting Services in native mode only; do not use SharePoint integrated mode.
- Verify that the ReportServer and ReportServerTempDB databases in SQL Server Management Studio are created.
- Verify the correct configuration of SQL Server Reporting Services. Open the Reporting Services Configuration Manager.
Connect to the Report Server Instance.
- Ensure that the Report Server Status is Started.
Select Scale-out Deployment, and then ensure that the Status column has the value of Joined.
- If Report Server is not started and the Scale out Deployment is not joined, check the configuration of Service Account, Web Service URL, and Database.
- Confirm that the SQL Server Reporting Services service is running.
- Internet Information Services (IIS) 7.5 and later versions, with the IIS Management Console and the following role services installed:
- Selected website for web console: requires a configured http or https binding.
- Warning!! Installing the web console on a computer that has SharePoint installed is not supported.
- Installation of the web console requires that ISAPI and CGI Restrictions in IIS are enabled for ASP.NET 4. To enable this, select the web server in IIS Manager, and then double-click ISAPI and CGI Restrictions. Select ASP.NET v4.0.30319, and then click Allow.
Okay , that would be it for today , we have prepared our server with all the prerequisites, 2 Servers will be Management Servers along with the management console installed, another two on a SQL Cluster to host the Operations and Data Warehouse Databases, and the last server will host both the Report and Web Console features.
Next part we are going to fire-up the installation. Hopefully it’s going to be smooth one 🙂 , See you Guys !