Here's a technique you might want to use for ad hoc troubleshooting or reporting. Even though it is possible to set up scheduled tasks to run PowerShell commands or scripts, it is cumbersome and time consuming. PowerShell v3 offers a great alternative, but I'll cover that another day. Suppose I want to do something every 15 minutes such as check the status of a service. Instead of going through the effort of creating a scheduled task, I'll create a PowerShell job.<\/p>\n
If I setup a job, it will run in my PowerShell session for as long as it needs to run or until I close my PowerShell session. Thus the trick is to keep the job running which easy to accomplish with a simple While loop.<\/p>\n
This will loop indefinitely because True is always True. In an interactive session, I can break out of this using Ctrl+C or insert code to break out if some condition is met. If I use this loop in my Start-Job command, the command will run indefinitely until the job terminates. I can always kill the job with the Stop-Job cmdlet. Although I suppose you should be careful with the code you put in the While loop as part of job because if you use Stop-Job, there's no way of knowing what code might be executing at the time. But for my use of this technique I'm keeping it simple and quick.<\/p>\n The other part is the timing interval. This is easily accomplished using the Start-Sleep cmdlet and specifying a value in milliseconds, or more typically, seconds. Depending on your task you could also take advantage of eventing, but that too is a bit complicated to setup and tear down. So, now the main part of my While loop looks like this:<\/p>\n My code will run every 900 seconds (15 minutes). Here's a longer example that I put in a script.<\/p>\n while ($True) { I could have put all of that into a script block and created the job, or I could use the script.<\/p>\n The job will write the service status information to a local text file every 10 minutes. When I'm done I can simply my PowerShell session or run Stop-Job. Here's where it can really get interesting: how about running this \"scheduled task\" ON a remote computer? There are two approaches. It depends on where you want the job to live. I could keep the job on my computer:<\/p>\n HasMoreData : True $file=\"c:\\work\\mylog.txt\" while ($True) { The job object is on my (local) computer, even though the task is running on the remote computer. The other approach is to put the job ON the remote computer. This is a little trickier since I have to get the code I want to run ON the remote computer. I could copy the script over. Or I might try something like this:<\/p>\n First I want to convert my script into a scriptblock by stripping out the comments and inserting a semi colon at the end of each line. Then I can create a scriptblock from this text on the remote computer.<\/p>\n I can pass this text as a parameter with invoke-command to setup a job on the remote computer. I recommend using a PSSession in case you want to go back later and stop the job.<\/p>\n The job is created on the remote session and runs indefinitely.<\/p>\n WARNING: 2 columns do not fit into the display and were removed.<\/p>\n Id Name State HasMoreData Location As I mentioned there are probably several ways you could do this. When I am finished I can either terminate the PSSession or stop the remote job.<\/p>\n WARNING: 2 columns do not fit into the display and were removed.<\/p>\n Id Name State HasMoreData Location So the next time you need some scheduled PowerShell, at least on a temporary basis, take a look at Start-Job.<\/p>\n","protected":false},"excerpt":{"rendered":" Here’s a technique you might want to use for ad hoc troubleshooting or reporting. Even though it is possible to set up scheduled tasks to run PowerShell commands or scripts, it is cumbersome and time consuming. PowerShell v3 offers a great alternative, but I’ll cover that another day. Suppose I want to do something every…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[75,8],"tags":[122,534,87,333,351],"class_list":["post-1956","post","type-post","status-publish","format-standard","hentry","category-powershell-v2-0","category-scripting","tag-invoke-command","tag-powershell","tag-remoting","tag-start-job","tag-tasks"],"yoast_head":"\n
\nWhile ($True) {
\n #do something
\n}
\n<\/code><\/p>\n
\nWhile ($True) {
\n #do something
\n Start-Sleep -seconds 900
\n}
\n<\/code><\/p>\n
\n$file=\"c:\\work\\mylog.txt\"
\n#the number of seconds to pause between checks
\n$seconds=600
\n#the service to check
\n$service=\"Spooler\"
\n#the computer to check
\n$computer=$env:computername<\/p>\n
\n $s=get-service $service -ComputerName $computer
\n $t=\"{0} Service {1} on {3} has a status of {2}\" -f (Get-Date), $s.name,$s.status,$computer
\n $t | Out-File -FilePath $file -Append
\n Start-Sleep -seconds $seconds
\n}
\n<\/code><\/p>\n
\nPS C:\\> start-job -FilePath C:\\scripts\\PollService.ps1
\n<\/code><\/p>\n
\nPS C:\\> invoke-command -FilePath C:\\scripts\\PollService.ps1 -ComputerName quark -asjob
\nPS C:\\> get-job 3 | format-list<\/p>\n
\nStatusMessage :
\nLocation : quark
\nCommand : #requires -version 2.0<\/p>\n
\n #the number of seconds to pause between checks
\n $seconds=600
\n #the service to check
\n $service=\"Spooler\"
\n $computer=$env:computername<\/p>\n
\n $s=get-service $service -ComputerName $computer
\n $t=\"{0} Service {1} on {3} has a status of {2}\" -f (Get-Date),
\n $s.name,$s.status,$computer
\n $t | Out-File -FilePath $file -Append
\n Start-Sleep -seconds $seconds
\n }
\nJobStateInfo : Running
\nFinished : System.Threading.ManualResetEvent
\nInstanceId : 03a48cd0-f21a-4b7d-9a78-f148ec784ff8
\nId : 3
\nName : Job3
\nChildJobs : {Job4}
\nOutput : {}
\nError : {}
\nProgress : {}
\nVerbose : {}
\nDebug : {}
\nWarning : {}
\nState : Running
\n<\/code><\/p>\n
\nPS C:\\> $text=get-content C:\\scripts\\PollService.ps1 | where {$_ -notmatch \"^#\" -AND $_} | foreach {\"$_;\"}
\n<\/code><\/p>\n
\nPS C:\\> $quark=new-pssession -comp quark
\nPS C:\\> invoke-command -scriptblock {param ($txt) $sb=$executioncontext.invokecommand.newscriptblock($txt) ; Start-job -scriptblock $sb } -session $quark -ArgumentList ($text | out-string)
\n<\/code><\/p>\n
\nPS C:\\> invoke-command {get-job -State Running} -Session $quark<\/p>\n
\n-- ---- ----- ----------- --------
\n17 Job17 Running True localhost
\nPS C:\\> invoke-command {get-content C:\\work\\mylog.txt} -Session $quark
\n1\/5\/2012 9:37:41 AM Service Spooler on QUARK has a status of Running
\n1\/5\/2012 9:38:46 AM Service Spooler on QUARK has a status of Running
\n1\/5\/2012 10:44:54 AM Service Spooler on QUARK has a status of Running
\n<\/code><\/p>\n
\nPS C:\\> invoke-command {stop-job -State Running -PassThru} -Session $quark<\/p>\n
\n-- ---- ----- ----------- --------
\n17 Job17 Stopped False localhost
\n<\/code><\/p>\n