Installer and configuration settings for 1E Client which affect all client features and modules.

Installer properties:

Configuration file settings:

1E Client settings

You must use UPPERCASE when specifying the name of any installer property in a mst transform file, and preferably when including them in a msiexec command-line.

Names of settings stored in the configuration file are not case-sensitive. Setting names stored in the registry may be case-sensitive and should be specified as shown.

Settings that have numeric values must be set using decimal integers, unless otherwise specified.




Sets the installation folder.

This value is not stored in the 1E Client configuration file.

This value is stored as InstallationDirectory in the Windows registry under HKLM\SOFTWARE\1E\Client\ and must not be changed.

Some client modules that run on Windows store their registry settings under their own keys in HKLM\SOFTWARE\1E.

This installer property is for Windows only.


1E Client logs on Windows


LOGPATH is not used by Nomad and WakeUp client modules. For a fresh install they use their defaults, and for upgrades they re-use what is in their registry. In each case these can be over-ridden by installer properties described in Nomad client settings and WakeUp client settings. Shopping WSA uses its own configuration file. Please refer to Log files for more details.



The TemporaryDirectory setting is stored in the /span> 1E.Client.Conf file specifying the directory path below which the 1E Client and its subprocesses will create temporary files and subdirectories.

Using this setting to specify a non-default value is only necessary if the OS default location is not suitable. For example, some security software forbids scripts being run from certain locations. Or you want to simplify configuration of Windows anti-virus and malware software to the same location as 1E logfiles.

The specified directory:

  • Must be an absolute path appropriate for the OS
  • Must already exist - it will not be created
  • Must be writable by the 1E Client (SYSTEM on Windows, root on Linux)

If any of these criteria is not satisfied then the 1E Client and subprocess falls back to using the default temporary directory.

If the value is validated successfully then environment variables are set so that subprocesses inherit the same temporary directory.

The path can only contain ASCII characters but that is not validated. Unicode characters are not supported.

The 1E Client itself creates a subdirectory under the specified path called 1e.client  which it uses for its own temporary files and directories.

Subprocesses invoked by the 1E Client, such as commands, PowerShell scripts, etc. create their temporary files directly under the specified path.

This setting is new in Tachyon v5.1 but has been backported to v5.0 in a hotfix.