Load the Business Class Email (BCE) signed XML configuration file.
Confirm that the plug-in works as expected for encryption. (This would be assuring custom configurations to the BCE XML for decrypt/flag/encrypt, and then also additional custom configuration for CommonComponentsConfiguration XML.)
Construct a Custom Configuration Config Directory
On a Windows host or Network Server, create a custom installation directory. (For this example, using a network share: \\172.18.250.59\share\my_plugin_install)
On the Windows host, navigate to the standard installation directory:
Note: Assure that the accountFileName syntax is properly formatted. If the accountFileName configuration line is incorrect, Outlook will set the plug-in to default values and will also mark the plug-in as Inactive for Outlook Add-ins:
Deploy the Custom Configuration Files
Un-install the standard installation of the plug-in that was performed from the beginning of this article. This can be done via normal un-install from Windows: Control Panel > Programs and Features > Cisco Email Security Plug-In, and selecting Uninstall/Change. Complete the steps as prompted.
At this point the custom configuration files are ready to install. From the Windows CLI, run the following syntax to install:
The installation usually takes ~30 seconds to complete. Once the install has finished, after opening Outlook, final product installation in the Outlook ribbon bar would be similar to:
From New E-mail, the Encryption option should be highlighted and ready for use:
The encryption option will be set based on the original BCE XML configuration:
<!-- Plugin related configuration. Valid type edition values are: decrypt - Plugin can only decrypt PXE envelopes. flag - Plugin can decrypt and flag a message for encryption. encrypt - Plugin can decrypt and encrypt a message on the device. --> <plugin edition="flag">
UseCustomConfig must be in proper case and is not plural. UseCustomConfigs will not work and cause Outlook to not read the configuration properly.
Do not end the custom configuration installation command referring to the custom configuration file directory with a "\".
The custom configuration directory and files must have permissions set as such to allow the end user running Outlook to be allowed to read/write the files. If not, this may also cause Outlook to not read the configuration properly, and the end user will be presented errors during Outlook startup.
Review the CiscoEmailSecurity.log file in the end user's directory for more detail on errors generated and associate to the plug-in operation: