Export (0) Print
Expand All

Release notes

This topic contains important information about this release of the AD RMS SDK 2.0 and updates for AD RMS SDK 2.1 beta.

What's new in AD RMS SDK 2.1 beta

This documentation set supports both AD RMS SDK 2.0 and AD RMS SDK 2.1 beta. AD RMS SDK 2.0 is available via the MSDN Download Center. AD RMS SDK 2.1 beta is available via the Rights Management site on Connect. Features that are avialable in the 2.1 beta version are specifically marked in this document.

New features added in AD RMS SDK 2.1 beta

  • Two new constants have been added to the License property types.
  • Support for Windows Azure AD Rights Management (AADRM) allowing for cloud based rights management.

Important developer notes for Active Directory Rights Management Services SDK 2.0 RTM

  • Issue: When creating a license from scratch, ownership rights must be granted explicitly.

    Solution: Your application must explicitly add Owner rights to the license owner when creating a license from scratch using IpcCreateLicenseFromScratch. For more information, see Add explicit owner rights.

  • Issue: If an application calls IpcProtectWindow or IpcUnprotectWindow twice for the same window by using its handle, Active Directory Rights Management Services SDK 2.0 will return a failure in the HRESULT.

    Solution: For specific guidance on this, see the Remarks section in IpcProtectWindow and IpcUnprotectWindow.

  • Issue: When building for multiple architectures, you must use this guidance.

    Solution: If you want to use the Ipcsecproc*isv.dll for a different architecture (for example, you have installed the 64-bit SDK on a 64-bit computer but now want to deploy on a 32-bit computer that requires Ipcsecproc*isv.dll), you must install the 32-bit SDK on a different computer and copy the Ipcsecproc*isv.dll files to there from the %PROGRAMFILES%\Microsoft Information Protection And Control folder (the default location or wherever you chose to install the SDK).

Frequently asked questions

Q: How does the default language behavior work with functions that take an LCID parameter?

A: Use 0 for the default locale. In this case, Active Directory Rights Management Services Client 2.0 looks up names and descriptions in the following sequence and retrieves the first available one:

1 - User preferred LCID.
2 - System locale LCID.
3 - The first available language specified in the Rights Management Server (RMS) template.
If no name and description can be retrieved, an error is returned. There can be only one name and description for a specific LCID.

 

 

Send comments about this topic to Microsoft

Build date: 10/23/2012

Community Additions

Show:
© 2014 Microsoft