Consider the following scenario:
- You create a template on a Rights Management Services (RMS) server to manage permissions for Microsoft Office 2010 documents.
- You configure the template to grant the Export permission.
- You apply the template to an existing Office 2010 document.
- A user who is granted the Export permission opens the document in Office 2010.
In this scenario, the user can use the Unrestricted Access
menu to remove restrictions from the Information Rights Management (IRM)-protected document.
The current behavior of the Export permission feature in Office 2010 is by design. However, it differs from the behavior of the Export permission feature in earlier versions of Office. You can install this hotfix to make the Office 2010 Export permission feature behave in the same manner as it did in earlier versions of Office.
To resolve this issue, apply the following hotfix package:
Description of the Office 2010 hotfix package (mso-x-none.msp): December 14, 2010
Registry key informationImportant
This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
How to back up and restore the registry in Windows
After you install the hotfix package, follow these steps to enable the hotfix:
- Click Start, click Run, type regedit in the Open box, and then click OK.
- Locate and then select the following registry subkey:
- On the Edit menu, point to New, and then click DWORD Value.
- Type IgnoreExportRight, and then press ENTER.
- In the details pane, right-click IgnoreExportRight, and then click Modify.
- In the Value data box, type 1, and then click OK.
- Exit Registry Editor.
Microsoft has confirmed that this issue affects the Microsoft products that are listed in the "Applies to" section.