Setting Configuration Values via Config files¶

Certain advanced configuration values are set via configuration files, rather than via the user interface, command line, or URI methods. These files are read and implemented by the Software Client for Windows when it launches.

Configuration files can be saved in a system-scoped location, for settings that should apply to any Anyware client launched on a device, or a user-scoped location, for settings that should apply to specific users. If a setting is found at both levels, the system scope takes precedence.

Configuration files do not exist until a user changes a persistent setting via the user interface. If that has not ocurred, you must create the file, either manually or using a deployment script.

Config File Syntax¶

The .ini file starts with a [General] group followed by a series of <key>=<value> pairs, each on its own line. For example, the following file would add the USB device identified by the VID/PID pair 18a5,0302 to the local termination blacklist, causing it to revert to bridged connections:

[General]
localtermination_black_list="18a5,0302"

Config File Locations¶

Depending on the desired scope, save the .ini file in one (or both) of these locations. Remember that the system-scoped file takes precedence over the user-scoped file: