On the Job: Putting PowerShell Scheduled Jobs to Work
summary
Shows how PowerShell Scheduled Jobs create scheduled tasks that run even when no one is logged on, using get-scheduledjob / start-job and the ScheduledTasks module (Windows 8 / Server 2012) for richer querying. Notes an ongoing bug: task terminated by the user when creating jobs under alternate credentials, advises to create jobs with the same credential to simplify result access, explains jobs and results live under AppData and that default max result count 32 can flood get-job output.
AI-written summary · about
chapters (35)
- 0:00Introduction
- 1:15PowerShell Scheduled Jobs
- 2:13Scheduled Task Manager
- 3:19Scenarios
- 4:13Youre not limited
- 5:17Test
- 7:29Job Definition
- 8:26Job Conventions
- 10:00Task Scheduler Bug
- 11:11Check Job Status
- 12:43Export Import Scheduled Jobs
- 13:23Demo
- 14:32Create a job trigger
- 15:37Create a schedule job option
- 16:17Schedule job results
- 17:14Register a Scheduled Job
- 19:19Access Network Resources
- 20:27Troubleshooting
- 22:00Scheduled Task Service
- 24:04Import Scheduled Task Service
- 26:35Get Scheduled Tasks
- 28:41Get Scheduled Task
- 29:01Report
- 29:43View
- 31:09Schedule Tools
- 33:00Create XML File
- 35:28Question Time
- 37:30Some jobs are good
- 40:00Schedule a service
- 41:12Scheduled tasks
- 42:24Scheduled jobs
- 42:57One more work
- 44:35Microsoft
- 45:07Hit Last Job Results
- 45:54Job Results
related talks
41mTaskJob: Manage .NET Tasks as PowerShell Jobs!
01h 47mBuilding PowerShell Applications that Operate on a Planetary Scale
39mPowerShell with SQL Statement Data Gathering
41mConfiguring Your PowerShell Workflow Environment
50mJenkins - User Interface for your Powershell tasks
34mWhip Your Scripts into Shape: Optimizing PowerShell for Speed
44mContinuously deploying SQL code using Powershell
52mPowerShell for SharePoint Online - How DevOps in making SharePoint Admins feel ..