How can I deploy the agent so that it starts with specific settings?
If you want to deploy an agent so that it starts with specific client settings, add a file "clientsettings.cfg" into the installer folder, and the installer will put the settings in place when the agent is installed.
Resolving the problem
You can always use the TEM Console to set agent settings centrally, but if you want to deploy an agent so that it starts with specific client settings, you can add a file "clientsettings.cfg" into the installer folder, and the installer will put the settings in place when the agent is installed. This technique can be used to set the initial relay of the agent, to set the autoselection method, to set initial bandwidth throttling usage, and so on.
The file "clientsettings.cfg" will need to be a text file with each line containing a "setting name"=setting value pair. For example, the clientsettings.cfg file could contain the following lines:
This particular example would cause the agent to install with settings to use double the average CPU usage and to throttle bandwidth to 9 kb/s (more info about client settings available at: http://support.bigfix.com/bes/misc/besconfigsettings.html))
- This clientsettings.cfg only works for Windows and Mac computers. Unix TEM Clients use the file /var/opt/BESClient/besclient.config to store the agent settings and you can modify it so it contains the desired settings at install time.
- The clientsettings.cfg only works with the setup.exe based client installer (and the Mac installer .dmg) and does not work with the Windows msi based client installer
- The clientsettings.cfg only works with Tivoli Endpoint Manager version 7.0 and higher (more info about setting relay-specific settings in version 6.0 can be found at http://support.bigfix.com/cgi-bin/kbdirect.pl?id=244.
Note: Beginning with IEM 9.0 the directory /etc/opt/BESClient/ is not automatically created by the installer. If it does not exist, you will need to manually create this directory.
Translate this page: