> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/unigetui/for-it-teams/organization/deploy.md).

# Deploy UniGetUI silently

Install UniGetUI silently on many Windows computers, for one user or for all users, with a script or your software distribution tool.

The Windows installer runs without any window when you give it the right switches. That's all you need to push UniGetUI to many computers from a script, Microsoft Intune, Configuration Manager, or any other software distribution tool.

## Choose who gets UniGetUI

<table><thead><tr><th width="200">MODE</th><th>WHERE IT GOES</th><th>WHEN TO USE IT</th></tr></thead><tbody><tr><td><strong>Current user</strong> (default)</td><td><code>%LOCALAPPDATA%\Programs\UniGetUI</code></td><td>One person installs it for themselves. No administrator rights needed.</td></tr><tr><td><strong>All users</strong> (<code>/ALLUSERS</code>)</td><td><code>C:\Program Files\UniGetUI</code></td><td>Managed computers. Requires administrator rights, and users can't modify the program files.</td></tr></tbody></table>

For a managed fleet, install for all users. It's also required if you want to edit the Devolutions Agent policy from UniGetUI (see [Install approved apps without admin rights](/unigetui/for-it-teams/organization/devolutions-agent.md)).

## Install silently

1. Download the installer for your architecture from the [Devolutions website](https://devolutions.net/unigetui/) or the [GitHub releases](https://github.com/Devolutions/UniGetUI/releases/latest): `UniGetUI.Installer.x64.exe` or `UniGetUI.Installer.arm64.exe`.
2. Open PowerShell as an administrator.
3. Run the installer:

```powershell
.\UniGetUI.Installer.x64.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /ALLUSERS /NoAutoStart
```

To keep a log of the installation, add `/LOG="C:\Windows\Temp\UniGetUI_install.log"`.

### Switches you'll use most

<table><thead><tr><th width="260">SWITCH</th><th>WHAT IT DOES</th></tr></thead><tbody><tr><td><code>/VERYSILENT /SUPPRESSMSGBOXES</code></td><td>No wizard, no progress window, no message boxes.</td></tr><tr><td><code>/NORESTART</code></td><td>Never restart the computer.</td></tr><tr><td><code>/ALLUSERS</code></td><td>Install for all users in Program Files.</td></tr><tr><td><code>/NoAutoStart</code></td><td>Don't open UniGetUI at the end of the installation.</td></tr><tr><td><code>/NoRunOnStartup</code></td><td>Register the startup entry as disabled, so UniGetUI doesn't start at sign-in.</td></tr><tr><td><code>/NoDesktopShortcut</code></td><td>Don't create a desktop shortcut.</td></tr><tr><td><code>/NoVCRedist</code>, <code>/NoEdgeWebView</code></td><td>Skip installing the Visual C++ Redistributable or the WebView2 Runtime, if your images already include them.</td></tr></tbody></table>

The complete list, including the Inno Setup tasks you can pass to `/TASKS` and `/MERGETASKS`, is in [Install UniGetUI](/unigetui/reference/installation.md).

## Deploy with a management tool

The installer is a regular `.exe` with silent switches, so it fits any tool that can run a command line. The general approach:

1. Package `UniGetUI.Installer.x64.exe` (and the arm64 version if you have Arm devices).
2. Use the silent command above as the install command, and run it with administrator rights (for Intune Win32 apps, that's the **System** install behavior).
3. Detect the installation with the uninstall entry named ***UniGetUI*** in the list of installed apps, or with the presence of `C:\Program Files\UniGetUI\UniGetUI.exe`.
4. Deploy to a pilot group first, then to everyone.

If your tool only accepts MSI packages, such as Group Policy software installation, you can build an MSI wrapper with the project files in the `InstallerExtras/MsiCreator` folder of the [GitHub repository](https://github.com/Devolutions/UniGetUI). The wrapper doesn't install the dependencies, so make sure the Visual C++ Redistributable and the WebView2 Runtime are already on the computers.

{% hint style="warning" %}
The installer registers UniGetUI to start at sign-in **for the account that runs the installer** (it writes to that account's registry hive). When you deploy as SYSTEM, your users don't automatically get UniGetUI in their startup apps. If you rely on [scheduled maintenance](/unigetui/for-it-teams/organization/standard-workstations.md), which only runs while UniGetUI is running, add a startup entry for your users with your usual tool.
{% endhint %}

## Good to know

* **Updating UniGetUI:** run a newer installer with the same switches. Your users' settings are kept, because they're stored in each user's profile.
* **Preset settings:** settings are per user. To ship a baseline, export them on a reference computer and import them with `UniGetUI.exe --import-settings <file>`. See [Command-line interface](/unigetui/reference/cli.md).
* **Security settings** are stored separately and protected. See [Lock down risky settings](/unigetui/for-it-teams/organization/restrict-settings.md).
* **Antivirus warnings on rollout:** see [My antivirus flags UniGetUI](/unigetui/help/troubleshooting/antivirus-flags-unigetui.md).

## Next

* [Lock down risky settings](/unigetui/for-it-teams/organization/restrict-settings.md)
* [Standardize workstations](/unigetui/for-it-teams/organization/standard-workstations.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/unigetui/for-it-teams/organization/deploy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.