Upgrading from SP1 Beta to RTM

This post is to aid RMS SP1 beta customers who would like to migrate their RMS Enterprise Server deployments from the RMS SP1 Beta to the RMS SP1 RTW product.  Technically the 'upgrade' itself is not supported and not a true upgrade.  However in order to perform this task and have the ability to preserve and open RMS protected content that was previously established within the RMS SP1 Beta timeframe, the product team has built a small utility and some very specific steps that allows this to occur.

You will still need to contact us at  <

mailto:rmsbeta@microsoft.com> in order to obtain the utility that cleans up the RMS SP1 beta server.


The beta release of Microsoft® Windows® Rights Management Services (RMS) Service Pack 1 (SP1) used the Windows Components Wizard to install RMS SP1 as an optional component of Windows Server 2003. However, the final release of RMS SP1 uses the Microsoft® Windows® Installer to install RMS SP1 instead of the Windows Components Wizard.

These two different setup procedures use different logic and a component that is installed by the Windows Component Wizard cannot be modified by another setup procedure, which means that the RMS SP1 (Final) Windows Installer cannot effectively remove the RMS SP1 Beta. Therefore, if you attempt to upgrade a server running RMS SP1 Beta to the final release of RMS SP1, the server will run both RMS SP1 Beta and RMS SP1 final versions and both will be available for use by RMS clients.

To remove the beta version of RMS SP1 cleanly, the RmsSp1Cleanup.bat utility is being provided to the customers that participated in the RMS SP1 beta. You must complete the procedure described in this document to remove the RMS SP1 beta release before you install the final version of RMS SP1.

Before you perform the procedure, ensure that you are able to restore the current configuration if necessary by backing up your RMS SP1 Beta configuration database. It is recommended that you preserve the following information along with your database backup should it be necessary to restore the RMS SP1 Beta in case of failure:

· The name of the backup copy of the database.

· The name of the computer on which the backup database is located.

· The account name and password that was originally used to provision RMS SP1.

· The password that was originally specified for software private key protection (if it was used).


Before you begin

Before using the RmsSp1Cleanup.bat utility, make sure that the following conditions are met:

· To run this utility, the logged on user must be a member of the Administrators group on the local computer or have the equivalent permissions (this is required to delete information from the registry and certain assembly files).

· Run this utility only on the RMS SP1 Beta version. If Rights Management Services does not appear in the Windows Components Wizard, do not run this utility.

· Make sure that no Windows Rights Management Server node resides under Add/Remove Programs - if so please select to also remove this application.

· The Windows Component Wizard should be closed before running this utility.

· Download the Windows Resource Kit Tools from the Microsoft Web site <

http://go.microsoft.com/fwlink/?LinkID=20334> (http://go.microsoft.com/fwlink/?LinkId=20334). Place the iniman.exe tool in the same folder where the SP1 Clean up utility (RmsSp1Cleanup.bat) will reside.


How to

The following procedure describes the steps that must be completed to successfully remove the RMS SP1 beta:

To Remove the RMS SP1 beta

1. Open the RMS Administration Web site and click the Trust Policies link.

2. In the Trusted user domains area, click the Export button to export the server licensor certificate to a file.

3. In the Trusted publishing domains area, click the Export link next to the key container for this server to create a trusted publishing domain file.


You will specify a location to which to save the file and password with which to protect this file. Note this information so that you can import this file to your new RMS installation.

4. From the Global Administration page of the RMS Administration Web site, select Remove RMS from this server to unprovision RMS.


If you have multiple front-end Web servers for the RMS cluster, you must unprovision RMS on all of these servers before proceeding.

5. Close the RMS Administration Web site.

6. From Add or Remove Programs in Control Panel, click Add/Remove Windows Components to open the Windows Components Wizard.

7. Clear the check box next to the entry for Rights Management Services and then click OK.

8. Close the Windows Components Wizard.

9. Copy INIMAN.EXE from the Windows Server 2003 Resource Kit Tools into a desired location or folder.

10. Copy the RmsSp1Cleanup.bat utility into the same folder as INIMAN.EXE

11. Run the RmsSp1Cleanup.bat utility

12. After it finishes, the utility displays a command script that flashes on the screen. The command prompt window closes after the script finishes.

13. Connect to your database server and delete the configuration (DRMS_Config), directory services (DRMS_DirectoryServices), and logging (DRMS_Logging) databases. The database schema used in the RMS SP1 Beta is not compatible with the final version of RMS SP1.

14. Install the final version of RMS SP1.

15. Provision RMS SP1 on the server.

16. Open the RMS Administration Web site and click the Trust Policies link.

17. In the Trusted user domains area, click the Browse button and locate the server licensor certificate file that you exported in step 2 and then click the Add button to establish the trusted user domain.

18. In the Trusted publishing domains area, click the Browse button and locate the trusted publishing domain file that you exported in step 3 and then in the space provided type password need to decrypt the file and then click the Import button to establish the trusted publishing domain.


Steps 19 through 22 only apply if you have multiple front-end Web servers for the RMS cluster.

19. To upgrade all remaining front-end Web Servers in the RMS cluster, repeat the following steps on each of the remaining front-end Web Servers.

20. Repeat Steps 6 through 12 to Remove RMS Sp1 beta from the front-end.

21. Install the final version of RMS SP1.

22. Join the front-end to RMS cluster created in step 15.


More Information

If the RMS SP1 beta was installed as an update to RMS version 1.0, there will be duplicated assemblies present in the global assembly cache (GAC) that were not removed during the RMS SP1 Beta update. This utility will attempt to remove those assemblies that remained; however, it may be useful to verify that this was successful.

If the utility did not successfully remove the assemblies, you must remove them manually. To safely remove the assemblies, type the following command at the command prompt:

gacutil /u myDll ,Version=,Culture=en,PublicKeyToken=874e23ab874e23a

In this command, myDll is the name of the assembly you want to remove from the GAC.

You can query on the specific DLLs by referencing the \Windows\Assembly folder.

You can also find out more information about gacutil.exe by typing gacutil.exe /? at the command prompt.

Any customized tools being used in conjunction with the RMS databases will need to be reconfigured.

Upgrading an RMS SP1 Beta database is not supported.


Chris Borkenhagen,

Software Test Engineer Lead