Get more info from Scheduled Tasks in powershell

user_536262 0
Viewed 2983

Is there a way to view all ScheduledTask properties from PowerShell without having to open up the not so user friendly taskschd.msc:

I manage to create the job fine with New-ScheduledTask and Register-ScheduledTask, but I'm unable to view the parameters like Action, Trigger, Principal and Settings, that I used in New-ScheduledTask

Below is what I manage to get:

Get-ScheduledTask -TaskName "test22 BAM-AT" -Verbose

TaskPath                                       TaskName                          State
--------                                       --------                          -----
\                                              test22 BAM-AT                     Ready


Get-ScheduledTaskInfo -TaskName "test22 BAM-AT" -Verbose


LastRunTime        : 2/23/2021 1:44:44 PM
LastTaskResult     : 0
NextRunTime        : 2/23/2021 4:00:00 PM
NumberOfMissedRuns : 0
TaskName           : test22 BAM-AT
TaskPath           :
PSComputerName     :
scheduled-tasks powershell windows
1 Answers

The Cim base ScheduledTasks module doesn't expose that level of detail up front. However, you can use another of it's cmdlets Export-ScheduledTask to get the XML task definition and parse it like an object.

Example:

$TaskXML = [XML]((Get-ScheduledTask)[0] |Export-ScheduledTask)
$TaskXML.Task.Triggers

Obviously you may have to poke around to extract the information you want etc...

Export-ScheduledTask returns all the XML you would need to import the task on another system, so it should have all the details, it's just a matter of extracting the XML.

Update Addressing Comments:

I apparently didn't realize there's more information returned and accessible from Get-ScheduledTask. However, Select-Object (select * above) isn't needed to access that information. Doing so will dehydrate the returned object, which may affect secondary use of it. The objects returned after Select are [PSCustomObjects] as opposed to a typical [CimInstance].

Thanks to @CraftyB's comments, here are some examples without the unnecessary Select-Object:

(ScheduledTask -TaskName "test22 BAM-AT").Actions

OR:

(ScheduledTask -TaskName "test22 BAM-AT").Triggers

Reference properties as needed.

Without more work, it is unclear to me if there are advantages or disadvantages to exporting the XML versus just referencing the properties. It's possible information is available in one approach that isn't in another.

user_47492640
Related