70-247 Series: Part 7
Design and Deploy System Center (19%) Continued….
Installing Highly Available System Center Operations Manager
Prepare the Infrastructure
Before installing System Center Operations Manager, we're going to need to prepare the Infrastructure, this includes:
- Creating Service Accounts - I used domain accounts across the board, in smaller deployments, you can use local accounts for some of the service accounts. See TechNet for more information
- Management Server Service Accounts
- Management server action account
- System Center Configuration service and System Center Data Access service account. Also make sure the Data Access service account is a local administrator
- Management Server Service Accounts
- Reporting Server Service Accounts
- Data Warehouse Write account
- Data Reader account
- Installing 1 or more Database Instances (or sharing another)
- Installing a SQL Server Reporting Services Instance
Install Pre-requisites on each server
We'll be installing the Management Server, Web Console and Console on the same server, each of them will have the following pre-requisites installed/configured (Install in this order to avoid issues):
- .Net Framework 3.5 SP1 Feature and Hotfix
- .Net 4.0
- MS XML 6.0
- IIS with the following role services:
- 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
- Windows Authentication
- ISAPI and CGI Restrictions in IIS are enabled for ASP.NET 4. If .Net 4 doesn't appear in the ISAPI and CGI Restrictions, run: %WINDIR%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -r and restart
Installing the first combined management and web console server
Installing the second combined management web console server
The first few steps of the Installation on the second server are identical to the first few on the first server. The screenshot below starts off where the steps differ.
Installing Reporting Server
Before starting with the steps listed below, I have completed the installation of an SQL Server database instance that will be dedicated to Reporting Services. The database instance is hosted on the Windows Failover cluster that is hosting the other SQL instances.
Configure the Reporting Server
Installing SCOM in a scaled-out deployment is not supported, in fact, I’ve tried it and it doesn’t work, not one bit. Therefore you cannot provide HA for the SSRS Server, but you can for the reporting database, as we have done. For more details on supported configurations, see this link: http://blogs.technet.com/b/momteam/archive/2008/03/28/operations-manager-reporting-supported-ssrs-configurations.aspx
Install the SCOM Reporting Components
Install pre-requisites
- .Net 4.0
Note in the screenshot below, I am connecting the reporting server to one of the Management Servers. To provide higher availability, you can use the load-balanced network name.
That's it for SCOM, pretty straightforward, lets take a look at Data Protection Manager next!