Home > Articles

Windows PowerShell Job Tips and Tricks

Timothy Warner, author of Sams Teach Yourself Windows PowerShell in 24 Hours, teaches you how to take your PowerShell local and remote job skills to the next level.
Like this article? We recommend

The Windows PowerShell jobs engine allows us to run local and/or remote tasks in the background of an elevated console session. For instance, let's say we needed to find all .PDF files in a huge folder tree:

Get-ChildItem -Path E:\ -Recurse -Filter *.pdf

If your E:\ drive is anything like mine, the previous task is going to hang up your PowerShell console session for a long time. Annoying!

By contrast, if we put the previous Get-ChildItem call into a job, we can happily continue working in our session:

Start-Job -Name 'PDFSearch-EDrive' -ScriptBlock { Get-ChildItem -Path E:\ -Recurse -Filter *.pdf }

Id     Name            PSJobTypeName   State         HasMoreData     Location
--     ----            -------------   -----         -----------     --------
2      PDFSearch-ED... BackgroundJob   Running       True            localhost

We can use Get-Job to check job status:

Get-Job -Id 2

Id     Name            PSJobTypeName   State         HasMoreData     Location
--     ----            -------------   -----         -----------     --------
2      PDFSearch-CD... BackgroundJob   Completed     True            localhost

Finally, we can use Retrieve-Job with the -Keep switch to view the job results and keep them in memory for future reference:

Receive-Job -Id 2 -Keep | Select-Object -First 2

    Directory: E:\lab\db\commbutton

Mode             LastWriteTime      Length Name
----             -------------      ------ ----
-a----     4/23/2015   9:55 AM      27667CCENTv3.pdf
-a----     4/23/2015   9:55 AM      56913ITTv3.pdf

All of this information I've given you is well and good, but it should just be review. I want to take your PowerShell job skills to the next level by teaching you four "power user" tips and tricks:

  • Saving your job results by default
  • Leveraging the -AsJob switch parameter
  • Troubleshooting child jobs
  • Making use of community contributions

With no further ado, let's begin!

Saving Your Job Results by Default

If you forget to add the -Keep switch parameter to the Receive-Job cmdlet, your job results go up the proverbial chimney. Personally, that default behavior in Windows PowerShell ticks me off.

My friend and Windows PowerShell MVP Jeff Hicks taught me a neat trick to ensure that Receive-Job always runs with the -Keep switch, at least for the current session.

All we have to do is modify the default parameter values for our session. Try this:

$PSDefaultParameterValues = @{'Receive-Job:Keep'=$true}

Now create, run, and receive another PowerShell job. You should find that the job results persist in your current runspace thanks to our new default parameter value. We can view the contents of this automatic variable at any time:


Name                           Value
----                           -----
Receive-Job:Keep               True

This default parameter change disappears when you close your current PowerShell session. Thus, you'll want to add that line to your PowerShell profile(s) as necessary if it's something you need for the future.

For some reason I'm inspired to remind you that you're free to export job results to, say, a text file or a delimited file. For instance, the following code creates a job that pulls event log data, and then stores it in a simple text file:

Start-Job -Name 'systemlog' -ScriptBlock { Get-EventLog -LogName System -Newest 50 }
Receive-Job -Id 2 -Keep | Out-File -Path '.\event.txt'

Ever the detective, PowerShell MVP Boe Prox taught me another way to retrieve job data if we forget the -Keep switch. For this example, I'll create a job showing processes that consume more than 100MB of RAM on my Windows 8.1 system:

Start-Job -Name 'highmem' -ScriptBlock { Get-Process | Where-Object { $_.WS -gt 100MB } }

If I run a Receive-Job and then a Get-Job again, the HasMoreData property is False as expected:

Receive-Job -Name highmem
Get-Job -Name highmem

Id     Name            PSJobTypeName   State         HasMoreData     Location
--     ----            -------------   -----         -----------     --------
4      highmem         BackgroundJob   Completed     False           localhost

Okay, here's where the .NET magic comes in. I'll store the highmem job as a variable, and then check out its ChildJobs.output property:

PS C:\> $highmem.ChildJobs.output | Select-Object -First 2

Handles  NPM(K)    PM(K)      WS(K) VM(M)   CPU(s)     Id ProcessName
-------  ------    -----      ----- -----   ------     -- -----------
   1156      37   190532     167728   794 8,549.25   1120 chrome
    188      26   168340     157188   915   434.78   1672 chrome

Whoa—isn't that awesome?

Leveraging the -AsJob Switch Parameter

Instead of formally defining background jobs with Get-Job, we can tack on the -AsJob parameter to some cmdlets to create ad hoc background jobs. Let's see which of the PowerShell core cmdlets support this switch:

PS C:\> Get-Command -ParameterName AsJob | Select-Object -Property Name


Let's focus on Invoke-Command because it uses WS-Man remoting and is therefore more efficient than the old DCOM/RPC remoting used by most of those other commands.

Check this out:

Invoke-Command -ComputerName dc1,mem1,mem2 -ScriptBlock { Get-EventLog -LogName Security -Newest 2 } -AsJob

Id     Name            PSJobTypeName   State         HasMoreData     Location
--     ----            -------------   -----         -----------     --------
15     Job15           RemoteJob       Running       True            dc1,mem1,mem2

Notice that the PSJobTypeName is RemoteJob instead of the BackgroundJob type we've seen thus far.

Troubleshooting Child Jobs

Something many PowerShell administrative scripts don't (yet) understand is that jobs in PowerShell always consist of one parent job and one or more child jobs. For instance, consider the Invoke-Command -AsJob example we used previously:

Invoke-Command -ComputerName dc1,mem1,mem2 -ScriptBlock { Get-EventLog -LogName Security -Newest 2 } -AsJob

Id     Name            PSJobTypeName   State         HasMoreData     Location
--     ----            -------------   -----         -----------     --------
15     Job15           RemoteJob       Running       True            dc1,mem1,mem2

That ID of 15 refers to the parent job container, and I'm sure that PowerShell has a separate child job defined for each computer queried by our Get-EventLog script block. How do I know? By using the -IncludeChildJob switch of the Get-Job cmdlet:

PS C:\> Get-Job -IncludeChildJob

Id     Name            PSJobTypeName   State         HasMoreData     Location
--     ----            -------------   -----         -----------     --------
15     Job15           RemoteJob       Completed     True            dc1,mem1,mem2
16     Job16                           Completed     True            dc1
17     Job17                           Completed     True            mem1
18     Job18                           Completed     True            mem2

Understanding child jobs makes troubleshooting easier because a failure in a child job can cause the parent job to report a failed status. To that point, we can retrieve child job contents simply by using the child job ID:

Receive-Job -Id 18 -Keep

   Index Time          EntryType   Source                 InstanceID Message    PSCompute
   ----- ----          ---------   ------                 ---------- -------    ---------
    4104 Jan 13 10:09  SuccessA... Microsoft-Windows...         4624 An acco... mem2
    4103 Jan 13 10:09  SuccessA... Microsoft-Windows...         4672 Special... mem2

Making Use of Community Contributions

Please keep in mind that Windows PowerShell is largely a community-driven technology stack; for proof, notice how many PowerShell features are hosted by Microsoft in GitHub repositories.

Once again, Boe Prox offers us an alternative to the native PowerShell job engine in his PoshRSJob module. Let's use PowerShellGet to install it:

Find-Module -Name poshrsjob | Install-Module -Verbose

Boe wrote the PoshRSJob module in an attempt to improve background job performance in PowerShell. He also wanted to give users the ability to throttle their jobs' resource utilization. Here's the command set:

PS C:\> Get-Command -Module PoshRSJob | Select-Object -Property Name


Let's say we want to write a job that checks the status of the Windows Update service on our three servers, but we want to make the job more resource-friendly on our system and the network. For instance, normally Invoke-Command operates on 25 computers simultaneously, but here we want to throttle that value back to two. Enter Start-RSJob!

Start-RSJob -Name 'wucheck' -Throttle 2 -ScriptBlock { Invoke-Command -ComputerName dc1, mem1, mem2 -ScriptBlock {Get-Service -Name wuauserv}}

Do you see the -Throttle switch? You should also notice peppier performance with the RSJob architecture as compared to the PowerShell core job engine.

One more thing—these RSJobs are managed separately from PowerShell core jobs. Therefore, don't forget to use Get-RSJob and Receive-RSJob in your experimentation.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020