Deploying SCOM 2007 R2 – Part1
In this multi part post, I will demonstrate the process of deploying System Center Operations Manager (SCOM) 2007 R2. After following these steps you can have a running SCOM R2 infrastructure that you can use to deploy agents and start monitoring. Following will be the architecture of our deployment.
- Single Management Group Deployment
- Operations Manager Database (OpsDB), DataWarehouse (OpsDW), ACS Database (ACSDB), SCOM Reporting and ACS Reporting on 1 Standalone server (no clustering). We will refer to it as DB server.
- Root Management Server with consoles deployed on 1 standalone server, referred to as RMS.
- 1 Standalone Management Server with Audit Collector referred to as MS.
- We will be using Windows Server 2008 R2 as OS and SQL 2008 SP1 for Database.
In this first part, we will cover the following components of our deployment.
- Complete the environmental prerequisites for SCOM R2 deployment
- Install the OpsDB on DB server
- Install the OpsDW on DB server
SCOM R2 Deployment Environmental Prerequisites
I have completed the following prerequisites before starting the SCOM deployment.
- Double checked that my Active Directory (AD) and DNS are healthy!
- My root domain doesn’t have a flat DNS namespace
- Checked that my AD domain functional level is Windows 2000 native or later
- Installed OS, Patches, Antivirus on the servers and joined them in the domain
- Created the following services accounts in my AD
- Management server Action Account (ScomMSA)
- SDK and Configuration Service Account (scomsdk)
- Agent Action Account (scomaac)
- Local Administrator Account for target devices for Agent Installation only (domain admin account)
- Data Warehouse Write Action Account (scomdwwrite)
- Data Reader Account (scomdwreader)
- Operations Manager Administrator account (scomadmin1)
- Create a Operations Manager Administrators group and added the Operations Manager administrator account to this group (ScomAdmins)
Install the OpsDB on DB server
- Logon to the DB server with an Admin account and add the Operations Manager administrators group, scommsa, scomsdk, scomdwwrite and scomdwreader to the local administrators group.
- Logon to the DB server with scomadmin1.
- Install SQL 2008 SP1 with reporting services. It will be a default installation with no special config required, so no screen shots here.
- Double click SetupOM.exe from SCOM R2 media to launch the SCOM R2 setup.
- In the prepare area, click Check Prerequisites to launch the prerequisites viewer.
- Select Operational Database, Reporting and Database Warehouse under the components and click on Check.
- Review the results and make sure that all checks are passed. In case of any warning or errors, resolve the dependencies reported and then click check. Repeat the process until all checks and passed and click close once done.
Note: I have not mentioned the server components prerequisites here, as the prerequisites checker is self explanatory. It will ask for IIS, .Net Framework etc. which can be added from Server Manager on Windows 2008 and there might be a few of them which you will have to download like ASP.Net Ajax Extensions. In any case, follow the prerequisite checker and you will be good.
- Click Install Operations Manager 2007 R2 under Install to start the installation process.
- On the Welcome page, click Next.
- On the End User License Agreement (EULA) page, accept the agreement, and then click Next.
- On the Product Registration page, optionally type appropriate values in the User Name and Organization fields, and then click Next.
- On the Custom Setup page, make sure that only Database component is set to available and all other components are set to not available. For this, click on the component and select appropriate options. Click Next.
- On the Management Group Configuration, type in the Management Group name, click on Browse and select the ScomAdmins group from AD. Click Next.
- On the SQL Server Database Instance page, select the SQL Server instance that you want to install on from the SQL Server database instance drop-down box. In our case it’s the same server where we are running this installation on. Accept the default value of SQL server port and click Next.
- On the Database and Log File Options, you can accept the default value of Database Name, Data and Log file location or change it as per your requirement. For the Database size, you can select the default or change it as per the sizing guidelines in design guide or you can use sizing helper.
- On the Operations Manager Error Reports page, optionally choose to send error reports to Microsoft and click Next.
- On the Microsoft Update page, optionally choose whether you want to use Microsoft Updates, and then click Next.
- On the Ready to Install the Program page, click Next when you are ready to start the installation.
- When setup completes successfully, click Finish on the Completing the System Center Operations Manager 2007 setup wizard page.
Install the OpsDW on DB server
- Click on the Install Operations Manager 2007 R2 Reporting under the install on the Start page.
- On the Start page, in the Install area, click the Install Operations Manager 2007 R2 Reporting link.
- On the Operations Manager 2007 R2 Reporting Setup welcome page, click Next.
- On the End User License Agreement (EULA) page, click I accept the license agreement to accept the agreement, and then click Next.
- On the Product Registration page, optionally type appropriate values in the User Name and Organization fields, and then click Next.
- On the Custom Setup page, make sure that only Data Warehouse component is set to available and all other components are set to not available. For this, click on the component and select appropriate options. Click Next.
- On the SQL Server Database Instance page, select the SQL Server instance that you want to install on from the SQL Server database instance drop-down box. In our case it’s the same server where we are running this installation on. Accept the default value of SQL server port and click Next.
- On the Database and Log File Options, you can accept the default value of Database Name, Data and Log file location or change it as per your requirement. For the Database size, you can select the default or change it as per the sizing guidelines in design guide or you can use sizing helper.
- On the Microsoft Update page, optionally select if you want to use Microsoft Updates and click Next.
- On the Ready to Install the Program page, click Next when you are ready to start the installation.
- When setup is completed successfully, click Finish on the Completing the System Center Operations Manager 2007 R2 Reporting Components setup wizard page.
- Let’s open the SQL Server Management Studio and verify the existence of OperationsManager and OperationsManagerDW.
This concludes first part of SCOM 2007 R2 deployment series. In the next part, we will look at the following components.
- Installing SCOM 2007 R2 RMS Server role along with consoles on RMS Server
Tags: Datawarehouse, Operations Manager, OpsDB, SCOM 2007 R2, Single Management Group
You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
April 4th, 2010 at 5:29 pm
[...] the first part of this post we have covered the following [...]
November 28th, 2010 at 3:56 pm
[...] wasn’t able to find any posts that had the same error as you. That being said, I ran across this. It goes over installing the database component for SCOM. The fact that it’s failing for you [...]
May 13th, 2011 at 12:29 am
When you install the DBs, does it install any System Center Service? Or does it just create the DBs on SQL Instance? I dont think it will create any SCOM services, just want to confirm this.
Thanks,
David
May 20th, 2011 at 12:50 am
Hi David,
I believe, it doesn’t not install any system center services. However, I do not have a SCOM setup now to verify.
Regards,
Vineet