How to Cluster the RMS in a Pre-Existing Management Group

Applies To: Operations Manager 2007 R2

The root management server (RMS) is a single point of failure for every management group. You can reduce this risk by placing the RMS role in a failover cluster that is running in quorum node configuration only. This procedure shows you how to cluster the RMS role after you have already installed the RMS role on a stand-alone server. You can place the RMS role in a cluster after the initial installation of the management group in Windows Server 2008-based clusters and in Windows Server 2003-based clusters. The procedure presented here assumes that you are using Windows Server 2008 Failover clustering. Your databases can be hosted on any of the following versions of Microsoft SQL Server:

• SQL Server 2005 with SP 1

• SQL Server 2005 with SP 2

• SQL Server 2005 with SP 3

• SQL Server 2008 with SP 1

To place the RMS role in a cluster, you have to perform the following steps:

1. Complete the pre-procedure checklist.

2. Prepare the Failover cluster nodes for the installation of the management server and RMS roles.

3. Install the Operations Manager 2007 R2 management server role on each cluster node.

4. Create the following RMS Failover cluster resources for the RMS: the System Center Management Service (HealthService), the System Center Management Configuration service (OMCFG), and the System Center Data Access service (OMSDK).

5. Create the virtual RMS by using the ManagementServerConfigTool.exe tool with the InstallCluster option.

6. Register the service principal name (SPN) by using the SetSPN.exe tool.

7. Verify that the clustered RMS is functioning correctly.

Supported and Unsupported Topologies

Supported Topology

This procedure works only for one starting RMS topology, which leads to a single ending RMS topology. The process is shown in figure 1. No other starting or ending RMS topologies are supported.

Figure 1: Supported topology

Three things happen in this procedure:

1. A clustered RMS server is created on a failover cluster that is not running any other workloads and that is configured as active/passive.

2. The pre-existing RMS is demoted from the RMS role and becomes a management server.

3. Any agents that had the pre-existing RMS as their primary management server are automatically redirected to the new clustered RMS. Also, all management servers are automatically redirected to the new clustered RMS.

Unsupported Topologies

Here are some examples of unsupported starting and ending topologies. If your Operations Manager 2007 R2 management group is in any of the configurations listed on the "Before" side of the diagrams, and you want to cluster the RMS, you must reconfigure the management group so that is in a supported configuration before you start the procedure.

Figure 2: Attempt to cluster the existing RMS

Figure 3: Attempt to cluster the existing RMS and to have agents report to the passive node

Figure 4: Attempt to move the RMS from one cluster to another cluster

Known Issues

• During this process, all agents that reported to the pre-existing RMS are redirected to the clustered RMS, and the pre-existing RMS (SRVR1) are demoted to be a management server (ms). If you do not want the agents to be owned by the RMS, you must manually redirect them to the demoted management server (SRVR1) or to other management servers in the management group.

• If the pre-existing RMS (SRVR1) is x64-based, and if the new clustered RMS will be x86-based, after the procedure, you have to manually demote the pre-existing RMS (SRVR1). The ManagementServerConfigTool.exe tool provides you with the command-line syntax that you must run to accomplish this.

• This procedure does not support using the Local System account for the System Center Data Access (OMSDK) or for the System Center Management Configuration (OMCFG) accounts. Domain accounts must be used and be available before you add the RMS cluster. In addition, you must ensure that the domain-based System Center Data Access account is listed as having the following fixed database roles for the OperationsManager database in SQL Server: configsvc_users, db_datareader, db_datawriter, db_ddladmins, and sdk_users.

Pre-Procedure Checklist

1. Verify that the Windows Server 2008-based failover cluster you want to use exists and is healthy. For installation and configuration guidance for Windows Server 2008-based failover clusters, see Failover Clusters (https://go.microsoft.com/fwlink/?LinkID=147285).

2. Ensure that the System Center Data Access and System Center Management Configuration accounts are configured to use a domain-based account. If you are using the Local system, change to domain-based accounts.

3. If you have to change to domain-based accounts, ensure that the System Center Data Access account is listed as having the following fixed database roles for the OperationsManager database in SQL Server: configsvc_users, db_datareader, db_datawriter, db_ddladmins, and sdk_users.

4. If you have changed to domain-based accounts, restart the System Center Data Access service, the System Center Management Configuration service, and the System Center Management service.

5. Restart the SQL Server and SQL Agent services.

6. Ensure that all System Center Operations Manager servers in the management group are running Operations Manager 2007 R2. Operations Manager 2007 SP1 and Operations Manager 2007 are not supported for this procedure. The agents in the management group can be Operations Manager 2007 SP1-based or Operations Manager 2007 R2-based agents.

7. Ensure that no agents are reporting to the management servers that are installed on either failover cluster node.

8. Disable notifications.

9. Close all instances of the Operations console that are connected to the management group.

10. On the pre-existing RMS, in the Applications and Services Logs tool, review the Operations Manager log for any error, warning, or critical events from the OpsMgr SDK Service. If you find any of these, resolve the issues before you start the RMS clustering procedure.

11. Plan an RMS network name.

12. Plan an RMS IP address.

13. Plan shared disk (clusterable disk) for the quorum drive and dedicated disk for the RMS files.

Clustering the Root Management Server in a Pre-Existing Operations Manager 2007 R2 Management Group

In this procedure, the management server and the user interface components are installed on the cluster nodes. They make use of the OperationsManager database that is hosted on an instance of SQL Server 2008.

The following procedures show how to install an Operations Manager 2007 R2 root management server on a Windows Failover cluster. Installing Operations Manager 2007 R2 root management server on a Windows Failover cluster involves the following tasks:

• Preparing the Windows cluster and creating a Service or Application for the RMS.

• Creating Physical Disk, IP Address, and Network Name resources in the RMS cluster group.

• Installing the secondary management servers on the cluster nodes and backing up the RMS encryption key.

• Creating Generic Service cluster resources in the RMS cluster group for the RMS System Center Management service (HealthService), the RMS System Center Data Access (OMSDK), and the RMS System Center Management Configuration (OMCFG) services.

• Backing up the OperationsManager database.

• Running the SecureStorageBackup tool with the Backup option on the pre-existing RMS to back up the RMS encryption key.

  Note

  If the RMS encryption keys are successfully backed up at the end of the RMS setup, it is not necessary to back them up again at this point.

• Running the SecureStorageBackup tool with the Restore option on all secondary management servers to place the RMS key on them.

• Running the ManagementServerConfigTool tool with the InstallCluster option to instantiate the RMS cluster.

• Bringing the RMS cluster group online.

• Moving the RMS cluster group to each node to complete the configuration.

• Testing to verify successful cluster installation.

• Optionally running the ManagementServerConfigTool tool with the AddRMSNode option to add cluster nodes to the RMS cluster that were inaccessible during the InstallCluster action described previously.

• Running SetSPN.exe after the InstallCluster action.

Step 1: Prepare the cluster nodes, the RMS cluster group, and the RMS cluster group resources

To prepare the cluster nodes, the RMS cluster group, and the RMS cluster group resources

1. On each RMS cluster node, ensure that the domain Operations Manager Administrators security group has been added to the local Administrators group.

2. Ensure that each cluster node meets the prerequisites for the management server and User Interface components:

   • Windows Server 2003 SP1 or Windows Server 2008

   • MDAC version 2.80.1022.0 or later

   • .NET Framework version 2.0

   • .NET Framework version 3.0 features

   • WSMAN v 1.1 (Only required if UNIX/Linux computers will be monitored in this management group).

3. Add the System Center Data Access (OMSDK) service and System Center Management Configuration (OMCFG) service account to the Local Administrators group on each node of the RMS cluster.

4. Log on to the cluster node that will be the primary owning node for the RMS with an account that is a member of the Administrators group.

5. Start the Failover Cluster Management tool from Administrative Tools.

6. If this is the first time that the Failover Cluster Management tool has been run, you will be prompted to connect to a cluster. Select the Manage a cluster option from the Action drop-down box and either enter or browse for the cluster name for the Cluster or server name box.

7. In the Failover Cluster Management tool, right-click the Services and Applications folder, and then click Configure a Service or Application to start the High Availability Wizard.

8. On the Before You Begin page, click Next.

9. On the Select Service or Application page, select Other Server, and then click Next.

10. On the Client Access Point page, type in the network name that you have planned for your RMS. This name will be registered in DNS as an A record.

11. Click the address box and type the IPv4 address that you have planned for the RMS. This is the publicly accessible address for the RMS.

12. Click Next.

13. On the Select Storage page, select the disk resource that will be used for the RMS. This should not be the quorum disk.

14. Click Next.

15. On the Select Resource Types page, click Next.

16. On the Confirmation page, review the information, and then click Next.

17. On the Summary page, optionally review the report, and then click Finish.

18. Right-click the application that you just created, and open its properties. On the General tab, optionally select a preferred owner node and on the Failover tab, accept the default failover values and ensure that the Prevent failback option is selected.

19. Click OK.

Step 2: Check the prerequisites for the management server installation

To check the prerequisites for the management server installation

1. Log on to the cluster node that will be the primary owning node for the RMS application with an account that is a member of the Administrators group.

2. Ensure that the RMS application is owned by the node that you are logged on to. For example, in a two-node cluster, log on to node 1, open Failover Cluster Management, and, in the navigation pane, select the RMS application. The value in the Current Owner field for the RMS application should be the node that you are logged on to. If it is not, right-click the RMS application and move it to node 1.

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

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

5. In the Components box, select the Server and Console components, and then click Check.

   Note

   When these components are selected, the Prerequisite Viewer checks for the presence of Windows Server 2003 SP1, MDAC version 2.80.1022.0 or later, .NET Framework version 2.0, .NET Framework version 3.0 components, and for WSMAN v1.1.

   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 checks as many times as necessary until a Passed evaluation is achieved on all items.

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

7. Repeat this procedure on all nodes in the cluster.

Step 3: Install management servers on the cluster nodes

Perform this procedure on every cluster node that will participate in the RMS cluster.

To prepare the cluster and install management server and user interface components

1. Log on to the cluster node that will be the primary owning node for the RMS with an account that is a member of the Administrators group.

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 Install Operations Manager 2007 R2. This starts the Operations Manager 2007 R2 Setup Wizard.

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, and then click Next.

6. On the Product Registration page, enter the appropriate values in the User Name and Organization fields. Enter your 25-digit CD Key, and then click Next.

7. On the Custom Setup page, leave the management server and User Interfaces options set to This component, and all dependent components, will be installed on the local disk drive. Set the Database, Command Shell, and Web Console components to This component will not be available, accept the default installation location, and then click Next.

8. On the SQL Server Database Instance page, type the SQL Server name and database instance in the SQL Database Name box. This is in the format of SQL Server\SQL Instance. If the SQL Server database was installed in the default instance, you only have to enter the SQL Server 2008 name that is running the OperationsManager database.

9. Check that the SQL Database Name field reads OperationsManager.

10. Check that the SQL Server Port field has the value of 1433.

    Note

    If you have chosen a different port for SQL Server communications and have already configured that port in SQL Server, you should enter that value here; otherwise, accept the default value of 1433. If you have installed SQL Server using a named instance, type in the dynamic port value.

11. Click Next.

12. On the Management Server Action Account (MSAA) page, accept the default Domain or Local Computer Account option, enter the credentials of the MSAA, and then click Next.

    Note

    By using a domain-based account, it will be much easier to perform discovery and push agent installation later on than if you chose the Local System account.

13. On the SDK and Config Service Account page, select the Domain or Local Account option, enter the credentials for the System Center Data Access and System Center Management Configuration service account, and then click Next.

    Note

    In this configuration, the account must be a domain account, because reporting is installed on a separate server. This account must have permissions on the reporting system.

    Note

    If you receive an Account Verification Error when you click Next, it is most likely that you mistyped the credentials or the SDK and Config service account was not added to the local Administrators group.

14. On the Customer Experience Improvement Program page, optionally indicate whether you want to join this program, and then click Next.

15. On the Microsoft Update page, optionally indicate whether you want to use the Microsoft Update services to check for updates, and then click Next.

16. On the Ready to Install the Program page, click Install when you are ready for the installation to proceed.

17. On the Completing the System Center Operations Manager 2007 R2 Setup Wizard page, clear the Start the Console check box, and clear the Back up Encryption Key check box, and then click Finish.

    Important

    Even though the Operations console has been installed, do not launch the console at this point. Clear the Launch the Operations Console check box to prevent the Operations console from launching.

    Note

    If setup fails, it gives you a value to search on and a link to open the setup log.

18. Set the System Center Data Access service and the System Center Management Configuration service to start manually on all cluster nodes that will be in the RMS cluster.

Step 4: Prepare the RMS cluster resources

In this procedure, you create cluster resources out of the System Center Management service (HealthService), the System Center Management Configuration service (OMCFG), and the System Center Data Access service (OMSDK). These are the RMS resources that can fail over between cluster nodes along with the network name, IP address, and physical disk.

To prepare the RMS cluster resources

1. Log on to the node that is the owner of the RMS application with an account that is a member of the Administrators group.

2. In Failover Cluster Management, in the navigation pane, right-click the RMS application, and then select Add a resource 4-Generic Service.

3. On the Select Service page, select the System Center Management Service, and then click Next.

4. On the Confirmation page, click Next.

5. On the Summary page, click Finish.

6. In the summary pane of your RMS application, right-click the System Center Management resource, and open its properties.

7. On the Dependencies tab, click Insert, and select the shared disk that you prepared for the RMS cluster from the Resource list.

8. Click Insert again and select the network name from the Resource list.

9. Click Apply.

10. Click OK.

11. Repeat the same process for the System Center Management Configuration service and the System Center Data Access service.

Step 5: Create the virtual RMS

To create the virtual root management server

1. Ensure that the file share with the encryption key is accessible by all cluster nodes. This is used for distributing the RMS Key.

2. If you successfully backed up the encryption key at the end of RMS setup, you can skip to step 5.

3. On the stand-alone RMS , as an Administrator, open a Command Prompt window and change the current directory to the Operations Manager installation folder; for example, cd\Program Files\System Center Operations Manager 2007.

4. To back up the RMS Key, type the following, where <fileshare> is a share accessible to all cluster nodes:

   SecureStorageBackup.exe Backup \\<fileshare>\<filename>.bin.

   Note

   This starts the Encryption Key Backup or Restore Wizard. Enter a password. It must be at least eight characters long and must include at least one symbol. You must confirm the password to create the encryption key file.

5. Log on to each secondary management server computer that is a node in the RMS cluster with an account that is a member of the Administrators group.

6. On each secondary management server, navigate to the Operations Manager installation directory and start SecureStorageBackup.exe as an administrator.

7. This starts the Encryption Key Backup or Restore Wizard. On the Introduction page, click Next.

8. On the Select Action page, select the Restore the Encryption Key option, and then click Next.

9. On the Provide a Location page, type in the path or browse to the encryption key file, and then click Next.

10. On the Provide a Password page, type in the password that you used when you backed up the encryption key, and then click Next.

11. Click Finish.

12. Repeat this procedure on each cluster node that will be participating in the RMS cluster.

13. On the computer running SQL Server and hosts the OperationsManager database, open the SQL Server Management Studio tool, expand the Databases folder, and select the OperationsManager database. Right-click, and then select Tasks, and then click Back Up to start a backup. On the Back Up Database - OperationsManager page, ensure that the Backup type value is set to Full, give the Backup set an appropriate name, and set the Backup set will expire value to a date in the distant future. In the Destination box, for the Back up to value, select Disk and add an appropriate disk location to hold the backup, if one is not already present, and then click OK.

    Important

    When you run the ManagementServerConfigTool tool to create the RMS cluster, you are advised to back up the OperationsManager database because irrecoverable damage can be done by creating the RMS cluster if something is done incorrectly.

14. Log on to the RMS application-owning node with an account that is a member of the Administrators group and is in the Operations Manager Administrator role.

15. In Failover Cluster Management, expand the cluster, and ensure that the RMS application is owned by the node that you are logged on to.

16. Navigate to the Support Tools directory on your source media and locate the operating system architecture folder that corresponds to the operating system architecture that is on the cluster nodes (AMD64 or i386 or ia64).

17. Copy the ManagementServerConfigTool.exe file to the System Center Operations Manager 2007 installation directory.

18. On the pre-existing RMS, open the Operations console and navigate to the Administration view.

19. In the Administration view, open the Management servers container which is under Device Management. In the results pane, you should see the pre-existing RMS with the value of Yes in the Root Management Server column. You should also see all of the cluster nodes that you installed secondary management servers on listed and with the value of No in the Root Management Server column.

    Important

    Check that the System Center Data Access and the System Center Management Configuration services on all cluster nodes have their startup type configured as Manual.

20. On the RMS application owning node, as an Administrator, open a Command Prompt window, type cd <path to Operations Manager installation directory>, and then press ENTER.

21. To instantiate the RMS cluster group as a cluster, type the following, where G is the disk resource that is allocated to the cluster group that is being used to create this virtual root management server and where <VirtualServerNetbiosName> is the network name resource allocated to the same cluster group:

    ManagementServerConfigTool.exe InstallCluster /vs:<VirtualServerNetbiosName> /Disk:G

    The value you enter for <VirtualServerNetbiosName> must be the value that appears in the Name box on the General tab of the Properties dialog box.

22. You will be prompted with this message: Running this tool can cause irreversible damage to your Operations Manager DB. Please backup your DB before continuing. Continue the Install Cluster action? (Y/N):. Type Y.

    Note

    ManagementServerConfigTool.exe InstallCluster installs the RMS as a clustered service on every available node in the cluster and demotes the pre-existing RMS to a management server.

23. In Failover Cluster Management, right-click the RMS application and click Bring this Service or application Online to bring all the RMS applications online.

24. Open Failover Cluster Management and right-click the RMS application. Select Move this service or application to another node and select the next node in the cluster. Repeat this so that the RMS application is moved to each node of the cluster.

    Important

    The RMS application must be moved and come online successfully on each cluster node to set the state of the services correctly on each node at this time. Do not skip this step.

25. Restart the System Center Management Service on the pre-existing RMS. This is necessary so that it recognizes that it has been demoted from RMS to a management server.

26. Open the Operations console. You will be prompted to connect to the RMS. Type in the <VirtualServerNetBIOS> name of the clustered RMS.

27. Open the Administration view and expand the Management Servers container under Device Management.

28. In the results pane you should see the server that was the pre-existing RMS listed and with a value of No in the Root Management Server column. This indicates that it has been successfully demoted to a secondary management server. You should see the VirtualServerNetBIOS name of the clustered RMS listed and with a value of Yes in the Root Management Server column. You should not see the individual cluster nodes listed at all.

    Warning

    If you do not see these results in the Operations console, the InstallCluster action did not complete successfully, and you have to follow the steps in the “Recovering from a Failed InstallCluster Action” procedure.

The clustered RMS setup is completed.

To recover from a failed InstallCluster action

1. Shut down all the cluster nodes that are hosting management servers.

2. Shut down the pre-existing RMS server.

3. Logon to the SQL Server that hosts the OperationsManager database with SQL Administrator rights and follow the How to Restore Operations Manager 2007 Databases (https://go.microsoft.com/fwlink/?LinkId=180782) procedure to restore the OperationsManager database.

4. After the OperationsManager database has been successfully restored, start the pre-existing RMS, and open the Operations console.

5. Examine the Alerts view for any alerts regarding the pre-existing RMS, and fix the issues indicated in the alerts, and then resolve the alerts.

6. Wait 15 minutes to see if any new alerts are raised regarding the pre-existing RMS. If no alerts are raised, and the pre-existing RMS show a green health state, proceed to the next step; otherwise, repeat steps 5 and 6 until there are no alerts regarding the pre-existing RMS and its health state is green.

7. In the Operations console, navigate to the Management Servers container and delete all the cluster nodes that are running secondary management servers.

8. Start all of the cluster nodes that are secondary management servers and log on with an account that is a member of the Administrators group.

9. Uninstall all Operations Manager 2007 R2 components via Control Panel, Programs and Features.

10. On one of the cluster nodes, open the Failover Cluster Management tool and select the RMS application that you previously created. Ensure that the application is owned by the node that you are on.

11. In the results pane, under Other Resources, delete the System Center Data Access, the System Center Management and the System Center Management Configuration resources.

12. Resume and follow all steps starting with the Installing Management Servers on the Cluster Nodes procedure earlier in this topic.

Step 6: Register the SPN

Use this procedure to correctly register the SPN of the RMS.

To use SETSPN

1. Log on to the owning node with an account that is a member of the Administrators group in the domain.

2. Open a Command Prompt window using the Run as administrator option.

3. Use the following command, where <domain>\<user name> is the account that the Failover Cluster service is running under, where the value for <VirtualManagementServerFQDN> is the same name you use for <VirtualManagementServerNetbios> with the domain extension appended, and where the value for <VirtualManagementServerNetbios> must be the value that appears in the Name box on the Parameters tab of the Properties dialog box for the network name resource: runas /user:<domain>\<user name> "SetSPN.exe -A MSomHSvc/<VirtualManagementServerFQDN> <VirtualManagementServerNetbios>" You must do this for both the FQDN of the virtual RMS server and for the NetBIOS name. For example: SetSPN –A MSomHSvc/cRMS cRMS will set the NetBIOS name and SetSPN –A MSomHSvc/cRMS.lab.demo cRMS will set the FQDN.

4. In the Command Prompt window, type setspn –L <rmsservercomputername>. In the list that appears, if the MSomHSvc SPN has been registered correctly, you see it listed. For example, you should see: MSOMHSvc/<RMS Virtual NetBIOS name>MSOMHSvc/<RMS FQDN>

5. If the SPN is listed, but is incorrect, run SetSPN -D MSOMHSvc/<RMS Node1> <Virtual RMS Name> to delete it, and then run the SetSPN -A MSOMHSvc/cRMS cRMS and SetSPN -A MSOMHSvc/cRMS.lab.demo cRMScommands to register it.

Step 7: Prepare an inaccessible management server

The following procedure is required only if, in bringing the cluster group online, the output stated that you are required to run the ManagementServerConfigTool.exe tool by using the AddRMSNode action on any of the non-root management server cluster nodes. This is most likely caused by a cluster node that is not accessible when the InstallCluster action was executed, or you are adding a new node to the cluster.

To prepare inaccessible management servers

1. Log on to the computer that hosts the management server as a member of the Administrators group.

2. Open the services snap-in and if the startup type for the System Center Data Access Service is set to Disabled, change it to Manual.

3. As an administrator, open a Command Prompt window, change directories to the installation folder, and type the following:

   ManagementServerConfigTool.exe AddRMSNode /vs:<VirtualServerNetbiosName> /Disk:<VirtualServer Disk Resource>

   VirtualServerNetbiosName is the Network Name resource allocated to the same cluster group. The value you enter for VirtualServerNetbiosName must be the value that appears in the Name box on the General tab of the Properties dialog box for the Network Name Cluster resource.

   VirtualServerDiskResource is the disk resource allocated to the cluster group being used to create this virtual root management server. The Disk location can be found in the results pane of the properties for the RMS application.

Step 8: Test the cluster installation

Use the following procedure to test the cluster installation.

To test an Operations Manager 2007 cluster

1. In the Operations console, click Administration.

   Note

   When you run the Operations console on a computer that is not a management server, the Connect To Server dialog box appears. In the Server name text box, type the name of the RMS Server (the cluster virtual server name) that you want the Operations console to connect to.

2. In the Administration pane, expand Administration, expand Device Management, and then click Management Server.

3. In the Management Servers pane, the RMS Server Network Name should appear with a health state of Healthy.

4. In the Administration pane, click Agentless Managed.

5. In the Agentless Managed pane, the entry for each node in the cluster should appear with a health state of Healthy.

Post-Procedure Checklist

After you successfully complete the RMS clustering procedure, perform the tasks in the following checklist.

• Re-enable notifications.

• All agents that were reporting to the pre-existing RMS have been redirected to the clustered RMS. If this is not the configuration that you want, you must manually reassign the desired agents to another management server in the management group.

• If you have System Center Operations Manager 2007 R2 Reporting installed, you must configure it to point to the new RMS.

• If you have System Center Operations Manager 2007 R2 Reporting installed, you must configure the OperationsManagerDW database to point to the new RMS.

• If you have the System Center Operations Manager 2007 R2 Web console installed, you must configure it to point to the new RMS.

To configure the reporting server with the name of the new root management server

1. Log on to the reporting server.

2. Navigate to the installation folder of SQL Server Reporting Services, for example, %ProgramFiles%\Microsoft SQL Server\MSSQL.2\Reporting Services\ReportServer if you are using SQL Server 2005 or %ProgramFiles%\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer, if you are using SQL Server 2008.

3. Open the rsreportserver.config file in Notepad, and locate the two instances of <ServerName>ServerName</ServerName>, where ServerName is the name of the original root management server. Change ServerName to be the name of the new root management server.

4. Save the file, and then close Notepad.

5. Open the registry and locate the key HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Reporting.

6. Change the DefaultSDKServiceMachine value to be the name of the new root management server.

To configure the data warehouse server with permissions for the new root management server

1. On the server hosting the data warehouse, open Microsoft SQL Server Management Studio, and in the Object Explorer pane, navigate to Security, and then expand Logins.

2. Locate the account that corresponds to the new root management server and on which the System Center Data Access Service is running (if it is running under the Local System account, the format is <domain\computername$>).

3. Right-click the account and select Properties.

4. In the Login Properties dialog box, in the Select a page pane, select User Mapping.

5. In the Users mapped to this login list, in the Map column, select the box that corresponds to the OperationsManagerDW database.

6. In the Database role membership for: OperationsManagerDW list, ensure that the following items are selected: configsvc_users, db_datareader, db_datawriter, db_ddladmin, and sdk_users.

7. Click OK to save your changes and to close the Login Properties dialog box.

To configure the Web console with the name of the new root management server

1. Log on to the Web console server.

2. Navigate to the installation folder of the Web console (by default, %ProgramFiles%\System Center Operations Manager 2007\Web Console).

3. Open the Web.config file in Notepad.

4. Locate the line ‘<add key="MOMServer" value="RootManagementServer "/>’, where RootManagementServer is the name of the original root management server. Change RootManagementServer to be the name of the new root management server.

5. Save your changes, and then close Notepad.