Product Feature Sheets

white papers

White Papers

use cases

Use Cases

case studies

Case Studies

What's New Latest Release - W7.10

Office Outlook Add-in Enterprise Edition

This section describes the system requirements and the installation files & guide for the Secure Messaging Office Outlook Add-in for standard, GPO and terminal services versions. The Add-in is a .NET Framework 4.0-based COM add-in for Microsoft Office. It fully integrates within Microsoft Outlook to allow seamless secure communication and added productivity features.

Standard Edition

The deployment and upgrade management for the Secure Messaging Microsoft Office Outlook add-in standard edition is based on Microsoft’s ClickOnce technology. The benefits of using ClickOnce include the ability for individual users to self-provision their installation as it does not require (in most cases) administrative rights on the computer. In contrast, the enterprise edition can be deployed to multiple desktops relying on Group Policy for centralized deployment (GPO) or Terminal Services.

For ease of use and a more viral deployment, use the standard edition available in the WebApp. Users can click on the ‘Apps’ menu and select to download and install the add-in. If users don’t see this link, they should contact their administrator to grant permissions to install the add-in. A step-by-step guide is provided to each user within the secure WebApp.

System requirements

The Secure Messaging Office Outlook Add-in supports the following software configurations:

  • Microsoft Windows 8/10, Windows Server 2012, 2012 R2, 2016 & 2019 (for server deployments).
  • Microsoft Office 2013, 2016, 2019, 32 & 64 bit, all editions, with the latest security / service packs installed.
  • The Add-in requires the following pre-requisites:
    1. Microsoft .Net Framework 4.5.2 or above (automatically installed with the standard edition).
    2. Microsoft Windows Installer 3.1+ (required only for the standard version, typically present on all Windows versions).
TROUBLESHOOTING: For the Enterprise Edition, the .NET framework installation must be completed separately directly from the Microsoft website: The latest version of the .NEtT framework is usually already installed with most latest version of Windows.

NOTE: The IMAP protocol is currently not supported by the Secure Messaging add-in for Outlook. This is because the IMAP protocol syncs message and attachment data between Outlook and your mail server unencrypted in plain text, thus allowing decrypted secure messages to be sent in the clear over the internet and saved unencrypted on the mail server. This constitutes a security breach. We recommend that you do not use IMAP with Secure Messaging added to Outlook. Please contact your administrator for more information or alternatives.

NOTE: The Secure Messaging add-in for Outlook is not supported in versions of Outlook that are installed from ‘Office in the Microsoft Store’.  Most importantly, these versions offer poor COM add-in support and in some cases, the COM add-ins are not supported at all.

Automatic Group Policy (GPO)

For organizations where group policy deployment is available and the majority of the computers belong to the domain, the recommended procedure is to first deploy the pre-requisites followed by the add-in.

NOTE: Windows Server 2008 and above with Group Policy enabled are supported.

The following steps are required to install the add-in using Group Policy:

  1. IMPORTANT: Uninstall the Standard Edition version of the Secure Messaging Office Add-in for any of the users you are deploying to. If this is not complete, the users will experience issues loading the Add-in.
  2. Create a distribution point.
  3. Create the group policy object.
  4. Assign the installation package to the selected users/groups in the domain.

Step 1: Creating the add-in distribution point:

  1. Log in to the server with a user name which has administrative rights.
  2. Create a folder to hold the add-in installation files in. This folder must be on your shared network.
  3. Set permissions on your shared network to allow your Users READ access to this folder.
  4. Download the add-in MSI file to the selected folder.
  5. Take note of the final location of the software, e.g., \\SERVER\shared_folder\______________.MSI

Step 2: Creating the group policy object in Windows Server 2008, 2008 R2, 2012 & 2012 R2:

  1. Log in to the server with a user name which has administrative rights.
  2. Start the Group Policy Management snap-in (Start -> Administrative Tools -> Group Policy Management).
  3. Right-click on your domain in the console tree, and then choose Create a GPO in this domain, and link it here.
  4. Type the name you want to call this policy (e.g. ‘Secure Messaging Add-in’), and click OK.
  5. Expand the Group Policy Objects item and select the newly added policy.
  6. If you know what users/groups this policy will apply: Click the Remove button to delete the Authenticated Users security group. Click the Add button to add security groups or users.

Step 3: Assigning the installation package:

  1. Log in to the server with a user name which has administrative rights.
  2. Start the Group Policy Management snap-in.
  3. Locate and expand your domain in the console tree, then expand Group Policy Objects, right-click on the group policy object that you want, and then click Edit. The Group Policy Object Editor will start.
  4. Under User Configuration, expand Policies, then Software Settings.
  5. Right-click Software installation, point to New, and then click Package.
  6. In the Open dialog box, type the full Universal Naming Convention (UNC) path to the shared folder with the MSI package that you want (e.g. \\server\share\setup.msi).NOTE: If the Windows Installer file resides on the local hard disk, do not use a local path. You need to use the UNC path to indicate the location of the installation files.
  7. Click Open.
  8. Click Assigned, and then click OK. The package will be listed in the right pane of the Group Policy window.
  9. Right-click the package, click Properties, switch to the Deployment tab.
  10. Select the “Install this application at logon” checkbox.
  11. Select the “Uninstall this application when it falls out of scope of management” checkbox./li>
  12. Select “Basic” under Installation user interface options, then click OK
  13. Set the ‘Always Install with elevated privileges’ option to DISABLED in the Local Group Policy editor (see ‘User Configuration’->’Administrative Templates’->’Windows Components’->’Windows Installer’ and ‘Computer Configuration’->’Administrative Templates’->’Windows Components’->’Windows Installer’)
  14. Close the Group Policy Editor, then quit the Active Directory Users and Computers or Group Policy Management snap-in. When the user logs on, the managed software package is automatically installed.

Upgrading the package:

  1. Remove the existing Group Policy Object, so that it will be uninstalled the next time the user logs in.
  2. Complete steps 2 and 3 above for the new installation package.

Terminal Services / Citrix deployment

For organizations that use Terminal Services, the recommended procedure is to first deploy the pre-requisites followed by the Secure Messaging Office Add-in.

Step-by-step procedure:

  • Login as Administrator on the server. Please note that each time before you install the add-in, you must be logged on with local administrator rights or, if necessary, domain administration rights.
  • Download the latest MSI for Terminal Services / Citrix. If pre-requisites are missing, the installation package will NOT download them and attempt to install them. Please ensure all pre-requisites are properly installed.
  • Before the installation can start, the Terminal Server must be switched to ‘installation mode’. You can perform this manually in DOS using the CHANGE USER command: CHANGE USER /INSTALL. The current mode can be determined with the /query command. Alternatively, you can perform the installation via the ‘Control Panel > Add/Remove Programs’. The Terminal Server will automatically switch to the right mode, and revert back to the execute mode when the installation is completed.
  • Distributed Installation with Load Balancing: If you are using a Citrix server farm with two or more servers, you can install the Add-in on every one of these servers.
  • Follow the prompts provided by the installer. Specify the path of the destination folder and remember that all users must have access to this folder on the server.
  • It is important that the administrator starts the Secure Messaging Office Add-in for the first time as this is when entries must be added to the Windows registry. To start the Add-in, simply launch Outlook and confirm that the add-in is present.NOTE: Before starting Outlook, the Terminal Server must be switched back to execute mode.
  • After Outlook Add-in is successfully installed, then a filed needs to be moved ( with administrative privileges ). Move file “DeliverySlipBrowser.exe“ from location : “C:\Users\{user}\AppData\Local\DeliverySlip\Toolbar” into location “C:\Program Files (x86)\Zix-Appriver\Secure Messaging Add-in“ or “C:\Program Files\Zix-Appriver\Secure Messaging Add-in“ – based on, where the Outlook add-in was installed.
  • Should the file “DeliverySlipBrowser.exe“ not exist in location “C:\Users\{user}\AppData\Local\DeliverySlip\Toolbar“, then open the Outlook with Secure Messaging add-in installed ( as a administrator ), and authenticate into Secure Messaging account. Once this is completed, “DeliverySlipBrowser.exe“ file in location “C:\Users\{user}\AppData\Local\DeliverySlip\Toolbar“ will be created.
  • Once properly installed, users can activate the Secure Messaging Office Add-in with their Secure Messaging portal simply by selecting a secure message in their Outlook Inbox. These users can all work with the add-in simultaneously.

NOTE: Even if your COM add-in or RTD server is registered for all users on the server, it may not start for users that have no permissions to access the folder where it is installed.


Does this work with Google, Office365 or Outlook?

Yes. DeliverySlip works equally well with Gmail/G Suite, Microsoft 365 and Outlook.

Do I need a new Email Account? Will there be Secondary passwords, PINS & keys to manage?

No, keep using your existing email address or aliases. Your email client and server infrastructure also remain the same. DeliverySlip works seamlessly from your inbox by using our Secure MS Outlook Toolbar or Chrome extension. There are no secondary passwords, PINS or keys required.

Where is the data stored when the email is sent securely?

Secure message content is stored encrypted at rest, using AES 256 bit encryption. Your encrypted data is stored in Microsoft Azure's cloud in the data jurisdiction that you selected (either USA, UK, Canada or Australia) upon your registration.

Do your support SSO (Single Sign On)?

DeliverySlip supports Azure Active Directory, Okta, Google, and others.

Does DeliverySlip work on mobile phones? Will I be able to read secure emails on a mobile phone?

Yes, DeliverySlip works on mobile phones and you will be able to read and reply to secure messages. Apps are available for iOS and Android devices.

Can email be automatically encrypted or must we manually encrypt it?

Yes. With data-leak prevention (DLP) rules enabled, DeliverySlip automatically encrypts information like Social Security, credit card or account numbers and keywords that can be tailored to your organization.

What regulatory compliance schemas do you support?

DeliverySlip is suitable for use with organizations that are subject to any number of regulatory compliance schemas including; GDPR, SOX, GBLA, FINRA and more.

Do you support “local store” for on premise Outlook Exchange?

Yes, local store for Outlook Exchange is supported. With this feature enabled, secure message content is stored locally in Outlook after you view the secure message, and then synced to Exchange.

Don't see your question here?

Check out our resource center for a full FAQ listing or complete our contact us form.

    How would you like to hear from us?

    Try it Now

    Your Secure Community portal is under construction. You will be redirected to your new portal shortly.

    creating portal