Using the AD RMS SDK
[The AD RMS SDK leveraging functionality exposed by the client in Msdrm.dll is available for use in Windows Server 2008, Windows Vista, Windows Server 2008 R2, Windows 7, Windows Server 2012, and Windows 8. It may be altered or unavailable in subsequent versions. Instead, use Active Directory Rights Management Services SDK 2.1, which leverages functionality exposed by the client in Msipc.dll.]
The following topics discuss how to setup your environment and program typical scenarios using the Active Directory Rights Management Services (AD RMS) SDK.
Topic | Description |
---|---|
Setting Up the Pre-production Development Environment | Discusses the steps necessary to enroll in the Pre-production certificate hierarchy and begin writing an AD RMS application. |
Switching to the Production Environment | Discusses how to move from the Pre-production to the Production certificate hierarchy when you have finished developing and testing your application and intend to release it to customers. |
Working with Licenses and Templates | Contains miscellaneous topics about end-user licenses and rights policy templates. |
Creating a Callback Function | Discusses how to create a callback function used by various AD RMS asynchronous functions to deliver status information to your application. |
Activating a Computer | Discusses how to sign a computer into a Pre-production or Production certificate hierarchy. For a C++ sample, see Machine Certificate Code Example. |
Activating a User | Discusses how to sign an Active Directory domain user account into a Pre-production or Production certificate hierarchy. For a C++ sample, see Rights Account Certificate Code Example. |
Creating an Application Manifest | Discusses how to create an application manifest to sign your application into a Pre-production or Production certificate hierarchy. |
Creating and Using Issuance Licenses | Discusses how to create an issuance license that identifies who can use an item of content and the rights governing that use. For C++ code samples, see Online Signing Code Example and Offline Signing Code Example. |
Encrypting Content | Discusses how to use the AD RMS SDK to encrypt content. For a C++ sample, see Encrypting Content Code Example. |
Decrypting Content | Discusses how to use the AD RMS SDK to decrypt content. For a C++ sample, see Decrypting Content Code Example. |
Revoking a Certificate | Discusses how to revoke licenses and certificates. For a C++ sample, see Revocation Code Example |
Publishing Content | Discusses how to use the compound file binary format (CFBF) to publish encrypted content, issuance licenses, and end-user licenses. |
Debugging an Application | Discusses how to debug an application that creates a secure environment. |
Note
If you call the AD RMS SDK client functions from managed code (using Platform Invocation Services – P/Invoke) it is important to remember that when you run a managed 32-bit client application on a 64-bit operating system, you must build the application by specifying "x64" for the /platform compiler option. If you specify "x86" or "anycpu", an E_DRM_MANIFEST_POLICY_VIOLATION error code is returned. For more information about the /platform command line option, see the /platform (Specify Output Platform) (C# Compiler Options) topic on MSDN. For more information about identifying the output platform when using Visual Studio, see Build Page, Project Designer (C#).
Related topics