Mimecast Synchronization Engine Requirements

Document created by user.zL0FB6L9lN Expert on Nov 2, 2015Last modified by user.oxriBaJeN4 on Apr 27, 2017
Version 16Show Document
  • View in full screen mode
This page applies to Mimecast Synchronization Engine version 3.x or later.

To better understand the Mimecast Synchronization Engine (MSE) requirements, we recommend that this page is read in conjunction with the following articles:


Supported Environments


Operating Systems


Windows Server 2003
Windows Server 2008
Windows Server 2008 R2
Windows Server 2008 R2 Service Pack 1
Windows Server 2012
Windows Server 2012 R2
Windows Server 2016


Application Servers and Platforms


PlatformsMailbox Folder ReplicationCalendar ReplicationMailbox Storage ManagementExchange Managed FoldersInstant Messaging ArchivingFile ArchivingActive Directory Synchronization
Exchange 2003NANANA
Exchange 2007NANANA
Exchange 2007 Service Pack 3NANANA
Exchange 2010NANANA
Exchange 2013NANANA
Exchange 2016NANANA
Office 365 HybridNANANA

Office 365


Skype for Business 2015 On-PremisesNANANANA

Skype for Business OnlineNANANANANANA
Exchange Server 2007 SP3 will no longer be supported in Mimecast Synchronization Engine releases released after 10th April 2018.

Hardware Requirements


The recommended hardware requirements for a Mimecast Synchronization Engine site varies depending on the following factors:

  • Total number of scheduled tasks
  • Task type
  • Schedule frequency


The minimum hardware requirements for a Mimecast Synchronization Engine site, in addition to the host operating systems requirements, are:



2+ cores @ 2Ghz




At least 40 GB of available disk space, on the drive where the application is installed. It is recommended that:

  • The default path for both the state and log file directories is changed during installation.
  • Additional disk space is allocated for state, logs, cache, and temporary files during operation.


Software Requirements


The following software is required for the Mimecast Synchronization Engine to install:


Mimecast Synchronization Engine VersionPowerShell Version.Net Framework Version


Network Requirements


Mimecast Synchronization Engine v4.x


Mimecast Synchronization Engine v4 must be able to communicate externally from your network to the Mimecast platform over HTTPS.


The global discovery and regional service endpoints must be accessible from the server hosting Mimecast Synchronization Engine v4. Mimecast Synchronization Engine v4 must be able to communicate with the global discovery endpoint during the bind process, and the customers respective regional service endpoint during normal operation.


The global discovery endpoint destination below is used during the bind process, and will need to be permitted where restrictions on outbound traffic are in place.



In addition, your regional service endpoint must be permitted, where restrictions on outbound traffic are in place.



Mimecast Synchronization Engine v3.x


MSE communicates from your network using HTTPS outbound to the Mimecast platform. Depending on the region where your Mimecast account is hosted, it is critical that the server where MSE is installed has outbound HTTPS access to the following hosts:



Firewall and Proxy Considerations


The following firewall and proxy points must be considered:

  • If your organization uses a proxy server or web filtering services, you should be aware that communications will be initiated by the NETWORK SERVICE account. Where proxy settings are enforced, ensure this is factored in during your implementation.
  • To prevent issues with related to connection timeouts, an increase in the connection timeout period for half open connections may be required.


Host Server Considerations


The Mimecast Synchronization Engine must be installed on a member or standalone server. The choice on where to host the MSE depends heavily on the features that will be provisioned on the server.

The Mimecast Synchronization Engine should not be installed on an Exchange server, domain controller, or any other line of business application server (e.g. SQL server).

Active Directory Synchronization


When provisioning a Mimecast Synchronization Engine site for Active Directory synchronization, the recommended location must be on the same LAN as a dedicated Domain Controller. This ensures best performance for larger deployments.


Exchange Services: On-Premises Exchange


Applies to: Mailbox folder replication, calendar replication, mailbox storage management, and exchange managed folders.


With On-Premises Exchanges, the following must be considered:

  • The Mimecast Synchronization Engine must be installed on same LAN as the Exchange servers, while having access to Active Directory Domain services in order to resolve objects, etc. Failed tasks and delays in the time scheduled tasks take to execute, may be observed if either Exchange or Active Director become unavailable.
  • Access to a domain controller with the global catalog may be required in certain deployments.
  • Ensure a fast and reliable connection from the Mimecast Synchronization Engine site to the target data source (e.g. Office 365, Exchange, File Servers, SQL Server, Active Directory, etc.).


File Archiving


The following must be considered with file archiving:

  • The Mimecast Synchronization Engine should ideally be installed on same LAN as the file servers hosting the files being archived. Failure to do so, may result in degradation in performance.
For file archiving tasks, take note of the user account that the Mimecast Synchronization Engine Windows service is running under, prior to upgrading from 2.9.x to 4.x. After the upgrade, change the account running the Mimecast Synchronization Engine Windows service from NETWORK SERVICE to the user account used for the 2.9.x Windows service.

Instant Messaging (IM) Archiving


The following must be considered with IM archiving:

  • The Mimecast Synchronization Engine should ideally be installed on same LAN as the SQL servers hosting the Lync archive database you wish to archive. Failure to do so may result in a degradation in performance.
For IM archiving tasks, take note of the user account that the Mimecast Synchronization Engine Windows service is running under, prior to upgrading from 2.9.x to 4.x. After the upgrade, change the account running the Mimecast Synchronization Engine Windows service from NETWORK SERVICE to the user account used for the 2.9.x Windows service.

Service Account


The Windows Service account the Mimecast Synchronization Engine service runs under, currently requires the English locale.




The following group types are supported by the Mimecast Synchronization Engine:

  • Security
  • Distribution. These must not be hidden from the Global Address List.
  • Dynamic Distribution


The following methods of grouping users are unsupported by the Mimecast Synchronization Engine:

  • Organizational Units
  • Domain or Forest level :
    • Dynamic Distribution


See Also...


1 person found this helpful