1E Client configuration settings and installer properties
Settings are available in the 1E Client configuration file, with details of which settings are mandatory or optional during installation, and which settings can be re-configured post-installation.
1E Client installers include a template configuration file that contains the more important settings with default values that match hard-coded default values. The configuration file is updated during installation and named 1E.Client.conf in the installation folder along with the 1E Client executable.
After installation, configuration file settings can be managed using 1E Client command-line parameters, Endpoint Troubleshooting configuration instructions, Endpoint Automation policies, Configuration Manager baselines, or other means. Registry settings can also be managed by Windows Group Policy.
1E Client installer zips
1E Client installation files are available for download from the 1E Support Portal. The following installer zips are available and contain the following files, where 8.0.x.xxx is a specific build:
1EClient.v8.0.x.xxx.zip |
1EClient_Non-Windows.v8.x.x.xxx.zip |
---|---|
|
|
Please refer to Supported platforms for details of supported OS versions and their prerequisites.
Deploying the 1E Client
Windows computers
When deploying 1E Client to Windows devices you can install using the MSI interactively but this only allows you to specify some configuration settings. You can configure these and some other settings using installer properties on the command line or in one or more MST transform files.
The Client Deployment Assistant is designed to help install Windows versions of 1E Client and other 1E agents using Configuration Manager. It includes template transform files for each combination of client/agent for 32 and 64-bit platforms, and automatically creates collections and deployments in Configuration Manager so that you only need to populate the collections. Refer to Client Deployment Assistant.
Please refer to:
Non-Windows devices
Please refer to:
1E Client settings
Configuration settings can be set during or after installation, depending on the platform, as described in the table below. Installer command-lines are described in Deploying 1E Client on Windows.
Platform |
Notes |
---|---|
Windows |
|
Linux |
|
Mac and Solaris |
|
The following applies to all configuration settings that are stored in the 1E Client configuration file:
-
They can be reconfigured after installation either manually or as described in 1E Client command-line parameters.
-
Property names and values are not case-sensitive, but the convention is to store them in mixed-case.
-
If you omit a mandatory property or its value, the 1E Client will not start.
-
If you omit an optional property or its value, the 1E Client will use the default value instead.
1E Client configuration file location and name
The 1E Client is controlled via the 1E Client configuration file 1E.Client.conf which resides in the installation folder along with the 1E Client executable.
The default installation location used for the different OS supported by the 1E Client are given in the following table:
OS |
Default install location |
---|---|
Windows |
%ProgramFiles%\1E\Client |
Linux and Solaris |
/etc/1E/Client |
Mac |
'/Library/Application Support/1E/Client' |
The configuration file uses ASCII encoding.
A comment line starts with the # symbol.
Installer properties and configuration settings
The following are alphabetical lists of all installer properties and configuration settings for 1E Client modules and features.
Those installer properties listed in mixed case are stored in the 1E Client configuration file, and those listed in UPPERCASE are stored in the registry. Where relevant, the locations of Windows registry settings are provided.
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.