(imported comment written by Aram_Eblighatian)
Amit,
There is often confusion in this area since the expiration date/time behavior for actions may at first seem strange, but I will try to explain. The first thing to note is that as you suggest, an action’s start/end times are defined as
client local time
. Given this, it is very possible that you might have clients in timezones ‘behind’ that of the main BigFix server. So, actions remain in the ‘Open’ state until all possible client timezones have been met. For example, let’s say your main BigFix server sits in the Eastern Time Zone (GMT -05:00), but you have BigFix clients all over the world, including in the Pacific Time Zone (GMT -08:00). You define an action to end/expire at 11:00 PM client local time. In this case, if the action actually ended/expired at 11:00 PM Eastern (GMT -05:00), then clients in the Pacific Time Zone would have essentially lost 3 hours to execute the action (as it would only be 8:00 PM Pacific). This behavior would be unacceptable. So, since all the action start/end times are defined against the client’s local time, the actions must remain in the ‘Open’ state until all possible time-zones have been met.
Was I able to explain?
Given this, so long as the client’s local time (and timezone) is accurate and appropriate, the actions will NOT execute on the BES Clients after the action’s defined end time.