Skip to content

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 macOS 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 user 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.

Setting Config Values

Configuration values are set via plist settings. Each setting is specified by a write command:

User-scope setting:

defaults write "com.teradici.Teradici PCoIP Client" <Key> <value>

System-scope setting:

sudo defaults write "/Library/Preferences/com.teradici.Teradici PCoIP Client.plist" <Key> <value>

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:

defaults write "com.teradici.Teradici PCoIP Client" localtermination_black_list "18a5,0302"

Config File Locations

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

Scope Location
System /Library/Preferences/com.teradici.Teradici PCoIP Client.plist
User ~/Library/Preferences/com.teradici.Teradici PCoIP Client.plist