fedora-intune: take the first Defender health snapshot right after boot
Build containers / fedora-cosmic (44) (pull_request) Canceled after 0s
Build containers / fedora-cosmic (rawhide) (pull_request) Canceled after 0s
Build containers / fedora-remote (44) (pull_request) Canceled after 0s
Build containers / fedora-intune (44) (pull_request) Canceled after 0s
Build containers / Compute changes (pull_request) Canceled after 12s
Build containers / Prune old releases and tags (pull_request) Skipped
Build containers / fedora-cosmic (44) (pull_request) Canceled after 0s
Build containers / fedora-cosmic (rawhide) (pull_request) Canceled after 0s
Build containers / fedora-remote (44) (pull_request) Canceled after 0s
Build containers / fedora-intune (44) (pull_request) Canceled after 0s
Build containers / Compute changes (pull_request) Canceled after 12s
Build containers / Prune old releases and tags (pull_request) Skipped
The first snapshot came 2 minutes after boot, so the compliance check at the first sign-in found none, fell back to mdatp (which won't answer it) and reported Defender as not running. Himmelblau then doesn't check again for 8 hours. Start the timer 20 seconds after boot, and wait up to 2 minutes for the daemon to answer so that snapshot isn't a false "not running". The timer runs it in the background, so boot isn't held up. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
811025773e
commit
49b360dffa
2 files changed
+10
-1
No files matched your search
@@ -2,7 +2,9 @@
|
||||
Description=Save Microsoft Defender health every 5 minutes
|
||||
|
||||
[Timer]
|
||||
OnBootSec=2min
|
||||
# Early, so the compliance check at the first sign-in after boot finds a
|
||||
# snapshot; Himmelblau doesn't check again for 8 hours.
|
||||
OnBootSec=20s
|
||||
OnUnitActiveSec=5min
|
||||
|
||||
[Install]
|
||||
|
||||
Reference in new issue
Block a user