Product Feature Sheets
This section describes the system requirements and the installation files & guide for the Delivery Slip 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.
The deployment and upgrade management for the Delivery Slip 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.
The Delivery Slip Office Outlook Add-in supports the following software configurations:
|TROUBLESHOOTING: For the Enterprise Edition, the .NET framework installation must be completed separately directly from the Microsoft website: https://www.microsoft.com/en-ca/download/details.aspx?id=42642. The latest version of the .NEtT framework is usually already installed with most latest version of Windows.|
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:
Step 1: Creating the add-in distribution point:
Step 2: Creating the group policy object in Windows Server 2008, 2008 R2, 2012 & 2012 R2:
Step 3: Assigning the installation package:
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.
Upgrading the package:
For organizations that use Terminal Services, the recommended procedure is to first deploy the pre-requisites followed by the Secure Messaging Office Add-in.
NOTE: Before starting Outlook, the Terminal Server must be switched back to execute mode.
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.
Yes. DeliverySlip works equally well with Gmail/G Suite, Microsoft 365 and Outlook.
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.
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.
DeliverySlip supports Azure Active Directory, Okta, Google, and others.
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.
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.
DeliverySlip is suitable for use with organizations that are subject to any number of regulatory compliance schemas including; GDPR, SOX, GBLA, FINRA and more.
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.
Check out our resource center for a full FAQ listing or complete our contact us form.
Your Secure Community portal is under construction. You will be redirected to your new portal shortly.