Use the MSI installer to install MaxTo for a wide set of users in your enterprise.

The MSI installer package is not intended for ordinary installations of MaxTo. If you don't know what Group Policy is, use the normal installer instead.

When you install the MSI package, all the users on the machine will get their own copy of MaxTo installed the next time they log in.

It is important to note that when you run the MSI package, it will appear to do nothing (besides asking you for administrative permissions).

Known pitfalls when deploying the MSI package

Nothing happens when users log in

The MSI package will not re-install MaxTo on login for users who have previously uninstalled MaxTo.

It does this by checking for the existence of the %LocalAppData%\MaxTo folder. If this folder exists, MaxTo will not be installed on login.

To get around this issue, delete the %LocalAppData%\MaxTo folder for the affected user profiles.

User installation of .NET Framework fails

MaxTo requires .NET Framework version 4.7.2. The normal installer (which is what the MSI runs on login) will attempt to install this dependency if it is not already installed. This can fail in some cases.

We strongly recommend deploying the .NET Framework version 4.7.2 in addition to MaxTo.