Who is this article for?

IT Personnel performing an installation of Mail Manager.

IT knowledge & access required.

There are two different installers available to install Mail Manager for Windows:

1. Per-User: Designed to be installed on the PC directly.
2. Per-Machine: Designed for shared machine environments (such as virtual environments and terminal servers).

This article outlines the benefits and restrictions of each version so that you can decide on which installation type is right for your organisation. To make this easier, the article has been split into the following sections:

1. Key Features of the Installation Types
2. Per-User Installations
3. Per Machine Installations
4. Further Reading

1. Key Features of the Installation Types

The table below outlines the key features of each installation type:

What to consider

• Single installation on a machine means a smaller hard drive footprint at scale
• The IT team need to be aware when new versions become available and take action
• IT Team required to deploy updated versions

2. Per-User Installations

Per-User installations are:

• Not suitable for VDI (Virtual Desktop Infrastructure) Systems.
• Installed via an installation wizard designed to guide you through the choices that suit your requirements (For example: Single users, multiple users, deployment methods, etc).
• Suitable for users to install themselves (self-service).
• Suitable for deployment via your software tool of choice.
• Able to be pre-configured with your license details and Shared Configuration Folder details.

When to consider a per-user installer:

• Best suited for companies who want Mail Manager for Windows updates applied automatically.
• Updates are automatically deployed, thereby reducing IT overhead of packing and deploying new versions.
• A single deployment can be performed for all users using the same machine.
• If a new user logs onto the machine, Mail Manager for Windows will be downloaded and installed automatically.
• New updates are automatically downloaded and installed for each user (approx. 100MB).
• Uninstalling Mail Manager won't impact other users using the same machine.

When not to choose per-user installer:

• If your company has many people use the same machine (for example, via terminal servers) or need to control which version of Mail Manager for Windows is used.
• Companies with certain software restrictions, policies, or white-listing software is used (e.g. Applocker, used to block executable files from running in %appdata% and %localappdata% locations).

All executables are signed, which provides proof that they have not been tampered or meddled with, and are being consumed in the way they were meant to be consumed.

Looking to perform a per-user installation? Visit How to Install Mail Manager (Per-User) for more details.

3. Per-Machine Installations

Per-Machine installations are:

• Required for Virtual Desktop Infrastructure (VDI).
• Performed using the per-machine installer (and not the per-user install file).
• Able to be pre-configured with your license details using the MSI configuration tool.
• Performed using administrative permissions for each PC.
• Disconnected from product updates, meaning IT have full control over what version is deployed.

When to consider a per-machine installer:

• Best suited to companies where multiple employees use the same machine (e.g. terminal servers) and/or need to control the version of Mail Manager for Windows used.

Why not to choose per-machine installer:

• Companies where each user works on an individual machine.
• Companies that want Mail Manager for Windows to update automatically.

All executables are signed, which provides proof that they have not been tampered or meddled with, and are being consumed in the way they were meant to be consumed.

Looking to perform a per-machine installation? Visit How to Install Mail Manager (Per-Machine) for more details.

4. Further Reading

• Minimum hardware and software requirements
• Installing Mail Manager (per-user)
• Installing Mail Manager (per-machine)
• Creating a Shared Configuration Folder
• Activating your license