Checklist: Preparing to migrate or upgrade RMS

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012 R2

Before starting a migration or upgrade, complete all the tasks in this checklist in the order in which they are presented to prepare your infrastructure for AD RMS. To ensure that your hardware meets the minimum requirements for AD RMS, see Pre-installation Information for Active Directory Rights Management Services (https://go.microsoft.com/fwlink/?LinkId=84733)

Checklist: Preparing to Migrate or Upgrade Windows Rights Management Services

  Task Reference

If you are upgrading your RMS cluster to AD RMS running on Windows Server 2008, ensure that all Windows Server 2003 servers in the RMS cluster are running RMS with Service Pack 1 (SP1) or RMS with Service Pack 2 (SP2). If you are upgrading your RMS cluster to AD RMS on Windows Server 2008 R2, ensure that all servers in the RMS cluster are running RMS with SP2.

Check installed RMS service pack version

Ensure that the RMS cluster to be migrated or upgraded has been provisioned.

Ensure provisioning level

Ensure that the RMS cluster has been enrolled with the Microsoft Enrollment Service.

Check enrollment status

To prevent loss of RMS data if you should need to roll back the migration or upgrade, be sure to back up the RMS configuration database.

Back up RMS configuration database

Before migrating or upgrading an RMS cluster, export the server licensor certificate (SLC). The SLC can be stored in either the RMS configuration database or a hardware security module.

Export server licensor certificate

If you are using a software-based CSP to protect your RMS private key, you must export the key container and install it on the new computer.

Export and install a software-based CSP key

For a list of known issues when migrating from RMS to AD RMS

Known issues with RMS to AD RMS migration

For a list of known issues when upgrading from RMS to AD RMS

Known issues with RMS to AD RMS upgrade