Not all settings can be hit using that cmdlet or others like it. These are just XML files.
Get-ChildItem -Path 'C:\Windows\System32\Tasks'
You can manually create a task on a single server then Export it save and copy manually or directly write it to the others and just register it there.
Export-ScheduledTask 'TestTask' |
out-file '\\TargetServer\c$\public\TestTask.xml'
Invoke-Command -ComputerName 'TargetServer' -ScriptBlock {
Register-ScheduledTask -Xml (Get-Content 'C:\Users\public\TestTask.xml' | out-string) -TaskName 'TestTask'
}
… or you can script it, but you have to manipulate the XML file.
For Example:
# Create your task
$A = New-ScheduledTaskAction –Execute 'powershell' -Argument 'Hello, from task scheduler'
$T = New-ScheduledTaskTrigger -Weekly -WeeksInterval 1 -DaysOfWeek Monday,Tuesday,Wednesday,Thursday,Friday -At 8am
$S = New-ScheduledTaskSettingsSet
$D = New-ScheduledTask -Action $A -Trigger $T -Settings $S
$Task = Register-ScheduledTask 'TestTask' -InputObject $D
# View the created task XML
Get-Content -Path 'C:\Windows\System32\Tasks\TestTask' | Out-GridView
# capture the task to work with
$Task = Get-ScheduledTask -TaskName 'TestTask'
# Step through the task information.
$Task | Select *
State : Ready
Actions : {MSFT_TaskExecAction}
Author :
Date :
Description :
Documentation :
Principal : MSFT_TaskPrincipal2
SecurityDescriptor :
Settings : MSFT_TaskSettings3
Source :
TaskName : TestTask
TaskPath : \
Triggers : {MSFT_TaskWeeklyTrigger}
URI :
Version :
PSComputerName :
CimClass : Root/Microsoft/Windows/TaskScheduler:MSFT_ScheduledTask
CimInstanceProperties : {Actions, Author, Date, Description...}
CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties
$ScheduleTaskKeys =
'State',
'Actions',
'Author',
'Date',
'Description',
'Documentation',
'Principal',
'SecurityDescriptor',
'Settings',
'Source',
'TaskName',
'TaskPath',
'Triggers',
'URI',
'Version',
'PSComputerName'
ForEach($TaskKey in $ScheduleTaskKeys)
{$Task.$TaskKey | Format-List -Force}
# View as JSON
$Task | ConvertTo-Json
# Example XML config
# Configuring triggers
$Task.Triggers | Format-List -Force
Enabled : True
EndBoundary :
ExecutionTimeLimit :
Id :
Repetition : MSFT_TaskRepetitionPattern
StartBoundary : 2018-11-10T08:00:00
DaysOfWeek : 62
RandomDelay : P0DT0H0M0S
WeeksInterval : 1
PSComputerName :
$Task.Triggers.Repetition | Format-List * -Force
Duration :
Interval :
StopAtDurationEnd : False
PSComputerName :
CimClass : Root/Microsoft/Windows/TaskScheduler:MSFT_TaskRepetitionPattern
CimInstanceProperties : {Duration, Interval, StopAtDurationEnd}
CimSystemProperties : Microsoft.Management.In
# Modify the trigger repetition settings, which cannot be done via the native cmdlet
$Task.Triggers.Repetition.Duration = 'P1D'
$Task.Triggers.Repetition.Interval = 'PT60M'
$Task | Set-ScheduledTask -User $env:USERNAME
TaskPath TaskName State
-------- -------- -----
\ TestTask Ready
# View the change
$Task.Triggers.Repetition | Format-List * -Force
Duration : P1D
Interval : PT60M
StopAtDurationEnd : False
PSComputerName :
CimClass : Root/Microsoft/Windows/TaskScheduler:MSFT_TaskRepetitionPattern
CimInstanceProperties : {Duration, Interval, StopAtDurationEnd}
CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties
Modify the XML file directly - say the repetition times settings using a simple replace, to something else
(Get-Content -Path 'C:\Windows\System32\Tasks\TestTask').Replace('P1D','P12H') |
Set-Content -Path 'C:\Windows\System32\Tasks\TestTask'
[Get-Help], PSInvalidOperationException