Daylight Saving with new Patch policy Custom Timezone

1

Hello,

With the new custom timezone for patch policy schedules ( BigFix Insights and Patch Policy new release available - December 2025 ), is it right to assume that GMT-05:00 for Eastern timezone will automatically get converted to GMT-04:00 on March 8th and will go back to GMT-05:00 when daylight saving time ends on November 1st?

Thanks in advance for any feedback.

2

Hi Jan, short answer is no, your assumption is wrong.
The new functionality is meant to avoid any time conversion from UTC when you set the time of the Patch Policy Schedule. This value does not consider the time shift.
If you need to run the Policy at a specific time on each endpoint, you can use the Client Time option.
If you need to run the policy on a fixed time on all your endpoints (no matter where they are located), you can set the time using the UTC of a different time zone. If I am in Italy and I want to run the policy at 6 pm Italy time, I can use 17:00 UTC time or 18:00 UTC+1 time. But if on 8th March my country move to a different offset, this is not automatically refreshed on the Patch Policy Schedule, that will run still at 18:00 UTC +1 (or 17:00 UTC).

1 Like
3

Hello @ADL ,

Thanks for clarifying the new feature.

Well, our main problem is that our servers have different timezones but they are scheduled all in Eastern time. Before the new feature, what we use is UTC then we would convert back and forth the start time to UTC -4 and UTC -5 due to daylight saving time. We have the option to to convert it to client local time but we will still have to convert the servers that have different timezones to Eastern timezone equivalent and that will require multiple schedules. So we were looking for a way that will automatically convert it from/to daylight saving time.

But I guess this feature could also be helpful since we can just toggle the timezone from/to -4 and -5 instead of changing the start time UTC equivalent.

What I would look forward to is the Frequency column showing the selected timezone whether it is “UTC -4” or “UTC -5” so we can easily be reminded that we need to change it instead of just displaying “Custom Time.” This would avoid having the need for users to go inside each and every schedule to confirm what custom timezone they have selected.

image

Thanks again Alessandro. Nice speaking with you again :slight_smile: