Welcome  |  Sign in
Skip Navigation Links
System Center Operations Manager TechCenter
Printer Friendly Version      Send     
Click to Rate and Give Feedback
TechNet
TechNet Library
Systems Management
System Center
Operations
 How to Promote a Management Server ...
How to Promote a Management Server to a Root Management Server Role in Operations Manager 2007

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 OperationsManager 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 (OpsMgr Health Service, the OpsMgr Config Service, and the OpsMgr SDK Service) for that clustered Root Management Server are stopped. 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.
  • 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.
  • 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 services described above are stopped, and then perform the PromoteRMS action on the active node of the cluster.
  • 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), then 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 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’, then the SQL Broker is disabled, 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 SecureStorageBackup.exe and the ManagementServerConfigTool.exe tools 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, and then change the folder to the installdir folder.

  3. Type the command:

    SecureStorageBackup.exe Restore <filename>

    Where filename is the Root Management Server encryption key backup file.

  4. Provide password as required.

  5. On the management server, open a command prompt window, and then type the command:

    ManagementServerConfigTool.exe PromoteRMS

  6. 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 command: ManagementServerConfigTool.exe UpdateDemotedRMS
    2. Delete the existing sub-folders 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.

  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 SDK Service is running (if 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, and then select User Mapping.

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

  6. In the Database role membership for: OperationsManagerDW list, ensure that the following items are checked: 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 onto 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, 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, 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'
© 2008 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Page view tracker