Taking Automation to Task
summary
Windows Task Scheduler work is concrete: PowerShell uses the ScheduledTasks v1 cmdlets but they omit triggers and settings (no monthly trigger via cmdlets), UAC hides admin-only tasks, and the default execution time limit defaults to three days which breaks short jobs. Demos create tasks with repetition intervals, an infinite-loop “Chad” to show killing by time limit, and a scheduled enabler for history because Task history is disabled by default and lives in Microsoft-Windows-TaskScheduler/Operational with event IDs like 107 100 102 129 and 200s. Full trigger info requires exporting task XML so use XML to see full triggers and chart actual start/end durations.
AI-written summary · about
chapters (4)
related talks
26mCommSec D2 - Hiding Tasks via Hardware Task Switching
50mAutomating security monitoring
28mSecure your cloud automation
43mHow to Tame the Event Log Beast
57mSecuring PowerShell: Hands-On Lab
25mWindows 11 At Your Service
47mAMSI: How Windows 10 Plans to Stop Script-Based Attacks and How Well It Does It
50mAutomated Discovery Of Logical Priv. Esc. Bugs In Win10