$convertTime<\/B>:<\/P>$convertTime = [wmiclass]”win32_scheduledjob”<\/PRE>\nWe use the ForEach<\/B> statement to walk through the collection of scheduled job objects. Unlike VBScript, we can use ForEach<\/B> to walk through a collection of one or more objects. VBScript will throw an error if a collection has only a single item in it. Inside the ForEach<\/B> loop, we use the Format-Table<\/B> cmdlet to format a nice output for our information:<\/P>ForEach($job in $list)\n {\n Format-table -inputobject $job -property jobID, command, jobstatus,\n<\/PRE>\nWe want to change the way the Format-Table<\/B> cmdlet displays information. This is where things get a bit complicated. To change the start time value that is displayed, we create a custom display for the table. We use a Windows PowerShell hash table to create a custom label and value for the table. The label we want to use is called “Start Time” and we want to calculate the expression by using the ConvertToDateTime<\/B> method from the Win32_ScheduledJob<\/B> WMI class:<\/P>@{ Label = “Start time” ; expression = { $convertTime.ConvertToDateTime($job.startTime)} } -autosize\n } \n} #end list\n<\/PRE>\nWhen we run the script, the scheduled jobs are displayed as shown here:<\/P>![\"Image](\"http:\/\/img.microsoft.com\/library\/media\/1033\/technet\/images\/scriptcenter\/qanda\/hsg\/2009\/march\/hey0331\/hsg-03-31-09-01.jpg\")
\n
<\/P>\n
Next we need to create the DeleteJob<\/B> function. The DeleteJob<\/B> function begins by using the function<\/B> keyword and the name of the function:<\/P>Function DeleteJob()\n{\n<\/PRE>\nTo make the script more useful, we accept an array of job IDs instead of only working with a single job ID. To do this, we use the ForEach<\/B> statement. The collection of job IDs is stored in the $jobID<\/B> variable, and inside the loop each individual job ID is known as $sJobID<\/B>. This is seen here:<\/P>foreach($sJobID in $jobID)\n {\n<\/PRE>\nWe now print out a status message to provide feedback to the user as to which job ID is being deleted on which computer:<\/P>
“Deleting job ID $sJobID on $computer”\n<\/PRE>\nNow we use the Get-WmiObject<\/B> cmdlet to retrieve the specific scheduled job that is represented by the job ID. The \u2013filter<\/B> parameter is used to return the specific scheduled job. As used here, it takes the place of the where<\/B> clause normally used with the WMI Query Language (WQL):<\/P>$job = get-wmiobject -class win32_scheduledjob -computername $computer `\n -filter “jobID = $sjobID”\n<\/PRE>\nWe then call the delete<\/B> method. Just like any other method in Windows PowerShell, it must be followed by a set of parentheses:<\/P>$errRTN = $job.delete()\n $errRTN\n } #end foreach job\n} #end deleteJob\n<\/PRE>\nWhen we call the script with a single job ID<\/B> parameter, the scheduled job is deleted:<\/P>![\"Image](\"http:\/\/img.microsoft.com\/library\/media\/1033\/technet\/images\/scriptcenter\/qanda\/hsg\/2009\/march\/hey0331\/hsg-03-31-09-02.jpg\")
\n
<\/P>\n
The command line that is used to delete the first scheduled job when the script is run is seen here:<\/P>
DeleteScheduledTask.ps1 \u2013JobID 1<\/PRE>\nIf you need to delete multiple scheduled jobs, you can separate them by commas at the command line when you call the script. As seen in the previous example, you do not need to supply the entire parameter name if you do not wish to do so. You can use a partial parameter:<\/P>
DeleteScheduledTask.ps1 \u2013J 2,3<\/PRE>\nWhen we run the script, we are greeted with the output seen here:<\/P>![\"Image](\"http:\/\/img.microsoft.com\/library\/media\/1033\/technet\/images\/scriptcenter\/qanda\/hsg\/2009\/march\/hey0331\/hsg-03-31-09-03.jpg\")
\n
<\/P>\n
Next it is time to evaluate the command-line parameters. If the script was run with the \u2013help<\/B> parameter, we call the help<\/B> function and exit the script. If the script was called with the \u2013list<\/B> parameter, we call the listJob<\/B> function and exit. If the \u2013jobID<\/B> parameter is present, we call the deleteJob<\/B> function. If the \u2013jobID<\/B> parameter is not present and neither the \u2013help<\/B> nor the \u2013list<\/B> parameters are present, we print a message about a missing parameter and call the help<\/B> function and exit. This section of the script is seen here:<\/P>if($help) { help ; exit}\nif($list) { listJob ; exit }\nif($jobID) { deleteJob }\nif(!$jobID) { “missing jobID” ; help ; exit }\n<\/PRE>\nWell, AF, “They Call It Stormy Monday” by Elmore James<\/A> playing now. I guess a classic blues song is appropriate for characterizing the feeling of sadness that overcomes us when we must bring the article to a conclusion. But cheer up, there is always tomorrow when Scheduled Tasks Week continues. Until then, take care.<\/P>\n <\/P>\n
Ed Wilson and Craig Liebendorfer, Scripting Guys<\/B><\/P><\/p>\n","protected":false},"excerpt":{"rendered":"
Hey, Scripting Guy! We had this guy a while back who went around and created all kinds of goofy scheduled tasks using the AT command. He did not document anything, and many of the scheduled jobs do not work anyway. And we are not sure what the ones that do work are supposed to do. […]<\/p>\n","protected":false},"author":595,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[31,32,3,45],"class_list":["post-54073","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-operating-system","tag-scheduled-tasks","tag-scripting-guy","tag-windows-powershell"],"acf":[],"blog_post_summary":"
Hey, Scripting Guy! We had this guy a while back who went around and created all kinds of goofy scheduled tasks using the AT command. He did not document anything, and many of the scheduled jobs do not work anyway. And we are not sure what the ones that do work are supposed to do. […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/54073","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/595"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=54073"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/54073\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=54073"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=54073"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=54073"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"Hey,](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/q-for-powertip.jpg\" "\\"Hey,")
<\/H2>\n![\"Spacer\"](\"https:\/\/devblogs.microsoft.com\/scripting\/wp-content\/uploads\/sites\/29\/2019\/05\/spacer.gif\")
![\"Hey,](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/a-for-powertip.jpg\" "\\"Hey,")
\n