SCOM 2007 R2 – Rough Guide on SCOM 2007 R2 & Data Warehouse Installation
Everyone who has installed SCOM 2007 R2 with the SCOM data warehouse on multiple servers will know that it is quiet tricky to get it right the first time. Therefore I put some installation notes together right before the release of SCOM 2012. In this installation I have one SQL 2008 R2 server and one Windows 2008 R2 server. The Windows server will hold the SCOM 2007 R2 management server, reporting server and the web console.
1. User Accounts & Groups
In Active Directory Users and Computers, create six accounts:
Management Server Action account, e.g. SRV_OM7_MSAA
SDK and Configuration Service account, e.g. SRV_OM7_SDK
Data Reader account, e.g. SRV_OM7_READER
Data Warehouse Write Action account, e.g. SRV_OM7_WRITER
Operations Manager Administrator account. e.g. OMAdmin
SQL Server Reporting Services account. e.g. SRV_SSRS
Add all these accounts to the local administrators group on the futur SCOM server. Create a Operations Manager Admins group, e.g. OMAdmins. Add a the OMAdmin user account to the group.
2. SQL Server Installation
I installed SQL server on one Windows Server 2008 R2 server and SQL 2008 R2 Reporting service on the future management server.
SQL collation setting must be configured for SQL_Latin1_General_CP1_CI_AS
3. SCOM database and data warehouse database installation
Next install the SCOM databases. I use the DBcreateWizard to do this.
Log on to the SQL server with a account that has SQL sysadmin rights and local admin rights.
Use the DBCreateWizard.exe from the SCOM 2007 R2 installation media (/support tools/AMD64) to have the SCOM database created. Choose a management group name and select the OMAdmins group to have permission on the management group. In the same way create the data warehouse database.
4. Install SCOM management on the server
Log in to the SCOM with the same user that created the databases. This user must be a local admin on the SCOM management server and it needs to be in the OMAdmin group.
After the installation, log in with the OMAdmin account, start the console and verify that the installation completed.
5. Install SQL Reporting server
This installation could have happened earlier as well. It just needs to be done before the SCOM reporting service is installed.
I use SQL 2008 R2. Start the setup, and install the setup support files. Select SQL reporting feature. Use a domain account for the service account e.g. SRV_SSRS.
Important: Update the SQL Server Reporting service with the latest service pack before continuing with the configuration.
The reporting service needs to be configured once it’s installed. To do this start the Reporting Service Configuration Manager:
Verify the service account settings
Create the Reporting database
Apply the reporting web service URL
Apply the report manager URL
Do a backup of the encryption key
6. Install the SCOM 2007 R2 Reporting
On the reporting server, on the local groups look for a group name starting: SQLServerReportServerUser… Remove the string “_50”.
Start the installation wizard and on the Custom Setup page deselect Data Warehouse. Enter the Write and Reader account and start the installation.
After the installation, add the “_50” string to the local group again.
To verify the installation, log into the Operations Manager server with the OMAdmin account and start the Operations Manager console. Verify that the Reporting tab is available.
SQL Server Broker Service
Operations Manager Discovery, in addition to other workflows, is dependent on SQL Server 2005 and SQL Server 2008 Service Broker, which must remain enabled for Operations Manager 2007 to be fully functional.
Installing OpsMgr 2007 SP1 Reporting on Windows Server 2008
Using a Firewall with Operations Manager 2007
Error message when you try to install System Center Operations Manager 2007 Reporting: “The wizard was interrupted before Operations Manager 2007 could be installed”
Installing Operations Manager 2007 Reporting successfully
OpsMgr 2007: How to make your Reporting install a success
Gunter Danzeisen Gunter hat einen Abschluss in Informatik der Technischen Schule. Zusätzlich ist er zertifizierter Microsoft System Engineer (MCSE 2003) sowie zertifizierter Microsoft IT Professional (MCITP 2008).