Decrease BigFix client registration time on Linux

[jgstew]

@cstoneba

I could use the opsites listed in the log file as the data to pre-populate in the config file

yes, if you find the min/max in the log file, you could put that in here:

("[Software\BigFix\EnterpriseClient\Settings\Client\__Group___AdminBy_" & it & "]%0d%0avalue                          = False%0d%0aeffective date                 = Thu,%252001%2520Jan%25201970%252005:23:11%2520-0800") of ("__op_" & it as string) of integers in (MIN,MAX)

@cstoneba

What that just a typo in the query?

It could be, unless the query returns it differently than what should show up in the file, in which case that is just a problem.

When you pre-populate a system like this, then install bigfix, you should be able to check the besclient.config file after the fact and there shouldn’t be any duplication as a result in that file and ideally it would look the same as on a client where you didn’t do the pre-populate, except for the possibility of a few opsites that were sequentially between the min/max but for some reason not in the actions that set them, so there could be a few extra. Though, the ordering of the entries in the file probably won’t match. The ordering shouldn’t matter.

If the query isn’t return what should be pre-populated properly, then there would be duplication.

[cstoneba]

Hi, sending you the log and config files privately, but I didn’t see any changes with pre-populating the opsite values originally found in the client’s logfile.