Skip to content

Conversation

@KnifMelti
Copy link
Contributor

@KnifMelti KnifMelti commented May 9, 2025

Proposed Changes

In the original script, a completely new trigger is created every time WAU-Policies runs.
For interval-based schedules, this means that the starting point for the interval is continuously reset to "now".
Since WAU-Policies runs daily at 06:00, these tasks will never actually execute - they are constantly pushed forward in time to the next interval.
This is why a solution that only updates triggers when the configuration has actually changed is necessary for all scheduling types with intervals.

Related Issues

Closes #933

@KnifMelti
Copy link
Contributor Author

KnifMelti commented May 9, 2025

In a coming MSI installation, we could trigger a run of WAU-Policies at the end to pick up the settings from GPO if enabled instead of letting it wait until the next morning @Romanitho

@Romanitho Romanitho changed the title Check if changed [GPO] Check if config changed before applying changes May 12, 2025
@Romanitho Romanitho merged commit 14c79f5 into Romanitho:main May 12, 2025
6 checks passed
@KnifMelti KnifMelti deleted the hotfix/wau-policies branch May 12, 2025 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: GPO WAU-Policies

2 participants