Mimecast for Outlook: Deployment Options

Document created by user.oxriBaJeN4 Employee on Sep 9, 2015Last modified by user.oxriBaJeN4 Employee on Oct 6, 2016
Version 8Show Document
  • View in full screen mode

Mimecast supports deployment in both standalone and multi user environments. This article provides an overview of the deployment options, including the advantages and disadvantages of each.


Recommended Reading



Standalone Installation


Mimecast for Outlook can be downloaded and installed directly on the user's workstation. You can also create a network installation point, and copy the installer onto the network share.


  • Easier for environments with few users.
  • Allows users to initiate installation as needed.
  • Useful where technical knowledge is not available.
  • Difficult to control and monitor Mimecast for Outlook installations.


Group Policy


Administrators can use Group Policy scripts to deploy Mimecast for Outlook to many workstations.


  • Useful if there is no desktop management application (e.g. Microsoft System Center Essentials, System Center Configuration Manager) but you need an automatic deployment mechanism.
  • Uses existing Active Directory Domain (AD DS) and Group Policy features.
  • AD DS handles the elevation of privileges required for application installation.
  • A script can be written in any language that is supported by the client computer.
  • Can be difficult to determine the Mimecast for Outlook installation success.
  • Uninstalls / installs for multiple computers must be undertaken using a command line script / batch file.
  • Can be difficult to determine exactly which versions are deployed to each workstation.


Managed Deployment


Mimecast for Outlook can be deployed to many workstations at the same time using a centralized deployment tool (e.g. Microsoft SCCM). 


  • Reduces administrator overhead.
  • Centralizes control, monitoring, reporting and issue resolution of deployment.
  • Requires supporting infrastructure.
  • Requires appropriate administrator skills and experience.


Multi User Environments


Mimecast for Outlook can be deployed to multi-user environments (e.g. Citrix, Terminal Services). This reduces the administrative overhead of Mimecast for Outlook deployment. A SQL server is required as a backend to store the end user's profiles.

AppV is not supported for use with Mimecast for Outlook.

  • Centralizes the management of Mimecast for Outlook installs.
  • Supports end user roaming experience.
  • Mimecast for Outlook can be made available to end users quickly.
  • Use of Mimecast for Outlook in non-cached mode does not support the Continuity functionality in the product. This is due to the mailbox itself being unavailable.
2 people found this helpful