How to Promote a Management Server to a Root Management Server Role in Operations Manager 2007

  • Article

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

Use the following procedures to promote a management server to a root management server role, and then, if needed, to reset the value of ENABLE_BROKER in the Operations Manager database to 1.

Some of the high-level guidelines for promoting management servers are:

  • In a failure recovery scenario, you can change the root management server by promoting another management server to the role of root management server. In this scenario, the management server that you plan to promote to root management server must have already been installed before the failure of the current root management server occurred.

  • If you promote the root management server role away from a clustered root management server, you must ensure that the services (the System Center Management Service, System Center Management Configuration Service, and System Center Data Access Service) for that clustered root management server are offline. These services might be already stopped (for example, as a result of the clustered root management server no longer being in operation). However, if these services are still running, you must manually stop them from within Cluster Administrator if you are using Windows Server 2003 or Failover Cluster Management if you are using Windows Server 2008.

    • For clustered Operations Manager 2007 SP1, never let the HealthService run on any node of the clustered RMS while the another management server is promoted to the RMS role.

    • For clustered Operations Manager 2007 R2, never let the System Center Management service run on any node of the clustered RMS while another management server is promoted to the RMS role.

  • After promoting the root management server role away from a clustered root management server, you cannot configure the individual nodes as management servers. This scenario is not supported, and therefore you should not use the UpdateDemotedRMS action on these nodes. If you will not be using the cluster again, uninstall all Operations Manager 2007 components from the cluster node computers

  • In Operations Manager 2007 SP1, it is possible to promote the root management server back to the original clustered root management server configuration. To do this, you must first ensure that the cluster RMS group (Windows Server 2003) or Service or Application (Windows Server 2008) is offline, and then perform the PromoteRMS action on the active node of the cluster. Failure to take the cluster resources offline will result in corrupting your OperationsManager database

  • In a scenario where a management server was promoted to root management server and the original root management server was not demoted at that time, (for various reasons such as connectivity issues or hardware problems with the computer), if at a later time the original server recovers and you want to use it again as the root management server, you must first demote it to a management server role. You must do this because you have already promoted another management server to a root management server role.

    After you demote the original root management server to a management server role by running the UpdateDemotedRMS action of the ManagementServerConfigTool locally on that original root management server, you can re-promote it to the root management server role.

Note

Running the PromoteRMS action automatically demotes the previous root management server to a management server role unless the original root management server is not accessible or if /DemoteExistingRMS: is set to ‘True’ (which will delete, rather than demote, the previous root management server from the database).

The high-level steps for promoting a management server to root management server are:

  1. Promote a management server to a root management server role.

  2. Configure the reporting server with the name of the new root management server.

  3. Configure the Web console with the name of the new root management server.

  4. Set ENABLE_BROKER to 1 if needed. After you successfully complete the promotion, you might need to set the value of the SQL Broker Availability Monitor to 1. Check the state of the SQL Broker Availability Monitor by running the following SQL query:

    SELECT is_broker_enabled FROM sys.databases WHERE name='OperationsManager'

    If the query result is ‘0’, the SQL Broker is disabled and you must re-enable it by using the 'To set ENABLE_BROKER to 1' procedure later in this topic.

To promote a management server to a root management server role

  1. On the management server that you want to promote, copy the ManagementServerConfigTool.exe tool from the SupportTools folder of the installation media to the installation folder (by default, C:\Program Files\System Center Operations Manager 2007), called installdir in this example.

  2. Open a command prompt window using the Run as Administrator option, and then change the folder to the installdir folder.

  3. Type the following command:

    SecureStorageBackup.exe Restore < filename >

    Here, filename is the root management server encryption key backup file.

  4. Provide a password as required.

  5. On the management server, open a command prompt window using the Run as Administrator option, and then type the following command:

    ManagementServerConfigTool.exe PromoteRMS

  6. You will see two warnings come up. The first warns you to backup your OperationsManager database, the second warns you to take the System Center Management, System Center Management Configuration and System Center Data Access services offline if your RMS is on a cluster. Type in Y for both.

  7. Demote the original root management server to a management server by doing the following on the original root management server:

    Note

    This step is required only if the original root management server is to be used as a management server.

    1. Type the following command: ManagementServerConfigTool.exe UpdateDemotedRMS. Type in Y to the backup database warning.

    2. Delete the existing subfolders of the Health Service State folder in the installdir.

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 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’s running under LocalSystem, 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:db_datareader, db_datawriter, and db_ddladmin.

  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.

To set ENABLE_BROKER to 1

  1. Open SQL Server Management Studio.

  2. In the Connect to Server dialog box, select the appropriate values in the Server type list, in the Server name list, and in the Authentication list, and then click Connect.

  3. Click New Query.

  4. In the query window, enter the following query:

    ALTER DATABASE OperationsManager SET SINGLE_USER WITH ROLLBACK IMMEDIATE

  5. Click Execute.

  6. Enter the following query:

    ALTER DATABASE OperationsManager SET ENABLE_BROKER

  7. Click Execute.

  8. In the Connect to Server dialog box, select the appropriate values in the Server type list, in the Server name list, and in the Authentication list, and then click Connect.

  9. Click New Query.

  10. In the query window, enter the following query:

    ALTER DATABASE OperationsManager SET MULTI_USER

  11. Click Execute.

  12. Verify that ENABLE_BROKER is set to 1 by using the following SQL query:

    Select is_broker_enabled FROM sys.databases WHERE name='OperationsManager'