Deploying Reporting in the Multiple Server, Single Management Group Scenario

  • Article

Applies To: Operations Manager 2007 R2, Operations Manager 2007 SP1

In this scenario, the Data Warehouse and the Operations Manager Reporting components are installed on separate servers. The Data Warehouse database is installed in the SQL Server Cluster and the Reporting services are installed on a stand-alone server that is hosting SQL Server Database and SQL Reporting Services. For a listing of the top ten Reporting Services installation issues see https://go.microsoft.com/fwlink/?LinkID=143359

Note

Although SQL Reporting Services is installed on the stand-alone server, Operations Manager Reports are not accessed on this server; instead, they are accessed in the Reports view in the Operations console. If you want to access Favorite reports via the Web console, then you must install the Operations Manager 2007 Web console component on the same computer as Operations Manager 2007 Reporting services and save the desired reports to the Favorites folder. The reports will appear in the My Workspace view in the Web console

Installation overview

  1. Run Install Operations Manager 2007 R2 Reporting on the stand-alone Reporting server, and choose to install the Reporting Server component only.

  2. Verify the health of Operations Manager 2007 Reports.

Before you start

  1. On the stand-alone server that is to be used for Reporting Services, add the following accounts and group to the Local Administrators group:

    • Domain MSAA

    • Domain SQL Service account

    • Domain SDK and Config Service account

    • Domain Operations Manager Administrators security group

    • Domain Data Reader and Data Writer accounts

    Note

    Before you continue with this procedure, be sure that the account you plan to use for the Data Warehouse Write account has SQL Login rights and is an Administrator on the computers hosting both the OperationsManager database and Reporting Data Warehouse database. Otherwise, setup fails and all changes are rolled back, which might leave SQL Reporting Services in an inoperable state.

    Note

    Both the Data Warehouse Write account and the Data Reader account must have logon locally rights on this server.

    The account that you use to run the Operations Manager 2007 Reporting installation must be a member of the following groups and roles.

    • Local Administrator – this is required by the Operations Manager 2007 Reporting installation and for configuring SQL Server Reporting Services.

    • Operations Manager Administrator role – this is required for configuring reporting roles and creating reporting instances.

    • SQL SysAdmin for the OperationsManager database – this is required for configuring dwsynch_users role.

    • SQL SysAdmin for the Data Warehouse database – this is required for configuring OpsMgrWriter and OpsMgrReader roles.

  2. Add the Application Server role to the stand-alone reporting server by using the Manage Your Server tool or manually install IIS by using the Add and Remove Programs tool.

  3. Install SQL Server 2005 on the stand-alone server with the SQL Server Database Services, Reporting Services in Native mode, not SharePoint Integrated mode and Workstation components, Books Online and development tools options.

  4. Apply SQL Server 2005 SP1 to the stand-alone reporting server and the KB918222 hotfixes for server, reporting, and tools. To obtain the hotfixes, see article 918222 in the Microsoft Knowledge Base (https://go.microsoft.com/fwlink/?LinkId=78950). Or install SQL Server 2005 SP2.

  5. Confirm the existence of the ReportServer and ReportServerTempDB databases in SQL Server Management Studio on the stand-alone server. Click Start, point to Programs, point to Microsoft SQL Server 2005, point SQL Server Management Studio, and connect to the default database instance. Open the Databases node and look for the two Reporting Services databases.

  6. Confirm the correct configuration of SQL Server 2005 Reporting Services. Click Start, point to Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and click Reporting Services Configuration to launch the Configure Report Server tool. Connect to the instance that you installed Reporting Services on.

  7. In the left pane, ensure that Server Status, Report Server Virtual Directory, Report Manager Virtual Directory, Windows Service Identity, Database Setup, and Initialization are all not in a Not configured state, any other state is acceptable. If they are not, select the item and follow the configuration instructions in the right pane.

  8. Confirm that the SQL Server Reporting Services service is running. Click Start, point to Settings, and select Control Panel. In Control Panel, select Administrative Tools, and open Services.

  9. In the Name column, find the SQL Server Reporting Services instance service and confirm that its status is Started and that its Startup Type is Automatic.

  10. Confirm that the Report Server Web site is functioning and accessible by browsing to https://servername/reportserver<$instance>. You should see a page with the <servername>/ReportServer<$INSTANCE> and the text Microsoft SQL Server Reporting Services Version #.##.####.## where the # is the version number of your SQL Server installation.

  11. Confirm the correct configuration of Report Manager Web site by opening Internet Explorer and browsing to http://<servername>/reports<instance>.

  12. When you are on 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.

For more information about how to verify a SQL Server Reporting Services installation see: https://go.microsoft.com/fwlink/?LinkId=137091

Installing Operations Manager Reporting on a Stand-Alone Server

In this procedure, you install the Operations Manager Reporting component on the stand-alone Reporting server. Due to changes that the Operations Manager 2007 Reporting component makes to SQL Server Reporting Services security, no other applications that make use of SQL Server Reporting Services can be installed on the same SQL instance.

To check for Operations Manager 2007 Reporting component prerequisites

  1. Log on to the server with the Operations Administrator account credentials.

  2. From your Operations Manager 2007 installation media, double-click SetupOM.exe to start the System Center Operations Manager 2007 R2 Setup on the Start page.

  3. Under Prepare, click Check Prerequisites to start the Prerequisite Viewer.

  4. In the Components box, select the Reporting component, and then click Check.

    Note

    When the Reporting component is selected, the Prerequisite Viewer checks for presence of Windows Server 2003 Service Pack 1, Microsoft SQL Server 2005 Reporting Services Service Pack 1, .NET Framework version 2.0, .NET Framework version 3.0 components. These are the minimum levels of components that are checked for; if you running SQL Server 2008 for example, then a status of passed is returned

    Note

    The results are displayed at the bottom of the Prerequisite Viewer. If there are any deficiencies, they are marked either as Warning or as Failed. Warnings can be ignored at the risk of degraded performance or other issues; Failed prerequisites must be fixed before the installation can proceed. You can close the Prerequisite Viewer, fix the items and rerun the Prerequisite Viewer to check as many times as it is necessary until a status of Passed is achieved on all items.

  5. When you are done with the Prerequisite Viewer, click Close.

To install Operations Manager 2007 R2 Reporting component

  1. Log on to the server with the Operations Manager Administrator account.

  2. On your installation media, start SetupOM.exe. This starts the System Center Operations Manager 2007 R2 Setup Wizard on the Start page.

  3. Under the Install heading, click the Install Operations Manager 2007 R2 Reporting link.

  4. On the Welcome page, click Next.

  5. On the End-User License Agreement page, select the I accept the terms in the license agreement option.

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

  7. On the Custom Setup page, ensure that the Reporting Server component is set to This component, and all dependent components, will be installed on the local disk drive, and that the Data Warehouse component is set to This component will not be available. To change the installation directory, click Browse, enter the appropriate path and folder name, and then click Next.

  8. If the Prerequisite Check page appears, and if all prerequisites have passed, click Next.

  9. On the Connect to the Root Management Server page, enter a value in the name field of the RMS Network Name Cluster resource, and then click Next.

  10. On the Connect to the Operations Manager Data Warehouse page, in the SQL Server Database instance field, enter the value that is in the name field of the SQL Network Name cluster resource. In the SQL database name field, ensure that OperationsManagerDW is there. Check that the SQL Server Port field is set to 1433, or if you have previously configured a different port for SQL Server communications, enter that value. Click Next.

  11. On the SQL Server Reporting Services Instance page, select the Reporting Services server instance name from the drop-down list, and then click Next.

    Note

    Installing Operations Manager 2007 Reporting Services integrates the security of the instance of SQL Reporting Services with the Operations Manager role-based security. Do not install any other Reporting Services applications in this same instance of SQL Server.

  12. On the Data Warehouse Write Account page, enter the Data Writer account credentials, and then click Next.

  13. On the Data Reader Account page, enter the Data Reader account credentials, and then click Next.

  14. On the Operational Data Reports page, optionally select whether to join the program, and then click Next.

  15. On the Microsoft Update page, optionally select whether to use Microsoft Update.

  16. On the Ready to Install the Program page, click Install.

  17. When the installation is complete, click Finish.

Note

Operations Manager Reports are accessed in the Operations console, in the Reporting view. After initial deployment, it can take up to 30 minutes for reports to appear.

To confirm the health of Operations Manager reports

  1. Log on to a management server with an Operations Administrator role account and start the Operations Console.

  2. In the Operations Console, select the Reporting View (on the bottom, left side of the console).

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

    Selecting the management packs report is particularly useful at this point because it provides you with a full inventory of the management packs that have been installed on your server.

  4. Close the report window.

Uninstalling Operations Manager Reporting Services

You can uninstall Operations Manager Reporting services through the Add or Remove Programs tool. If you do, you must also run the ResetSRS.exe tool found in the SupportTools folder of the Operations Manager installation media.

To uninstall Operations Manager 2007 Reporting Services component

  1. Log on to the Reporting Server with the Operations Manager Administrator account.

  2. Click Start, point to Control Panel, and then click Add or Remove Programs.

  3. From the list of currently installed programs, select System Center Operations Manager 2007 Reporting Server, and then click Remove. This uninstalls Operations Manager Reporting Server, and it does not uninstall SQL Server 2005 Reporting Services.

  4. When the uninstall is complete, copy the ResetSRS.exe tool to the root of the local hard drive.

  5. Open a Command Prompt window and change directories to the root of the local hard drive or wherever you copied the ResetSRS.exe tool, and then type c:\resetSRS.exe <SQLINSTANCENAME> where SQLINSTANCENAME is the name of the instance of SQL Server that SQL Reporting Services was installed in. If you installed in the default instance, use MSSQLSERVER for the <SQLINSTANCENAME> value.

  6. Click Start, point to Microsoft SQL Server 2005, point to Configuration Tools, and then select Reporting Services Configuration.

  7. On the left side, select Web Service Identity and on the right side click Apply. This restores the SQL Server Reporting Services installation to its pre-Operations Manager 2007 Reporting Server component state.