So having worked with the Task Scheduler Library in Windows over the last few weeks it's a real problem area of Windows
I've already mentioned the issue that deprecated features still appear in the user interface.
The next area to note is that the Get-ScheduledTask PowerShell cmdlet is not fully functional. If you create a scheduled task with a Monthly trigger this cannot be read using the cmdlet.
Instead of a fully fledge object like you would receive from the other trigger types you instead receive the base object.
MSFT_TaskTrigger
Enabled : True
EndBoundary :
ExecutionTimeLimit :
Id :
Repetition : MSFT_TaskRepetitionPattern
StartBoundary : 2017-10-18T19:31:14
PSComputerName :
CimClass : Root/Microsoft/Windows/TaskScheduler:MSFT_TaskTrigger
CimInstanceProperties : {Enabled, EndBoundary, ExecutionTimeLimit, Id...}
CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties
I've already mentioned the issue that deprecated features still appear in the user interface.
The next area to note is that the Get-ScheduledTask PowerShell cmdlet is not fully functional. If you create a scheduled task with a Monthly trigger this cannot be read using the cmdlet.
Instead of a fully fledge object like you would receive from the other trigger types you instead receive the base object.
MSFT_TaskTrigger
Enabled : True
EndBoundary :
ExecutionTimeLimit :
Id :
Repetition : MSFT_TaskRepetitionPattern
StartBoundary : 2017-10-18T19:31:14
PSComputerName :
CimClass : Root/Microsoft/Windows/TaskScheduler:MSFT_TaskTrigger
CimInstanceProperties : {Enabled, EndBoundary, ExecutionTimeLimit, Id...}
CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties