Check the task action
Use absolute paths for PowerShell and script files. Avoid relying on the current working directory.
Check the run account
Confirm the account has Log on as a batch job rights where required and access to the script, network paths, certificates and output folders.
Use explicit PowerShell arguments
A typical action uses powershell.exe -NoProfile -ExecutionPolicy Bypass -File C:\Path\script.ps1 where appropriate for your policy.
Check mapped drives
Scheduled tasks usually should not depend on interactive mapped drives. Use UNC paths or authenticate to the required resource explicitly.
Review task history
Enable Task Scheduler history and check Last Run Result. Also capture PowerShell transcript or custom logs.
Test in the same context
Run the task manually from Task Scheduler and compare the environment, permissions and paths with the interactive session.
Explore more TechRunbook guides
Browse practical troubleshooting guides, PowerShell scripts, checklists and infrastructure resources for your environment.
Browse all articles →