Server-wide ScheduledJobs should allow for non-creator/owner to administer them - by Seth Gray

Status : 


Sign in
to vote
ID 780966 Comments
Status Active Workarounds
Type Suggestion Repros 0
Opened 3/7/2013 3:14:06 PM
Access Restriction Public


Currently created scheduledjobs can only be administered (either through get-scheduledjob/set-scheduledjob or get-job (to get status)) by the user who was initial created as the owner of the job. This is by default the logged in user, or credentialed user if passed -credential switch. 

Problem is that this means user's who are not the owner of the scheduled job can't get status via get-job, nor administer it, making it difficult for us to recommend scheduled jobs as a devops/IT admin feature. Scheduled jobs might be around for a lot longer than the original user who created it, and the idea that you can't see the status of the job (or even know it exists on the server) from powershell seems a pretty big oversight on this functionality. 

Sign in to post a comment.