1E Client settings

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

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.

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:

• 1E Client

• 1E client features

• Shopping client module (only available on Windows OS)

To change the logging level, please refer to LoggingLevel in the 1E.Client.CONF file.

The following are not configurable in this version:

• Maximum size of 5MB

• 5 rollover files numbered 1 (newest) to 5 (oldest) with the rollover number included as n.log

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 Content Distribution client settings, PXE Everywhere Agent settings, and Wakeup client settings. Shopping 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.

The following table shows the OS-specific defaults used if the setting is omitted, blank, or invalid. The default is recommended.

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.

This setting allows you to set a custom shell executable for the lookup during the masquerading process, used to launch the 1E Client UI on a logged-on user's session.

The possible values are:

• Auto ( Default) - Looks up the shell executable by reading the registry value at HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell. By default, the value stored at this registry path is explorer.exe

  This value only takes into account the custom shell executables set at the machine level and not the individual users.

• Name of the custom shell executable. Make sure to only use the name of the executable and not the complete executable path (for example cmd.exe not C:\Windows\System32\cmd.exe)

Enables automatic client certificate provisioning on the device.

The URL where new certificate provisioning requests are submitted can be overridden using this setting.

When the 1E Client submits a certificate signing request to auto-provision a client certificate, it will then not re-submit another certificate signing request for this many hours.

When the 1E Client checks for a usable client certificate for connection to the 1E Platform, it will ensure that any existing certificates are valid for at least this many days in the future.