Because the guides for the sharing application went through a major revamp this month, changes for these are also listed in this post. And in case you missed them, be sure to check out our fun quiz questions:
We value customer feedback and try to incorporate it when possible. Although we can't promise to make the docs perfect for everybody, we are committed to continual improvement. If you have any feedback about the docs for Windows Azure RMS, email
What's New for the RMS Sharing Application Documentation, January 2014
Rights Management sharing application administration guide
used to be included as a separate section of the user guide, but this month was republished as a separate topic. We did that to make the instructions for an enterprise installation easier for you to find, as well as removing this and the more technical information from end users. In addition, the admin guide has the following changes:
The “Supported file types” section is renamed “
Supported file types and file name extensions
” to help clarify that in some cases, a protected file will have a new file name extension. This is important, because it might require reconfiguration of firewalls or security software if they are configured to take specific action on files, according to their file name extension. For example, firewalls might block all email attachments unless the file name extension is listed as an exception.
The table that lists the file name extensions is updated so that it now lists the original file name extension first, and then the new, RMS-protected file name extension. We thought admins wouldn’t need the description for these well-known file types, and removed this column.
For the file types supported by Office, we removed the references and distinctions for the two protector types. Although technically accurate, it’s not relevant to an admin who needs to deploy the sharing application.
- Updated to correct Exchange 2013 registry entries in the
Configuring an Exchange server to use the connector
section. Where it used to reference v14 in the registry key (for example, HKEY_LOCAL_MACHINESOFTWAREMicrosoftExchangeServerv14IRMCertificationServerRedirection), these are now corrected for v15 (for example, HKEY_LOCAL_MACHINESOFTWAREMicrosoftExchangeServerv15IRMCertificationServerRedirection).
However, if you use the new server configuration tool for the Microsoft RMS connector (released in December), the tool automatically configures these entries for you. This topic was updated in December with information about the tool. For more information, see the
Configuring servers to use the RMS connector