> ## Documentation Index
> Fetch the complete documentation index at: https://anaconda.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Enterprise deployment

The Miniconda MSI installer is compatible with endpoint and fleet management tools that support the MSI format, such as Microsoft Intune, SCCM, and Group Policy. This page covers the information your IT admin needs to deploy Miniconda to managed Windows devices, regardless of which tool they use.

## System requirements

Requirement

Value

**Architecture**

64-bit (x86\_64 or Arm64)

**Operating system**

A [supported version of Windows](https://anaconda.com/docs/reference/policies-practices/platform-support.md#windows)

## Install and uninstall commands

Most endpoint management tools require an [install command](#install-command) and an [uninstall command](#uninstall-command). Replace the MSI filename in the following commands with the filename of the installer you downloaded.

For the full list of `msiexec` properties available during installation, see [Silent installation](https://anaconda.com/docs/getting-started/msi-installer-beta/install/silent-install.md).

### Install command

```sh theme={null}
msiexec /i "<MSI_FILENAME>" /qn ALLUSERS=1 /norestart /l*v "%TEMP%\miniconda_install.log"
```

Comments

Replace \<MSI\_FILENAME> with the filename of the MSI installer (for example, `Miniconda3-PBE-26.9.4.beta1-Windows-x86_64.msi` or `Miniconda3-PBE-26.9.4.beta1-Windows-arm64.msi`).

Flag

Purpose

`/qn`

Run with no user interface (fully silent)

`ALLUSERS=1`

Install for all users on the device

`/norestart`

Prevent an automatic restart after installation

`/l*v "%TEMP%\miniconda_install.log"`

Write verbose logging to a file for troubleshooting

You can append additional properties to customize the installation. See [Silent installation](https://anaconda.com/docs/getting-started/msi-installer-beta/install/silent-install.md) for all available properties, including `OPTION_ENABLE_SHORTCUTS`, `OPTION_REGISTER_PYTHON`, and `INSTALLFOLDER`.

### Uninstall command

```sh theme={null}
msiexec /x "<MSI_FILENAME>" /qn /norestart /l*v "%TEMP%\miniconda_uninstall.log"
```

Comments

Replace \<MSI\_FILENAME> with the filename of the MSI installer.

You can append additional cleanup properties to the uninstall command, such as `OPTION_REMOVE_USER_DATA`, `OPTION_REMOVE_CACHES`, and `OPTION_REMOVE_CONFIG_FILES`. See [Uninstalling Miniconda (MSI)](https://anaconda.com/docs/getting-started/msi-installer-beta/uninstall.md) for details.

## Detection rules

After deploying Miniconda, your management tool needs a way to determine whether the app is already installed on a device. The approach depends on your tool, but the two most common methods for MSI packages are product code detection and file-based detection.

### MSI product code (recommended)

Most endpoint management tools can detect installed MSI packages by their product code. This is the most reliable method because it does not depend on file paths.

If your tool does not auto-detect the product code from the MSI package, you can find it by installing the MSI on a test machine and checking the Windows registry under:

```
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
```

### File-based detection

If your tool does not support MSI product code detection, you can check for the `_conda.exe` binary that the MSI installer places at the top level of the installation directory. The path depends on how the installer was configured:

* **Per-user install** (default): `C:\Users\<USERNAME>\AppData\Local\Programs\Miniconda3-PBE <CONDA-VERSION>`
* **All-users install** (`ALLUSERS=1`): `C:\Program Files\Miniconda3-PBE <CONDA-VERSION>`
* **Custom directory** (`INSTALLFOLDER`): Whatever path you specified in the install command

In the paths above, `<USERNAME>` is the Windows user account name and `<CONDA-VERSION>` is the version of conda bundled in the installer (for example, `26.9.4`).

Field

Value

Path

Your installation directory (see above)

File

`_conda.exe`

> [!NOTE]
>
> The default installation directory includes the version in its name (for example, `Miniconda3-PBE 26.9.4`). This path changes with each installer version, which makes file-based detection less reliable across upgrades. Use MSI product code detection when possible.

## Return codes

The MSI installer uses standard Windows Installer return codes:

Code

Meaning

`0`

Success

`1707`

Success

`3010`

Success, soft reboot required

`1641`

Success, hard reboot required

`1618`

Another installation is in progress, retry later