Two different installers are available to install Mail Manager for Windows, please read the following before making your decision which to use.
Per-user installer - not suitable for VDI systems
| • | Running the per-user-installer.exe will guide you through the choices that suit your requirements e.g. single or multiple users and deployment methods |
| • | Suitable for user's to install themselves or to deploy via your software of choice |
| • | Can be pre-configured with your licence details and Shared Configuration Folder details |
| • | If found during installation, an existing machine installation will be removed automatically. Note: local administrative permissions may be required to remove this |
| • | Users can use Mail Manager for Windows as a limited user |
| • | Using this method, Mail Manager for Windows will receive automatic updates i.e. no version sprawl |
Who it's for:
| • | This method is best for companies who want Mail Manager for Windows updates applied automatically i.e. install and forget |
Who it’s not for:
| • | Companies where many people use the same machine (like terminal servers) or need to control which version of Mail Manager for Windows is used |
| • | Where software restriction policies or other white-listing software is used e.g. AppLocker, to block executable files from running in %appdata% and %localappdata% locations. Note: Mail Manager executable's are digitally signed |
What to consider:
| • | No need for the IT team deploy updates – Mail Manager for Windows will be kept up to date with the latest version |
| • | Deploy once for all users using the same machine |
| • | Each time a new user logs on to the machine Mail Manager for Windows will be downloaded and installed automatically |
| • | Every user has their own installation of Mail Manager for Windows |
| • | Mail Manager for Windows will be installed to %LocalAppdata%\Mail Manager |
| • | New updates are downloaded (approx 100MB) and installed for each user automatically |
| • | Uninstalling Mail Manager for Windows won't affect other users using the same machine |
Per-machine installer - required for VDI systems
| • | The per-machine installer is used to install Mail Manager for Windows in: C:\Program Files or to a location of your choice |
| • | The installer can be pre-configured with your licence details etc. see Configure the MSI file for deployment (Step 3). |
| • | During the installation process administrative permissions are required |
| • | Once installed users can use Mail Manager for Windows as a limited user |
| • | It is multi-client-capable, meaning that it will be used by multiple users on the same machine |
| • | Using this method, Mail Manager for Windows will not receive automatic updates |
Who it's for:
| • | This method is best suited to companies where multiple employees use the same machine, e.g. terminal servers, and/or need to control which version of Mail Manager for Windows is used by their users |
Who it’s not for:
| • | Companies where people use their own machines or want Mail Manager for Windows updates applied automatically |
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 |
