Translate this site using Windows Live Translator:
Moving your RMS V2 (WS 2008) Database to another server - RMS: Protecting Your Assets. - Site Home - TechNet Blogs

RMS: Protecting Your Assets.

The Protecting 'My' Asset Disclaimer: This is my 'un-official', 'in my spare time', 'use at your own risk', all things RMS (Rights Management Services), IRM (Information Rights Management), IPP (Information Protection Pla

Moving your RMS V2 (WS 2008) Database to another server

Moving your RMS V2 (WS 2008) Database to another server

  • Comments 4
  • Likes

Lot's of people have used my previous posting detailing the steps necessary to move your database server to another server, post-mortem. First allow me to say ' Picklemonkey and Duckbutt '. all the people that were searching for that post using those terms will also find this post. :)

Here is the original post:

Here are the steps for RMS on WS2008.

Pre-'doing this' stuff:

1. Stop the AD RMS logging service and IIS on all your RMS servers, and ensure there are no connections to the DRMS_ databases. 
2. Hold a picture of Al Gore close to you, and repeat "I am one with the universe", 10 times.

To move to a new SQL server:

1) It is recommended that you back up the 3 DRMS SQL databases, but at a minimum, export your Enterprise Trusted Publishing Domain.  This can be used as a minimal disaster recovery backup.  If needed, you can import this file into any RMS installation to recover documents if necessary. 

2) Run RMSConfigEditor.exe from the RMS toolkit.

3) Type the name of the SQL server in the Server text box and click "Go". (Note: If you are using an instance or port it needs to be included i.e. SQLSVR01\RMSDB,11553)

4) Pick the DRMS_Config database from the Database drop down list and click "Go".

5) Open the DRMS_ClusterPolicies and find the following PolicyName entries.  In the corresponding PolicyData entry, you will find the name of the SQL server being referred to.  Adjust the PolicyData entry to the new SQL server name and click the "Persist" button on each.


6) Go to Start>Run Regedit and modify the following keys to reflect the new cname (needs to be done on every server in the cluster):

There will be a key in here that starts PasswordDerivedKey_<SQL Server>...
You will need to change this to reflect the new SQL dbase name.
Note: If you are using a database instance and/or port the name needs to reflect this. So if your SQL string is SQLServer01\RMSDB,11553, then your key needs to show PasswordDerivedKey_SQLServer01\RMSDB,11553...

Value name: ConnectionString
Value name: LoggingDatabaseServer

Value name: ConfigDatabaseConnectionString

That should be it. Restart all of your services, and make sure everything is working.

You just survived a worse experience than Hillary Clinton's Bosnia gunfire experience, and can now run for president. Give yourself a pat on the back, and go hug your local Dunkin' Donuts coffee guy.


  • correction for the Pre-'doing this' stuff:

    Step 1 The "RMS logging service" is called "AD RMS logging service"

    correction to move to a new SQL server:

    Step 3) If a SQL instance is used you must type the server name including the instance name like myDBserver\InstanceName

  • Can I apply this article: "How to change the TCP port that SharePoint Portal Server or SharePoint Server uses to connect to SQL Server" to RMS?

  • Hi Jason,

    Thanks for the other day durimg Wrms to AD RMS migration, it was a life saver.

    We are about to migrate the SQL database from SQL 2005 to SQL 2008, will try the steps above and provide feedback based on my experience.


  • Check also this resource on

    Handles same topic as a lab guide.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment