Upon startup of your used CAD software, the license code in the registry key will automatically be applied.

NOTE: for this process you will need a separate Enscape License Key which you will need to directly request from us. To do this, please contact our support.

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, please refer to this article. If you want to read the Enscape version automatically, then please refer to this article.

If you’d like to deploy your license automatically so that the Enscape user doesn’t have to enter the code manually when starting Enscape for the first time, simply follow these steps:

Here’s a very simple deployment script which 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

Note: If you want your license to be deployed on each start up (for each user) without being deleted, name it “License-Persistent.txt”, and place it into “%ProgramData%\Enscape”.

To suppress Enscape Update Notifications, Graphics Card Driver warnings, and the First Steps window you can 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.

NOTE: the implementation for suppressing these popup notifications is currently subject to change.

Selecting “all users” from the installers options will only install 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:

1. Run a script on any user’s first log on 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.

2. 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 version:

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).
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.

It is worth noting that 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)

So, an automatic approach would be 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 possible way to uninstall Enscape versions prior to 2.6 silently and without user interaction, you could use a PowerShell script that would check for versions previous to 2.6 that are installed, and this would then open the .msi installer UI to manually uninstall.

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.

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 this article.

To enable Offline Enscape Assets follow the steps detailed here.

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.