# Using Software Distribution (Silent Install)

{% hint style="warning" %}
**IMPORTANT**\
Before performing silent installations, it is recommended to:

* Sign in to the Admin Portal at [**https://admin.mago.io**](https://admin.mago.io/)
* Pre-configure the global and room-specific Mago policies
* Add all license keys to your tenant in advance

This ensures that newly installed Mago instances will apply the correct configuration immediately after activation.
{% endhint %}

{% stepper %}
{% step %}

### Prepare for software distribution

1. Download the latest **Mago installer** (.exe) from the Admin Portal.
2. Copy the installer to your deployment system or file repository.
3. Ensure the deployment is executed with **administrator privileges** on the target machine.
4. Confirm that the device meets the required Windows 11, hardware and driver requirements.
   {% endstep %}

{% step %}

### Silent installation commands

The following commands perform a fully silent installation with no visible UI or prompts.

All commands must be executed in an elevated **cmd.exe** or by a software distribution tool running as Administrator.

**Option A) Install with default configuration (no local Mago user created)**

`Magoroom_installer.exe /KEY {Serial} /DEFAULT-CONFIG /S` 

Use this when your environment manages user accounts separately or when using Azure AD/Intune-based device provisioning.

**Option B) Install with default configuration and creation of local Mago user**

`Magoroom_installer.exe /KEY {Serial} /DEFAULT-CONFIG /LOCAL-USER /S` 

Creates a default **Mago** local user account automatically during installation.

**Option C) Install with default configuration and creation of custom local user with password**

`Magoroom_installer.exe /KEY {Serial} /DEFAULT-CONFIG /LOCAL-USER-USERNAME {username} /LOCAL-USER-PASSWORD {password} /S` 

Use this when your security policies require custom-defined local account names or passwords.
{% endstep %}

{% step %}

### Post-installation behavior

After a successful silent installation:

* The Mago application will be installed and registered as the primary shell for the Mago user
* The system will be ready to auto-login to the local Mago user (if created)
* Upon first launch, Mago will automatically activate using the provided license key
* The device will immediately apply all policies configured in the Admin Portal
  {% endstep %}

{% step %}

### Notes for mass deployments

* Ensure all required Windows 11 updates and hardware drivers are installed before pushing Mago.
* For environments with strict firewalls, validate that Mago required ports and URLs are whitelisted.
* Use the Admin Portal to centrally manage policies and room settings across all deployed devices.
* Reboots may be required depending on software distribution platform behavior.
  {% endstep %}
  {% endstepper %}