Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    1. COI think there's still a problem with this approach, same problem as with the task scheduler UI. The state of this job is located in C:\Users\{jobowner}\AppData\Local\Microsoft\Windows\PowerShell\ScheduledJobs this state is required for the job to run properly. If you change the owner via UI or the schtasks exe it won't move that state and the job just errors. It seems to me to be a pretty big hole. Joe Admin creates some maintenance tasks, lets them run for a while, and then quits. New Admin has no way to get at the tasks without doing some serious hacking...
      singulars
    2. COHere's a decent write-up that appears to cover this issue: [link]http://janegilring.wordpress.com/2012/05/28/working-with-scheduled-tasks-from-windows-powershell/ Excerpt: _"...to retrieve the results of the job, not by looking in the XML-files, but by using the Get-Job cmdlet. There is a gotcha to be aware of regarding this. If you open a new PowerShell session and run Get-Job, the scheduled jobs created using the PSScheduledJob cmdlets will not be available. You have to first import the PSScheduledJob module and then run Get-Job. By using Receive-Job we can get the results from our job"_
      singulars
    3. COI read this, and have tested to be sure, but it only works for the user who created /is the owner of the job. The important bit is part where he identifies that the state of the job is stored to the user's appdata folder. I think we're just out of luck here and will have to write something to at least get status out of xml files. Ugly... "We can see that the job is stored in a separate folder in the current user`s AppData-folder:"
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload