MSDRM 1.0 Registry Settings

Applies To: Windows Server 2008, Windows Server 2008 R2

The MSDRM registry entries are used to set or modify certification and licensing pipeline paths and other AD RMS wide configurations on the client. You may want to override the locations of the AD RMS servers used for publishing depending on the topology used in your enterprise. The locations of the servers used for publishing are normally discovered by the client by using Active Directory. By adding the appropriate registry keys on the client computers, the clients will bypass those methods and instead use the URLs that you specify in the registry entry value.

A registry key is created during bootstrapping and used to provide the SCP connection point. Users on the Internet and Intranet users whose SCP point is not registered in AD must set these registry keys on their machines to use AD RMS.

There are three keys that can be used to modify the AD RMS pipelines.

Activation: This registry key defines the URL of the user activation service

REG_SZ: default
Value: <http(or https)://RMS_Cluster_Name/_wmcs/Certification> 

EnterprisePublishing: This registry key defines the URL of an RMS installation that you want this client to use for license requests.

REG_SZ: default 
Value: < http(or https)://RMS_Cluster_Name /_wmcs/Licensing> 

CloudPublishing: This registry key defines the URL of the Microsoft-hosted licensing service that can be used if the client does not have access to an RMS installation but does have access to the Internet. Typically this setting can be used for passport user.

REG_SZ: default 
Value: <http(or https):// FQDN_Cluster_Name/_wmcs/Licensing>  where FQDN_cluster_name is the fully-qualified domain name of the Windows Live ID service URL cluster.

This URL is automatically configured when the client is initialized to use the Windows Live ID service for AD RMS certification and it normally does not need to be configured in the enterprise.

Another pair of registry values under the MSDRM key that are commonly used in the enterprise can be used to configure tracing:

Trace: This registry key can be used to enable application tracing, which records logs of every action executed by the RMS client and that can be viewed by the DebugView tool.

Value: 1 to enable tracing, 0 to disable tracing (default)

UpdateFrequency: This registry value specifies how often the Rights Policy Templates will be downloaded by the automated scheduled task for template downloads.

REG_DWORD: UpdateFrequency
Value: Number of day between downloads