(imported topic written by Metapro91)
I’m having issues with computer groups taking a long while to update: I’ve got computer groups built based off of other groups (for nesting purposes) and it is taking a very long time for changes to take effect without refreshing the endpoints and/or the group itself. Any advice?
(imported comment written by MrFixit)
We nest groups in a similar fashion and would be interested as well if there was something that can be set for the client to do that more often.
What I’ve done to work around this is to have all of my groups in a custom site, and that is all I have in that custom site asside of a single task which contains a single line in it: “notify client forceRefresh”. I can issue that task against any computer that I want to re-evaluate the groups. From what I’ve seen in the debug log is that the client will immediately re-evaluate everything in that site, so if you have lots of other content including analysis and properties in that same site those will also be triggered immediately for evaluation even if a property was set to once a week.
-Gary
(imported comment written by Metapro91)
Thanks Gary, I’ll try making custom copies of our existing groups and adding them to a new site reserved just for computer groups. I have a feeling that may help. Can anyone verify that the force client fresh will only recheck relevance that is part of that specific site, or will it also evaluate all other possible relevance that’s included in other sites? Additionally, are computer groups in sites evaluated at the every report time period (default is 15 minutes I believe) and is there a way to modify that period just for a specific site and not for all other sites?
(imported comment written by Metapro91)
I just found this, which gives a bit of insight on the force refresh command: http://forum.bigfix.com/viewtopic.php?id=5423