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 root directory under which the Client will create the DBs and Persist subfolders and hence the locations of the databases and persistent storage within the local file system. If the specified directory doesn't exist it will be created. Local System (SYSTEM) requires at least modify rights on the directory. If the specified directory is invalid, or cannot be used, the 1E Client will log an error and refuse to start. For example if the directory name is a file, non-existent volume, or SYSTEM does not have permission .
If not specified, the default is the %ALLUSERSPROFILE%\1E\Client directory. This is also the default location of client log files, which are not affected by this setting. The location and name of the 1E Client log file is determined by the LogPath setting. Please refer to Log files for details of other client log files.
This setting is for Windows only. It is ignored on non-Windows platforms, without warnings or errors logged.
Do not use this setting unless required, for example if security software unavoidably conflicts with 1E Client.
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
1E Client logs on macOS
/Library/Logs/1E.Client.Daemon.log (shows any service start errors)
/Library/Logs/1E.Client.log (shows the current operation of the 1E Client)
1E Client logs on other non-Windows platforms
1E Client logs on Android
The LogPath setting is stored in the 1E.Client.Conf file and determines the full path and filename of the 1E Client log file.
The 1E Client log is shared by:
To change the logging level, please refer to LoggingLevel in the 1E.Client.CONF file.
The following are not configurable in this version:
The LogPath setting is not used by Nomad, PXE Everywhere, 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, PXE Everywhere Agent settings, and WakeUp client settings. Shopping WSA also has its own configuration file. Please refer to Log files for more details.
The TemporaryDirectory setting is stored in the 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:
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
Subprocesses invoked by the 1E Client, such as commands, PowerShell scripts, etc. create their temporary files directly under the specified path.
This setting was introduced in a v5.0 hotfix.