July 7th 2017 - 2:00 PM EST - BigFix Best Practices Webinar: Top 5 actions to improve your Bigfix performance!

Top 5 actions to improve your Bigfix performance!
July 7th 2017 - 2:00 PM EST
Registration: https://ibm.biz/BigFixWebinar

6 Likes

Here is the presentation from today’s call. Thanks for joining!
BigFixBestPracticesWebinar_20170707.pdf (810.9 KB)

4 Likes

One of the things mentioned during the presentation is to manage old baselines so they don’t effect the client eval loop on an ongoing basis when they are no longer needed.

The quickest way to do that is to set the applicability to false:

If you still want to keep it around for reference in the console, you could create a copy in a site that 0 computer’s subscribe to and delete the original, though that new copy will not be connected to the actions that were created, so there is not a large benefit to doing that and you might be better off just exporting it for archival and deleting it from the console if you want to keep it around for historical reasons.

Another thing worth mentioning… if not using SSDs for the BigFix database, then you might try changing the FillDB batch rate, which could improve performance: https://www.ibm.com/support/knowledgecenter/en/SSARLZ_9.2.0/com.ibm.tivoli.tem.doc_9.2/Platform/Config/c_filldb_batch_rate.html

It is definitely worthwhile to check the performance before and after while the system is under load to make sure it is an improvement.

1 Like

I also liked this tip:

Disable the Windows Indexing Service and compression on the BES Server file structure

I wonder if there is a fixlet to do this already somewhere.

unique values of ( (preceding text of first "\[" of it & following text of first "]" of it) | it) of following texts of firsts "file:///" of (it as string as trimmed string) of values "URL" of keys of keys "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search\CrawlScopeManager\Windows\SystemIndex\WorkingSetRules" of (x32 registries; x64 registries)
1 Like