Installation Problems
It is quite typical (unfortunately) that many production environments are treated as a test bed for many installations. In this instance you may be faced with a scenario where you will need to deploy RMS into an environment that hasn’t perhaps been controlled with a proper change management policy or a test environment where staff can “play”.
When starting the provisioning stage of the RMS deployment you may be faced with some of the following scenarios, I will try to cover most of the common resolution strategies:
- You receive a warning about a root CA not existing
- RMS assumes that you have already deployed the first Root CA
- Errors with Service Connection Points
Ensure that you have installed the Widows Support Tools for your version of Windows Server. The support tools can be found on the Microsoft Windows Server CD. Once installed, you should be able to click on Start > Run > Adsiedit.msc

and click OK. Adsiedit.msc opens.

If you’re running Adsiedit.msc from your local machine you will need to connect to the Configuration connection point. To do this follow the following steps:
- In ADSI Edit select Action > Connect to …
- The Connection Settings dialog opens
- In the Select a well known Naming Context dropdown, select Configuration and click OK.
- Expand to CN=Configuration,DC=contoso,DC=com
- Expand to CN=Services
- A normal configuration should look as follows, but in your case you’re probably missing the CN=RightsManagementServices container. We will need to recreate this container.

- Ensure that the account you’re logged in on has Domain Admin rights.
- Right click Servcies and select New > Object …
- In the Create Object dialog, select container and click Next

- In the Value field enter RightsManagementServices
- Click Next, click Finish.
- We now need to create a child container under the RightsManagementServices container. Right click on CN=RightsManagementServices and select New > Object …
- In the Create Object dialog, select container and click Next
- In the Value field enter SCP
- Click Next, click Finish.
Your ADSI Edit window should look something like this, showing the newly created containers.

At this point go back to your RMS administration website and refresh the provisioning page. You should notice that the warning has disappeared.