Page History
...
SYNOPSIS
Converts jobs from the Windows Task Scheduler to JobScheduler.
...
The job configuration from the Windows Task Scheduler is converted to XML job files that which can be deployed to a JobScheduler Master.
The cmdlet writes XML job files to an output directory. You can copy such files to the JobScheduler Master's ./config/live folder to deploy your jobs.
...
Specifies an individual job to be converted. Consider Note that job names are not unique with Windows Task Scheduler. When used with the -TaskPath parameter then a single job can be selected.
...
Without this parameter jobs from any all paths are converted.
| Required? | false |
| Position? | 2 |
| Default value | |
| Accept pipeline input? | true (ByPropertyName) |
| Accept wildcard characters? | false |
...
Accepts the name of a Joda time zone, see http://joda-time.sourceforge.net/timezones.html
The cmdlet does not convert dates according to this time zone, instead the specified time zone is added to the run-time settings of jobs. Consider Note that a JobScheduler Master might be operated in a time zone
that is different from to the time zone that the Windows Task Scheduler is operated for.
...
- Triggers for monthly job execution are not converted as there is no public API for this trigger type.
- Actions of Windows Task Scheduler jobs are mapped to a single JobScheduler job script.
- For cyclic jobs in JobScheduler, repetitions have to occur within a 24 hours period. Windows Task Scheduler knows about repetitions that exceed this period.
...
Overview
Content Tools