Share via


Files Installed with the SDK

The AD RMS client requires the following files. On a 32-bit operating system, the 32-bit binary files are located in the %SystemRoot%\System32 folder. On a 64-bit operating system, the 32 bit binary files are located in the %SystemRoot%\SysWow64 and the 64-bit files are located in %SystemRoot%\System32 folder.

File name Location (depends on operating system) Description
Msdrm.dll

%SystemRoot%\System32

%SystemRoot%\SysWow64

Contains the AD RMS functions. This DLL is installed by the AD RMS client, not the SDK.
Secproc.dll

%SystemRoot%\System32

%SystemRoot%\SysWow64

The AD RMS client lockbox for the Production hierarchy.
Secproc_ssp.dll

%SystemRoot%\System32

%SystemRoot%\SysWow64

The AD RMS server lockbox for the Production hierarchy.
Secproc_isv.dll

%SystemRoot%\System32

%SystemRoot%\SysWow64

The AD RMS client lockbox for the Pre-production hierarchy.
Secproc_ssp_isv.dll

%SystemRoot%\System32

%SystemRoot%\SysWow64

The AD RMS server lockbox for the Pre-production hierarchy.
Rmactivate.exe

%SystemRoot%\System32

%SystemRoot%\SysWow64

An application used to perform AD RMS client machine activation in the Production hierarchy.
Rmactivate_ssp.exe

%SystemRoot%\System32

%SystemRoot%\SysWow64

An application used to perform machine activation when using a server lockbox in the Production hierarchy.
Rmactivate_isv.exe

%SystemRoot%\System32

%SystemRoot%\SysWow64

An application used to perform AD RMS client machine activation in the Pre-production hierarchy.
Rmactivate_ssp_isv.exe

%SystemRoot%\System32

%SystemRoot%\SysWow64

An application used to perform machine activation when using a server lockbox in the Pre-production hierarchy.
ISVTier5AppSigningPrivKey.dat ADRMSSDKInstallationPath\Bin Contains the private key used to generate a manifest for use during development of an AD RMS-enabled application. This is only included in SDK versions later than RMS 1.0 SP1.
ISVTier5AppSIgningPubKey.dat ADRMSSDKInstallationPath\Bin Contains the public key used to generate a manifest for use during development of an AD RMS-enabled application. This is only included in SDK versions later than RMS 1.0 SP1.
ISVTier5AppSignSDK_Client.xml ADRMSSDKInstallationPath\Bin Contains the certificate used to generate a manifest for during the development phase of an AD RMS-enabled application. This is only included in SDK versions later than RMS 1.0 SP1.
ISVTier5AppSignSDK.cc ADRMSSDKInstallationPath\Bin Can be used to understand the structure of the Pre-production certificate.
ISVTier5AppSignSDK.xml ADRMSSDKInstallationPath\Bin Can be used to understand the structure of the Pre-production certificate.

The following files, which were included with the AD RMS client 1.0, are no longer part of the AD RMS client.

File name Description
ActMachine.exe Activates the computer and user. ActMachine.exe is not required if the AD RMS application attempts to activate the machine itself.
Msdrmhid.dll Contains the hardware ID–computing information.
MSDRMCtrl.dll Contains the ActiveX control for nonsilent, end-user license acquisition, which is supported by RMS client 1.0 only.

Send comments about this topic to Microsoft

Build date: 3/13/2008