Home About Disclaimer License

Medium Experts Exchange VIP Badge

Deploying SCOM 2007 R2 – Part3

In the second part of this post we have covered the following components.

  • Installed the SCOM 2007 R2 RMS Server role along with consoles on RMS Server

In this part, we will be:

  • Installing SCOM Reporting on DB Server
  • Installing SCOM 2007 R2 MS role on MS Server

Installing SCOM Reporting on DB Server

Well I am always afraid or rather bit more careful when working with SQL reporting services (SRS). I make sure not to mess with it and follow all steps carefully. Let us verify the SRS functionality before installing the SCOM reporting.

  • Logon to the DB server with scomadmin1.
  • Open SQL Management Studio and confirm the existence of ReportServer and ReportServer TempDB database.

clip_image002

  • On the DB server, go to Programs, SQL Server 2008, and Configuration Tools and click to open Reporting Services Configuration Manager. Make sure that Report Server status is set to started.

clip_image004

  • In the left pane select Scale-out Deployment and ensure that the Status column has the value of Joined.
  • Confirm that the SQL Server Reporting Services service is running. In Server Manager, expand the Configuration container and select Services.
  • In the Name column, find the SQL Server Reporting Services instance service and confirm that its status reads Started and that its Startup Type is Automatic.
  • Confirm the correct configuration of Report Manager Web site by opening Internet Explorer and browsing to http://DBServerName/reports.

clip_image006

  • When you are in the Report Manager Web site, click New Folder to create a new folder. Enter a name and description, and then click OK. Ensure that the new, created folder is visible on the Report Manager Web site.
  • Confirm that the ReportServer web site is working. Open Internet explorer and type http://dbservername/reportserver. You should get output similar to the following.

clip_image008

  • In the SQL Management Studio, navigate to Security, Logins and the select the account we will be using to install SOCM reporting. Right click this account and go to properties.

clip_image010

  • In the properties, click on User Roles and verify that this account is a member of sysadmin role.

clip_image012

  • The last step before stating the SCOM reporting setup is to provide the SQL Login rights to the Data Warehouse Write Account (scomdwwrite). For this create a new login for scomdwwrite in SQL and provide the rights to connect to SQL database engine.

clip_image014

  • Now we can run the SCOM reporting setup. Let’s follow the following steps for this.
  • Double click SetupOM.exe from SCOM R2 media to launch the SCOM R2 setup.
  • In the Install area, click the Install Operations Manager 2007 R2 Reporting link.
  • On the Welcome page, click Next.
  • On the End-User License Agreement page, select the I accept the terms in the license agreement option.
  • On the Product Registration page, enter the appropriate value in the User Name and Organization fields. Enter the 25-digit CD Key, and then click Next.
  • On the Custom Setup page, make sure that only Reporting 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.
  • If the Prerequisite Check page appears, and if all prerequisites have passed, click Next.
  • On the Connect to the Root Management Server page, enter the name of the RMS server, and then click Next.
  • On the Connect to the Operations Manager Data Warehouse page, in the SQL Server Database instance field, type the name of DB Server and in the SQL database name field, ensure that OperationsManagerDW is there. Check that the SQL Server Port field is set to 1433 and then click Next.
  • On the SQL Server Reporting Services Instance page, select the Reporting Services server instance name from the drop-down list, and then click Next.
  • On the Data Warehouse Write Account page, enter the Data Writer account (scomdwwrite) credentials, and then click Next.
  • On the Data Reader Account page, enter the Data Reader (scomdwread) account credentials, and then click Next.
  • On the Operational Data Reports page, optionally select whether to join the program, and then click Next.
  • On the Microsoft Update page, optionally select whether to use Microsoft Update.
  • On the Ready to Install the Program page, click Install.
  • When the installation is complete, click Finish.
  • Log on to RMS server with scomadmin1 and start the Operations Console.
  • In the Operations Console, select Reporting (on the bottom, left side of the console).
  • Under Reporting, select the Microsoft ODR Report Library, and then double-click any of the reports listed. By default, you should see the Management Group, Management Packs, and Most Common Alerts reports. This causes the selected report to be generated and be displayed in a new window.

Note: It may take up to 30 minutes for reports to populate.

  • Close the report window.

Installing SCOM 2007 R2 MS role on MS Server

  • Logon to the MS server with an Admin account and add the Operations Manager administrators group, scommsa and scomsdk to the local administrators group.
  • Logon to the MS server with scomadmin1.
  • 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 only Server under the components and click on Check.

clip_image016

  • 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.

clip_image018

  • 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 all the components are set to not available and only Management Server is set to available. For this, click on the component and select appropriate options. Click Next.

clip_image020

  • On the SC Database Server Instance page, enter the name of the DB server, Name of the Operations Manager Database and leave the port value to default 1433. Click Next.
  • Enter the credentials of ScomMSA account after selecting Domain or Local Computer Account and click Next.
  • Enter the credentials of scomsdk account after selecting Domain or Local Computer Account 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.
  • Click Finish on the Completion page. This completes the installation of Management Server. Pretty Simple duh..!

This concludes Third part of SCOM 2007 R2 deployment series. In the next part, we will look at the following components.

  • Installing ACS Collector on MS Server and Create the ACS Database
  • Uploading ACS Reports on DB Server

Tags: , , ,


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.


2 Responses to “Deploying SCOM 2007 R2 – Part3”

  1. [...] concludes second part of SCOM 2007 R2 deployment series. In the next part, we will look at the following [...]

  2. [...] the third part of this post we have covered the following [...]


Leave a Reply