What is the format for writing comments in the clientsettings.cfg and besclient.config files?
Most languages have a format or syntax for inserting comments into their files.
C++ has /* comment comment comment*/
LUA has –comment comment comment
DOS BATCH has REM comment
XML has <!–comment comment comment–>
How do we add comments to these files used by the BigFix installers?
Thanks!
I don’t believe we support writing comments in the Settings config files.
May I ask the use case for this request? Note that generally, these files are not edited manually, but centrally managed via the BigFix Console.
Waittaminute. So somehow I can generate these files or install packages via BigFix Console? Where would I find this Fixlet/Task/menu option/etc?
We’ve been updating them by hand since we have custom attributes to set.
My whole team is pretty new to BF. We can’t even think of where to look to do something like this, since we’re only aware of things you can do AFTER the Agent is installed.
Normally, one would create a task to update client settings to your standards (report time, cpu usage, etc.) and issue that as a Policy Action.
The only things that are commonly put into a clientsettings.cfg are failover relay settings (so the client can perform an initial registration without connecting to the root server), and possibly some custom tagging (so you can assign a customer or department by handing out different installer packages).
What are you trying to accomplish in your clientsettings.cfg file?
Thanks guys, it’s very helpful to hear what’s normal usage.
We have a Relay in each remote location.
We assign Primary and Secondary relays (the __RelayServer1 and __RelayServer2, and IP:http://1.2.3.4/bfmirror/downloads/ that seem obligatory), as well as some custom tags to define the POC for the the location (like _Location, _SysAdmin, _SysAdmin_Email, _SysAdmin_Phone etc, along with some obscure ones like _var1 forced on us by company policy).
These are pretty static for each location, which is why I set them in a clientsettings.cfg file. That way I can zip up the entire install package (including the Masthead), send it to my remote admins (who are often just “that guy who’s good with computers” at the location), and they just unzip-and-run as part of their standup process.
What I’m trying to accomplish is to annotate the config file so that 1.) the next new guy can open the config file and know what each custom tag/set of tags is for, and 2.) the remote admins can update those static settings on their own, instead of waiting on us at HQ to get around to it.