Prepare your environment to Operations Manager 2012 – Part III Moving the RMS role

Hi All,

To continue the serie about “Prepare your environment to Operations Manager 2012”, we have now to move the RMS role to a Windows Server 2008 R2 server and remove the Windows Server 2003 server.


I invite you first to read my previous post :
Prepare your environment to Operations Manager 2012 – Part I Actions Plan
Prepare your environment to Operations Manager 2012 – Part II Updating the SQL Server

Adding a new management server

The really first step is to add our brand new Windows Server 2008 R2 server as a management server in our existing Operations Manager Management Group. As this is a quite regular process, I will skip some screens.

First step, we have to install the .Net Framework 3.5.1.

Don’t forget to add your service accounts as Local Administrator of this new server.

Let’s starting the installation of this new management server.

We only have to install the Manager Server and the User Interfaces.

We have to specify our DB server (the new one, running SQL Server 2008 R2 SP1).

Specify the Action Account for this management server.

Specify now the SDK and Config Service Account.

We are new ready for the installation.

Installation done.

Don’t forget to apply the Cumulative Update 5 to this new management server.

CU5 Installed on our new management server.

if we take a look in the console, we could see that our new management server is working well.


Moving the RMS role

As our final goal is to remove the Windows Server 2003 server, we have to promote as RMS our new installed management server.

  • Make sure that you have a backup of the databases and all servers.
  • Backup the Key from the RMS by using SecureStorageBackup.exe and copy it to the MS that you want to promote.
  • Be sure to have all the services accounts passwords available.
  • Be sure that no agent, no Linux servers, no website, no network devices that are currently monitored by the RMS.
  • Run the command prompt as Administrator
To promote a management server to a root management server role
  • 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 FilesSystem Center Operations Manager 2007), called installdir in this example.
  • Open a command prompt window using the Run as Administrator option, and then change the folder to the installdir folder.
  • Type the following command:
    SecureStorageBackup.exe Restore < filename >
  • Provide the password as required.
  • On the management server, open a command prompt window using the Run as Administrator option, and then type the following command:
    ManagementServerConfigTool.exe PromoteRMS
To configure the reporting server with the name of the new root management server
  • Log on to the reporting server.
  • Navigate to the installation folder of Reporting Services for example, C:Program FilesMicrosoft SQL ServerMSRS10_50.MSSQLSERVERReporting ServicesReportServer 
  • 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.
  • Save the file, and then close Notepad.
  • Open the registry and locate the key HKEY_LOCAL_MACHINESoftwareMicrosoftMicrosoft Operations Manager3.0Reporting.
  • Change the DefaultSDKServiceMachine value to be the name of the new root management server.

If we start the console, connect it to the new RMS, we could see that the RMS role has been well moved.

Removing the Windows 2003 Server

As we now have our brand new RMS running on Windows Server 2008 R2, the last thing that we have to do is to uninstall Operations Manager 2007 R2 from the Windows Server 2003 server.

Go to the Windows Server 2003, Control Panel, Add/Remove Programs and remove Operations Manager 2007.

The last step is to remove the server from the Operations Manager Console, right click on it and chose delete.

Click on YES.

Our Operations Manager Group is finally compliant for the upgrade to Operations Manager 2012. I will cover this process step by step into a next post.

Don’t hesitate to contact me if you have any question.

Christopher Keyaert

clip_image001 clip_image002 clip_image004 clip_image005 clip_image007 clip_image008

About Christopher Keyaert

Christopher Keyaert is a Consultant, focused on helping partners to leverage the System Center and Microsoft Azure cloud platform. He is also a Microsoft Most Valuable Professional (MVP) for Cloud and Data Center Management and a Microsoft Certified Trainer (MCT).
This entry was posted in Uncategorized. Bookmark the permalink.

0 Responses to Prepare your environment to Operations Manager 2012 – Part III Moving the RMS role

  1. David Biot says:


    In some environments you can encounter issues moving the RMS role. When doing the promoterms, the new MS tries to access files in the health service state folder of the old RMS. The problem is, the health service stateManagemnet packs folder has a lot of files with long GUIDS, making the UNC path from the new MS to these files from the old RMS bigger than 255 characters. With a big crash as a result.

    To ensure you have no issues promoting the RMS: stop the health service on the old RMS, rename the management packs folder and perform your promoteRMS with no issues :).

  2. says:

    Great tips David, thank you !

Leave a Reply

Your email address will not be published. Required fields are marked *