---
title: "Deploy to Multiple Machines"
canonical: "https://documentation.chaos.com/space/ENSCAPE/840695811/Deploy%20to%20Multiple%20Machines"
format: markdown
---
This page provides information on how to deploy Chaos License Server on multiple machines.
## **For Enscape Versions 4.1 Onwards**
---
To deploy a license across multiple machines, install the **[Chaos License Server on a centralized machine](https://docs-chaos.atlassian.net/wiki/spaces/LIC5/pages/124494252)** on your office network that is accessible to all users. Authenticate it with your Chaos Account that holds your floating licenses.
Enscape users (or your IT administrator) on your network need to configure their copy of Enscape to connect to the License Server, either during [installation](https://docs-chaos.atlassian.net/wiki/spaces/enscape/pages/841056264) or using an external utility installed alongside Enscape.
To perform a silent installation, follow the instructions on the [Installer Program Options](https://docs-chaos.atlassian.net/wiki/spaces/enscape/pages/841908266) page.
> ℹ️ This method applies to both Latest releases and [Long-Term Support](https://docs-chaos.atlassian.net/wiki/spaces/enscape/pages/943357960) versions of Enscape.
## **For Enscape Version 4.0**
---
To deploy a license automatically and eliminate the need for manual code entry during the first launch of Enscape, follow these steps:
1. Open an Administrator command prompt.
2. Run the installation file with the specified arguments to install for all users on the machine.
3. To install for the current user only, run the installation file from a standard non-Administrator command prompt.
```
PATHtoENSCAPEexe -gui=0 -acceptEULA
```
The **-acceptEULA** argument accepts the EULA. If the **-acceptEULA** option is not specified, the installer terminates because the EULA is not accepted.
Follow the installation instructions and configure the setup as needed across all machines. The installer creates a file named *config.xml* in the folder of the installation file. Save this *config.xml* file, as it is required to install Enscape on other machines.
To install Enscape via a deployment script and add the Enscape license key to the Windows Registry, use a script like the following:
```
reg query HKEY_LOCAL_MACHINE\SOFTWARE\Enscape /v LicenseKey >nul
if %errorlevel% equ 1 (
reg add HKEY_LOCAL_MACHINE\SOFTWARE\Enscape /reg:64 /v LicenseKey /t REG_SZ /d your_Enscape_license_code
)
PATHtoENSCAPEexe -gui=0 -acceptEULA -configFile=”config.xml” -quiet=1
```
> ⚠️ **PATHtoENSCAPEexe** in the argument above refers to the location of the exe installer on your machine. For example, it could be **C:\Users\username\Downloads\Enscape-4.0.0.577.exe**
If problems occur during the command line installation, add the **-debug=3** argument at the end of the command line. This creates an installer log file named, for example, *installer_debug_XXX.log* (where *XXX* is the timestamp) in the current TEMP directory. Send this file along with any other relevant information when submitting a support ticket.
> ⚠️ This process requires a separate Enscape license key, which must be requested directly. To request a key, contact [support](https://support.chaos.com/hc/en-us).
## **For Enscape Versions 2.8 to 3.5**
---
To deploy a license automatically and eliminate the need for manual code entry during the first launch of Enscape, follow these steps:
1. Create a string registry key called “LicenseKey” under HKEY_LOCAL_MACHINE\SOFTWARE\Enscape.
2. Set your License Key as the value of the created registry key.
On startup of the CAD software, the license code in the registry key is applied automatically.
> ⚠️ This process requires a separate Enscape license key, which must be requested directly. To request a key, contact [support](https://support.enscape3d.com/hc/en-us).
Here’s a very simple deployment script which you can adapt to your needs:
```
reg query HKEY_LOCAL_MACHINE\SOFTWARE\Enscape /v LicenseKey >nul
if %errorlevel% equ 1 (
reg add HKEY_LOCAL_MACHINE\SOFTWARE\Enscape /reg:64 /v LicenseKey /t REG_SZ /d your_Enscape_license_code
)
start /w msiexec.exe /i Enscape.msi /quiet ACCEPTEULA=1
```
For information on all the available switches, refer to the [Installer Program Options page](https://docs-chaos.atlassian.net/wiki/spaces/enscape/pages/841908266). To read the Enscape version automatically (prior to 4.0), refer to the [Read the Version Automatically page](https://docs-chaos.atlassian.net/wiki/spaces/enscape/pages/840827035).
## **For Enscape Versions Prior to 2.8**
---
To deploy a license automatically and eliminate the need for manual code entry during the first launch of Enscape, follow these steps:
1. Create a file called “License.txt” containing your license code.
2. Create the directory “*%ProgramData%\Enscape*” on the computer on which you want to deploy Enscape.
3. Place the License.txt in that freshly created directory.
On startup of the CAD software, the license code in the file is applied automatically. After a successful deployment, the file is deleted.
Here’s a very simple deployment script that you can adapt to your needs:
```
if not exist "%ProgramData%\Enscape" md "%ProgramData%\Enscape"
echo your_license_code > "%ProgramData%\Enscape\License.txt"
start /w msiexec.exe /i Enscape.msi /quiet ACCEPTEULA=1
```
> ℹ️ To deploy the license on each startup (for each user) without deleting it, name the file *License-Persistent.txt* and place it in `%ProgramData%\Enscape`.
## **Suppress Taskbar Icon Grouping**
---
**For versions 4.2 onwards**, the Suppress Taskbar Icon Grouping setting can be enabled. All Enscape windows will then appear as a separate group of windows in the taskbar. To suppress grouping, you can run the following command as an Administrator:
```
REG ADD “HKEY_LOCAL_MACHINE\SOFTWARE\Enscape” /v SuppressTaskbarIconGrouping /t REG_SZ /d 1 /f
```
## **Suppress Notifications**
---
To suppress Enscape Update Notifications, Graphics Card Driver warnings, and the First Steps window, use the following commands:
- **REG ADD “HKEY_LOCAL_MACHINE\SOFTWARE\Enscape” /v SuppressUpdateNotifications /t REG_SZ /d 1 /f**
- **REG ADD “HKEY_LOCAL_MACHINE\SOFTWARE\Enscape” /v SuppressGraphicsDriverWarning /t REG_SZ /d 1 /f**
- **REG ADD “HKEY_LOCAL_MACHINE\SOFTWARE\Enscape” /v SuppressFirstStepsWindow /t REG_SZ /d 1 /f**
To perform this for the current user, just replace the **HKEY_LOCAL_MACHINE** with **HKEY_CURRENT_USER**.
> ⚠️ The implementation for suppressing these pop-up notifications is currently subject to change.
## **Deploying Enscape for ArchiCAD for All Users - 4.0**
---
Selecting **All Users** from the installer's options only installs Enscape for users who have already started ArchiCAD at least once. To ensure installation for every new user on the machine, do the following:
- [Run a script on any user’s first log on](https://support.microsoft.com/en-us/help/325347/how-to-run-a-logon-script-one-time-when-a-new-user-logs-on-in-windows) using CMD, run as an administrator:
*“C:\Program Files\Enscape\ egistration\Enscape.Installer.Runtime.exe” install -archicad -all-users “C:\Program Files\Enscape”*
> ⚠️ This command assumes the installation path is `C:\Program Files\Enscape`. If it is different, please replace it with that.
- This command registers Enscape for ArchiCAD for All Users again and output a log file of this in this location:
%LOCALAPPDATA%/Enscape/Logs/Enscape.Installer
## **Deploying Enscape for ArchiCAD for All Users - Prior to 4.0**
---
Selecting “all users” from the installer's options only installs it for users who have already started ArchiCAD at least once.
In order to ensure installation for every new user of a machine, you can do the following:
- [Run a script on any user’s first log on](https://support.microsoft.com/en-us/help/325347/how-to-run-a-logon-script-one-time-when-a-new-user-logs-on-in-windows), and from there, call the Plugin installer like this:
msiexec.exe /q /i Enscape.msi REINSTALL=ArchiCAD
**NOTE:** the /q option for the command to perform a quiet installation.
- Add the registry base key of your ArchiCAD version to the Default User created in the previous step. (This removes the requirement of starting ArchiCAD before installing Enscape.)
Here are some example commands for different ArchiCAD versions:
**REG ADD “HKEY_USERS\Test\Software\GRAPHISOFT\ARCHICAD-64\ARCHICAD-64 21.0.0 USA R1”**
**REG ADD “HKEY_USERS\Test\Software\GRAPHISOFT\ARCHICAD-64\ARCHICAD-64 22.0.0 INT R1”**
**REG ADD “HKEY_USERS\Test\Software\GRAPHISOFT\ARCHICAD\ARCHICAD 23.0.0 USA R1”**
**REG ADD “HKEY_USERS\Test\Software\GRAPHISOFT\ARCHICAD\ARCHICAD 24.0.0 INT R1”**
In the commands “Test” refers to the loaded Hive ([see step 7](https://support.microsoft.com/en-us/help/325347/how-to-run-a-logon-script-one-time-when-a-new-user-logs-on-in-windows)).
The last two parts of the base key depend on your ArchiCAD version, you can look them up at HKEY_CURRENT_USER\Software\GRAPHISOFT for any user that has already started ArchiCAD.
## **Uninstalling Enscape versions prior to 2.6 via Command Line**
---
Uninstalling previous versions of Enscape prior to version 2.6 cannot be done by the MSI installer directly.
Instead, the commands to uninstall Enscape 2.5 can be found in the following registry entries:
**HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Enscape → UninstallString** (if Enscape 2.5 was installed for all users)
**HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Enscape → UninstallString** (if Enscape 2.5 was installed for the current user)
An automatic approach is to read these registry values and execute the commands if they exist.
**NOTE: **This only needs to be performed once. Furthermore, although there is no way to silently uninstall Enscape versions prior to 2.6, you could use a PowerShell script to check for installed versions earlier than 2.6, then open the .msi installer UI to uninstall manually.
## **Converting Settings Presets for Deployment**
---
The only way to deploy the old Settings Presets from versions of Enscape prior to version 2.6 to multiple machines is to install a VM (Virtual Machine) or to install 2.6 on a test machine, run the file conversion, save the new .json formatted files, then redeploy.
## **Settings Deployment**
---
It is possible to deploy settings. Currently available options to deploy are Customization and offline asset and material locations.
To achieve this, you need to create settings on a device that has Enscape installed. Perform the desired changes and close Enscape.
These settings will be now saved in the **settings.json** found in: **C:\Users\%username%\Documents\Enscape\Settings**
To implement Enscape Customization follow the steps listed in the [Customize Enscape page](https://docs-chaos.atlassian.net/wiki/spaces/enscape/pages/841351171).
Find how to use Enscape assets offline on the [Cosmos Asset Library page](https://docs-chaos.atlassian.net/wiki/spaces/enscape/pages/841810013).
Once these actions have been performed, the “settings.json” is ready to be deployed alongside Enscape.
To implement it, after the installation steps in your script, copy this file to the “Settings” folder listed above.
If you need further assistance, please send a message to our [support](https://support.enscape3d.com/hc/en-us).