How to Move the Operations Manager Reporting Server in Operations Manager 2007

  • Article

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

You can move the Microsoft System Center Operations Manager 2007 reporting server component to a new server, or reinstall the component on the original server.

Important

Moving a reporting server is supported only on the Service Pack 1 or R2 version of System Center Operations Manager 2007.

The high-level steps of moving the Operations Manager reporting server are as follows:

  1. Back up the OperationsManagerDW database.

  2. Note the accounts that are being used for the Data Warehouse Action Account and for the Data Warehouse Report Deployment Account. You will need to use the same accounts later, when you reinstall the Operations Manager reporting server.

  3. Uninstall the current Operations Manager reporting server component.

  4. Restore the original OperationsManagerDW database.

  5. If you are reinstalling the Operations Manager reporting server component on the original server, run the ResetSRS.exe tool to clean up and prepare the reporting server for the reinstallation.

  6. Reinstall the Operations Manager reporting server component.

During this move, Operations Manager stops storing data in the OperationsManagerDW database until you complete the Operations Manager reporting server reinstall.

Use the procedures in this topic to move the reporting server to a new server and verify the success of the move. You must back up any custom reports that were authored outside of Operations Manager 2007. For more information about this, see Moving the Report Server Databases to Another Computer in the SQL Server 2008 Books Online (https://go.microsoft.com/fwlink/?LinkId=151513).

Note

Ensure that you follow all steps precisely, as not doing so might result in data corruption.

To move the Operations Manager reporting server

  1. On the current Data Warehouse server, use SQL Server Management Studio to back up the OperationsManagerDW database (default name).

  2. On the current Operations Manager reporting server computer, uninstall the Operations Manager reporting server component as follows:

    1. Click Start, click Control Panel, and then click Add or Remove Programs if you are using Windows Server 2003, or click Programs and Features if you are using Windows Server 2008.

    2. In the Add or Remove Programs or Programs and Features dialog box, select System Center Operations Manager 2007 R2 Reporting Server, and then select Change.

    3. In the System Center Operations Manager 2007 R2 Reporting Setup Wizard, on the Operations Manager 2007 R2 Maintenance page, select Modify, and then click Next.

    4. On the Custom Setup page, configure the Reporting Server component with the This component will not be available option.

    5. Complete the wizard.

  3. On the Data Warehouse server, use SQL Management Studio to restore the OperationsManagerDW database backup that you created in step 1.

  4. If you are reinstalling the Operations Manager reporting server component on the original server, you must remove any data that is left from the original installation by doing the following:

    1. Copy the ResetSRS.exe tool from the SupportTools folder on the product CD to a local folder.

    2. Open a command prompt window using the Run as Administrator option and run the tool as follows:

      ResetSRS.exe <SQL Server instance name>

      Here, SQL Server instance name is the SQL Server instance that SQL Reporting Services is installed on, such as 'Instance1'.  If SQL Server is using the default instance, enter MSSQLSERVER.

    3. Open the Reporting Configuration Manager by clicking Start, pointing to Programs, pointing to Microsoft SQL Server 2005 or Microsoft SQL Server 2008, pointing to Configuration Tools, and then clicking Reporting Services Configuration.

    4. For SQL Reporting Services 2005, in the Configure Report Server page, check the status of the Web Service Identity item. If the status is not Configured (green), click that item, and then click Apply.

      Check the status of the rest of the items on that page. Configure any items that are designated with a red ‘X’, indicating an unhealthy configuration status.

  5. For SQL Server Reporting Services 2008, confirm the correct configuration of SQL Server 2008 Reporting Services. Click Start, point to Programs, point to Microsoft SQL Server 2008, point to Configuration Tools, and click Reporting Services Configuration Manager. Connect to the instance that you installed Reporting Services on.

  6. In the left pane, select the <servername>\SQLinstance. This displays the Report Server status in the results pane. Ensure that the Report Server Status is Started.

  7. In the left pane, select Scale-out Deployment and ensure that the Status column has the value of Joined.

  8. If Report Server is not started and the Scale out Deployment is not joined, check the configuration of Service Account, Web Service URL, and Database.

  9. Confirm that the SQL Server Reporting Services service is running. In Server Manager, expand the Configuration container for Windows Server 2008 or Services for Windows Server 2003 and select Services.

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

  11. On the new Operations Manager reporting server computer, run SetupOM.exe to reinstall the Operations Manager reporting server component by pointing the reporting server to the existing OperationsManagerDW database and using the original accounts for the Data Warehouse Action Account and the Data Warehouse Report Deployment Account, as follows:

    1. On the System Center Operations Manager 2007 R2 Setup page, select Install Operations Manager 2007 R2 Reporting.

    2. In the System Center Operations Manager 2007 R2 Reporting Setup Wizard, on the Custom Setup page, configure only the Reporting Server component for installation. Configure the Data Warehouse component with the This component will not be available option.

  12. Verify that the database move was successful as described in the next procedure.

To verify a successful move of the reporting server

  1. Verify that you can successfully run a report from the Operations Manager Operations console.

  2. Ensure that the health state of all management servers in the management group is Healthy.

    If the health state of any management server is Critical, open Health Explorer, expand Availability - <server name>, and then continue to expand until you can navigate to Data Warehouse SQL RS Deployed Management Pack List Request State. Check the associated events to determine if there is an issue accessing the OperationsManagerDW database.