The Twingate Windows client is distributed in an MSI package in order to allow automated managed device deployment. We maintain a list of MSI releases, which you can download and configure in your MDM solution.
The Twingate Windows client distributed via https://get.twingate.com/ is an EXE package that is not intended for deployment via an MDM such as InTune. For access to a list of MSI-packaged releases, see Windows Releases.
The MSI package supports a number of command line options that are useful for automated deployments:
- Silent installation. The
/qnoption will suppress the installation dialog and automatically accept the user terms of service.
- Pre-configure the Twingate Network. The
network=option allows pre-configuring the Twingate Network name so that users do not have to enter this information.
- Disable automatic updates. Setting
no_optional_updates=truewill disable optional updates. See the next section for more information on why you might want to do this.
In this example, this will install the Twingate Windows client, setting the Twingate Network to
beam reach.twingate.com and disable optional updates.
TwingateWindowsInstaller.msi /qn network=beamreach.twingate.com no_optional_updates=true
Usually, yes, but this depends on whether you allow users to have local admin rights on their Windows PC. Automatic updates cannot be installed without the local user providing administrator authorization, so if you do not allow local admin rights, you should disable automatic updates. The MSI command-line setting allows flexibility for different user groups depending on their local admin permissions.
- If you allow local admin rights. You may leave optional updates enabled (this is the default). Users will be prompted when an update is available and asked to update the Twingate client.
- If you do not allow local admin rights. You should disable optional updates. If they are enabled, users will receive update availability prompts, but will not be able to update the client. New versions of the Twingate Windows client must be pushed to users via your MDM solution.
Updated 20 days ago