How to ensure client receives ForceRefresh

[vk.khurava]

Ok so planman is kind of your automation tool to push scheduled jobs in BigFix but Repeatedly sending Force Refresh commands to clients, regardless of conditions, can lead to significant issues over time,

Force Refresh command instructs the BigFix client on endpoints to immediately re-evaluate its relevance, re-send its current status to the BigFix server, and reapply relevant actions. Issuing Force Refresh commands to a large number of clients simultaneously can lead to several problems like network spikes, server overload, client performance impact, interference with normal client operations.

You must coordinate with the administrator of your Planman tool and request that they schedule the actions ahead of the maintenance window, maintaining the start and end times in accordance with the actual deployment window.

I’m not sure what strategy Planman is using, but if they are using XML Push to schedule an action, they must update the fields below before using XML Push.

<HasStartTime>true</HasStartTime>
<StartDateTimeLocalOffset>**Desired Timing**</StartDateTimeLocalOffset>
<HasEndTime>true</HasEndTime>
<EndDateTimeLocalOffset>**Desired Timing**</EndDateTimeLocalOffset>

In case of issue with start/end time calculation, you can take reference from below post.

How to get the difference between two date/times, and convert it to action XML scheduling format

Here is a new method I just came up with once I discovered the “Format” inspector: https://bigfix.me/relevance/details/3008616 Q: ( format "P{0}DT{1}H{2}M{3}S" + it / (1*day) of it + it mod (1*day) / (1*hour) + it mod (1*hour) / (1*minute) + it mod (1*minute) / (1*second) ) of ("26 days, 18:36:56" as time interval) A: P26DT18H36M56S This relevance converts a time interval object into a formatted string for use in action start & end times, which are in the StartDateTimeLocalOffset or EndDateTim…