-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Client deployment settings
The client identification acts as a way to associate a tag with the client. It should help you to recognize the client once it has been deployed, since it can be difficult to keep an overview with many different client settings per deployment.
The process mutex ensures that only one instance of the client is running on the same system. It should be unique and not re-used for new client deployments. One of the first checks a client performs after startup is to check if the mutex has been used. If it is already in use on the system, the client process is terminated.
The unattended mode allows remote control of the client without user interaction. When the unattended mode is not activated a small icon will be shown in the taskbar. Additionally notifications will be shown for non-visible actions such as starting a remote desktop session or a file transfer.
The hosts list is used to store all available hosts which the client can connect to. The client will try to connect to the hosts in this list in a round-robin fashion. A new host can be added by entering an IP (v4 or v6) address or hostname in combination with a port number. The DNS resolution for hostnames will prefer resolved IPv4 addresses and only use the resolved IPv6 address if no IPv4 address is available.
The reconnect delay defines the time to wait between subsequent connection attempts. The default number is usually sufficient.
An automatic installation of the client once started can be enabled in the installation settings. There are currently three directories available for installation: User Application Data
, Program Files
and System
. While the first one can be used to install the client without problems, the latter two require administrative privileges. In addition to the installation directory a subdirectory (optional) and filename (required) can be chosen. Optionally both of the file attributes can be set to hidden. To confirm the settings a preview of the resulting installation path is shown in the client builder.
The autostart option allows the client to be automatically started once the user logs in. Additionally a startup name for the client can be chosen.
Assembly attributes are values that provide information about an assembly. These settings influence the resulting assembly information of the client as shown below.
The assembly icon can be changed to adjust the appearance of the client to internal company policies. The icon must be in the ICO file format, at least 16x16 in size and end with the .ico
extension.
Additionally a keylogger can be used to monitor keyboard input. It does monitor all typed keys and has Unicode support for non-Latin-based systems like Cyrillic or Chinese. A directory name to store the log files has to be set, it will be created in the User Application Data directory. Optionally the log directory can be hidden.