> For the complete documentation index, see [llms.txt](https://support.goodaccess.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.goodaccess.com/configuration-guides/features/msi-deployment.md).

# MSI deployment

{% hint style="info" %}
This feature is available in the **Essential plan and higher**.
{% endhint %}

This page provides an overview of Client Application deployment using MDM tools. Select a deployment scenario below and follow the corresponding instructions.

## 🚀 Deployment scenarios

The Client Application can be deployed using different methods depending on your environment and update strategy:

#### Automatic updates

The application is installed with automatic updates enabled.

* The built-in updater is enabled
* The application updates automatically without requiring administrator action
* MDM tools are used only for initial deployment
* Version control is handled by the application itself

👉 This corresponds to `AUTO_UPDATES=true` in [🔧 Public properties](#public-properties).

**👉 Ensure that version enforcement is disabled in your MDM tool so the application can update itself.**

💡 Example (Microsoft Intune): Configure “Ignore app version” to “Yes” so that application updates are not enforced by the MDM tool.

*Recommended for environments where application updates are handled automatically without user or administrator involvement.*

#### Manual updates

The application is managed through your MDM tool.

* The built-in updater is disabled
* Application updates are controlled by administrators via MDM
* New versions must be deployed manually through the management system

👉 This corresponds to `AUTO_UPDATES=false` in [🔧 Public properties](#public-properties).

**👉 Ensure that the built-in updater is disabled and that application version control is enforced through your MDM tool.**

💡 Example (Microsoft Intune): Configure “Ignore app version” to “No”, allowing the MDM tool to enforce application updates.

*Recommended for environments where application updates are centrally managed by administrators.*

## ⚙️ Command-line arguments

The following arguments control installation behavior.

#### **/qn (silent installation)**

Runs the installation in silent mode without any user interface.

* No prompts or dialogs are shown
* Installation runs in the background

#### /norestart

Prevents the system from restarting after the installation is completed.

* The installation finishes without triggering a system reboot
* Any required restart must be handled manually

## 🔧 Public properties

These MSI public properties define how the application behaves after installation.

{% hint style="danger" %}
Changing the AUTO\_UPDATES property inconsistently with the selected deployment scenario may lead to unexpected application behavior across environments.
{% endhint %}

#### **AUTO\_UPDATES**

* **Default:** true
* **Values:** true / false
* **Format:** `AUTO_UPDATES=false`

Defines how the application handles updates when new versions are available.

* **true:**\
  The built-in updater is enabled. The application prompts the user to install updates when available and will automatically install them if the update is not applied within a certain period.
* **false:**\
  The built-in updater is disabled. The application notifies the user about updates and requires administrator-managed installation.

#### **DEFAULT\_PROTOCOL**

* **Default:** openvpn
* **Values:** openvpn / ikev2
* **Format:** `DEFAULT_PROTOCOL=ikev2`

Defines the default connection protocol used by the application.

* **openvpn:**\
  Recommended for stable and persistent connections (e.g., RDP sessions).
* **ikev2:**\
  Alternative protocol suitable for standard VPN connections.

#### **PERSISTENT**

* **Default:** false
* **Values:** true / false
* **Format:** `PERSISTENT=true`

Controls whether the application maintains connection state across system sessions.

* **true:**\
  Automatically establishes a connection at system startup (before user login) and keeps the connection active after Windows lock or user logout.
* **false:**\
  Connects only after user login and disconnects on logout or lock screen.

## 📥 Download

* [MSI package](https://link.goodaccess.com/download-windows-link)

{% hint style="danger" %}
**The MSI package grants per-user update capabilities**.

When deploying via MDM tools, this behavior can be controlled by enabling or disabling automatic updates.

⚠️ **Incorrect configuration may lead to unexpected behavior or issues related to deployment.**

Please select one deployment scenario above and ensure that all settings and arguments are configured consistently.
{% endhint %}

## 📓 Changelog

* [Windows changelog](/product-changelog/windows.md)