This document guides you through installing and configuring Adobe Experience Manager Document Security Extension 11.0 for Microsoft Office.

This document includes information about the following tasks:

• Installing Document Security Extension for Microsoft Office
• Preconfiguring the installer to point to the LiveCycle Rights Management ES2 and later and Document Security add-on for Adobe Experience Manager Forms.
• Configuring the automatic application of default policy

Before you install Document Security Extension for Microsoft Office, read the Release Notes.

Uninstall third-party plugins 

AEM Document Security Extension for Microsoft Office does not support third party plug-ins for Microsoft Office applications. As this extension may conflict with third party plug-ins, you must uninstall any non-Adobe plugins for Microsoft Office before installing Document Security for Microsoft Office. Adobe does not provide support for Document Security for Microsoft Office applications with third party plug-ins installed.

System requirements

Refer to the Release Notes, for the system requirements.

Installing Document Security Extension for Microsoft Office

You can download the standard installer, AEMDocumentSecurityExtensionforMicrosoftOffice.exe, from Adobe download website. You cannot customize this EXE file directly, but it can be installed interactively or in silent mode. You must be logged on as an administrator to install the software.

Install in silent mode

Use a file extractor utility, such as WinZip, to extract AEMDocumentSecurityExtensionforMicrosoftOffice.exe from the installer file. Open the command prompt, go to the folder that contains the setup file, and type the following text:

AEMDocumentSecurityExtensionforMicrosoftOffice.exe /s /v"/qn"

The installer is also available as an MSI file, which can be used for customization.

Install an MSI file in silent mode

Starting Office applications on a machine with Document Security Extension and McAfee VirusScan 

To ensure that Office applications start smoothly on a machine that has Document Security Extension installed and McAfee VirusScan with On-Access Scan enabled, disable the Buffer Overflow Protection option in the McAfee VirusScan Console.

Preconfiguring the installer to connect to Document Security

You can preconfigure the Document Security Extension for Microsoft Office installer to point to a LiveCycle or AEM server so that users who install Document Security Extension for Microsoft Office can use the features without configuring a connection. As such, users can open protected documents with no configuration necessary. However, they cannot protect new documents until they configure the client to use a particular server.

The following steps describe how to create and configure an MSI file. This MSI file contains the registry values that are required to preconfigure the Document Security Extension for Microsoft Office installer to the LiveCycle or AEM server that is installed in your enterprise.

Prerequisites for customizing the installer

Use the Orca database editor to customize the installer. The following steps describe how to create a custom MSI file by modifying a copy of the MSI installation file using the Orca database editor. Orca is available as part of Windows SDK for Windows Server 2008 and .NET Framework 3.5. For more information about how to edit Microsoft Windows® Installer files using Orca, see Microsoft Support.

Install Orca

Create and configure the MSI file

Configuring automatic application of a default policy

As part of the configuration, you can configure automatic application of a default policy so that Document Security Extension for Microsoft Office protects every document that is saved.

You can specify one of the following options:

• Protect all documents with a default policy.
• Allow users to optionally save a file in an unprotected format when they cannot connect to the server. This flexibility allows you to account for cases when users are creating documents while disconnected from the network (for example, while on an airplane).

After you enable the auto-apply policy feature, the document is protected with the default policy in the following cases:

• User edits and saves a newly created document
• User edits and saves an unprotected document
• User opens an application that opens with a default document, edits, and then saves the document

Configure the auto-apply policy feature in the MSI file 

Before you begin, preconfigure the installer to point to your LiveCycle ES4 server, as described earlier in this article.