MSI for per-machine installation

This MSI is suitable for companies that want to pre-install the app and have more control over it.

• The company wants a single installation (saves disk space).
• Single install location facilitates easier IT rules for Firewall allow lists and Software Restriction Policies (SRP).
• Companies can choose to manually roll out updates or let users auto-update (requires admin privileges for users).
• Since the MSI for per-machine installation requires admin privileges for auto-updates, this type of MSI is recommended when manual updates are used.
• Per-machine installation makes it easier to restrict users from uninstalling the app (due to requiring admin privileges).

MSI for per-user installation during user login

This MSI is suitable for companies that want to pre-install the app but want to let users have control over the app.

• The company does not want to manage the app for the user other than just pre-install it for them.
• They let the user update and uninstall the app if they desire.
• The MSI for per-user installation during user login deploys the app in the user folder; thus, the auto-update does not require admin privileges. We recommend this MSI if automatic updates are preferred.

This is an MSI for deploying the GoTo app as a single installation per machine (in Program Files).

• Installation requires elevation (admin permissions).
• Automatic updates can be enabled or disabled. They are enabled by default.
• If automatic updates are enabled:
  • The user is notified about updates while using the product, and can manually check for new updates.
  • Any available updates are automatically installed upon exit.
  • When an update is installed, the user will see a User Account Control prompt to grant admin permissions, because the update affects all users on the machine.
  • If the user does not or cannot authorize the action, the update will not happen and the user will be prompted again in the future.
• If automatic updates are disabled:
  • The user will not receive notifications for new updates and cannot check manually for updates.
  • The only way to update the app is for the company to roll out a new MSI.
• Rolling out a new MSI will update or roll back the app to the version carried in the MSI. This includes cases where an auto-update may have installed a newer version than the version in the MSI being rolled out. To ensure consistency in the update approach, it is suggested to either perform a one-time MSI roll out and let automatic updates take care of future updates, or to consistently roll out the MSI with automatic updates disabled, and establish a manual update cadence.

This is an MSI for deploying an installer for per-user GoTo on the machine level (in Program Files) and setting up a login hook for all current users and any new users to run the per-user installer at user login. This MSI deploys the GoTo user installer and not the GoTo app itself. The GoTo installer will add the GoTo app for each user who logs in on the machine. The app will be installed only the first time the user logs in and will be installed in the user's profile.

Users are free to remove the GoTo app, as it is installed per user.

• Installation of the MSI requires elevation (admin permissions), while the per-user install performed at user login does not. The per-user install at user login is silent.
• The MSI install sets up a RunOnce entry for each existing user profile on the machine, including the default (template) user profile.
  • The entry contains a command line starting the per-user installer in silent mode.
  • The entry added to the default (template) user profile ensures that new users who sign in for the first time on a machine will get the app too.
  • The RunOnce entry ensures that the user installer will be started only once per user. Windows deletes RunOnce entries after they are executed.
  • Uninstalling the MSI removes the RunOnce entry added by the installer (if it still exists), including the entry in the default (template) user profile.
• Automatic updates can be enabled or disabled. They are enabled by default.
• If automatic updates are enabled:
  • The user is notified about updates while using the product, and can manually check for new updates.
  • Any available updates are automatically installed upon exit.
  • Updates happen for each user individually, do not require admin permissions, and will not update other users.
  • If an auto-update happens, the app version will be newer than the version of the MSI and the GoTo per-user installer that installed it.
• If automatic updates are disabled:
  • The user will not receive notifications for new updates and cannot check manually for updates.
  • The only way to update the app is for the company to roll out a new MSI.
• Rolling out a new MSI will update the GoTo per-user installer and set the RunOnce entries as described above. Upon user login the GoTo app will be installed (for first time users) or updated (for existing users) to the new version of the MSI.
• Rolling out a new MSI will update or roll back the app to the version carried in the MSI. This includes cases where auto-update may have installed a newer version than the version in the MSI being rolled out. To ensure consistency in the update approach, it is suggested to either perform a one-time MSI roll out and let automatic updates take care of future updates, or to consistently roll out the MSI with automatic updates disabled, and establish a manual update cadence.

The MSIs support a property AUTOMATICUPDATES, which can be set during installation. Setting this property during MSI installation directly sets the AutomaticUpdates registry setting in the app registry key Software\LogMeInInc\GoTo, under HKLM or HKCU:

• The MSI for per-machine installation sets the registry setting on the machine level (HKLM\Software\LogMeInInc\GoTo).
• The MSI for per-user installation during user login sets the registry setting on the user level (HKCU\Software\LogMeInInc\GoTo).

The MSIs support custom properties that can be supplied during installation to customize the deployment. These properties can be supplied to the command line if the MSI is installed via a command line, or via a transform file (MST) if deployed via Group Policy Object (GPO) or other deployment software.

Example of a command line specifying MSI properties: msiexec.exe /i GoToSetupMachine-x64.msi APPLICATIONFOLDER="%ProgramFiles%\CustomGoToFolder" FORCERUN=1

Properties supported by the MSI for per-machine installation

Properties supported by the MSI for per-user installation during user login

The MSIs are offered in 64-bit and 32-bit architectures. They install the app in the respective architecture.

The MSI architecture must match the OS architecture. The 64-bit MSI will fail with an error message if run on a 32-bit OS, and the 32-bit MSI will fail with an error message if run on a 64-bit OS.

The MSIs can be downloaded here.