###UTC time zone setting can help
When creating schedule, by default it use “Client Time” as time zone settings, by design, the default time to create the Multiple Action Group is UTC +14. One thing regarding +14 time zone is that this is the earliest time zone on earth, meaning that areas in this zone are the first to see a new day, so it will ensure the client time apply to all computers on earth for that day.
So in this case, it’s hard to set schedule in the same day.
To verify schedule behavior, I am thinking maybe you can try UTC as time zone settings. Say like currently I am in +1 time zone and now it’s 3:50 pm, then you try to create policy schedule, you can set schedule time as 3 PM UTC time, so the schedule will be run after 10 mins.
###What happened for that schedule?
We are thinking to add one UI to display events for certain schedules, this feature is planned in roadmap. But for now, enable verbose log for WebUI is needed to see what happened for certain behaviors in detail.
Patch Policies App Logs
– C:\Program Files (x86)\BigFix Enterprise\BES WebUI\WebUI\logs\autopatch.log
– Default is not Verbose. To enable verbose logging:
- Edit the computer setting of WebUI Service and add a new setting: "_WebUIAppEnv_DEBUG“
- The value is “bf*“ (bf* will enable all verbose log for WebUI Apps)
- Restart WebUI Service
Sometime schedule will be executed but no Multiple Action Group will be created in Bigfix Console, one reason can be no relevant patches, after verbose mode enabled and you can see log like below:
message: 'There is no patches included in this preview, will not create MAG!!!' }
To verify if there is any patch relevant to some devices, you can check Applicable Patches in “policy detail view” -> “patches” tab.
Hope the information helps and feel free to let us know in case you have further questions.