This is the built-in help made by Microsoft for the command 'Receive-Job', in PowerShell version 2 - as retrieved from
Windows version 'Microsoft® Windows Vista™ Ultimate ' PowerShell help files on 2016-06-23.
For PowerShell version 3 and up, where you have Update-Help, this command was run just before creating the web pages from the help files.
Gets the results of the Windows PowerShell background jobs in the current session.
Receive-Job [-Job] <Job[]> [[-ComputerName] <string[]>] [-Keep] [-NoRecurse] [<CommonParameters>]
Receive-Job [[-InstanceId] <Guid[]>] [-Keep] [-NoRecurse] [<CommonParameters>]
Receive-Job [-Job] <Job[]> [[-Location] <string[]>] [-Keep] [-NoRecurse] [<CommonParameters>]
Receive-Job [[-Name] <string[]>] [-Keep] [-NoRecurse] [<CommonParameters>]
Receive-Job [-Job] <Job[]> [[-Session] <PSSession[]>] [-Keep] [-NoRecurse] [<CommonParameters>]
Receive-Job [-Id] <Int32[]> [-Keep] [-NoRecurse] [<CommonParameters>]
The Receive-Job cmdlet gets the results of Windows Powershell background jobs. Use Receive-Job to get the results of jobs started by using the St
art-Job cmdlet or the AsJob parameter of any cmdlet. You can get the results of all jobs or identify jobs by their name, ID, instance ID, compute
r name, location, or session, or by submitting a job object.
When you start a Windows PowerShell background job, the job starts, but the results do not appear immediately. Instead, the command returns an ob
ject that represents the background job. The job object contains useful information about the job, but it does not contain the results. This meth
od allows you to continue working in the session while the job runs. For more information about background jobs in Windows PowerShell, see about
_Jobs.
To get the results of the command, use the Receive-Job cmdlet. Receive-Job gets the results that have been generated by the time that the Receive
-Job command is submitted. If the results are not yet complete, you can run additional Receive-Job commands to get the remaining results.
By default, job results are deleted from the system when you receive them, but you can use the Keep parameter to save the results so that you can
receive them again. To delete the job results, receive them again (without the Keep parameter), close the session, or use the Remove-Job cmdlet
to delete the job from the session.
<
Online version: http://go.microsoft.com/fwlink/?LinkID=113372
about_Jobs
about_Job_Details
about_Remote_Jobs
Start-Job
Get-Job
Wait-Job
Stop-Job
Remove-Job
Invoke-Command
<
-------------------------- EXAMPLE 1 --------------------------
C:\PS>$job = start-job -scriptblock {get-process}
C:\PS> receive-job -job $job
Description
-----------
These commands use the Job parameter to get the results of a particular job. The first command uses the Start-Job cmdlet to start a job that runs
a "Get-Process" command. The command uses the assignment operator (=) to save the resulting job object in the $job variable.
The second command uses the Receive-Job cmdlet to get the results of the job. It uses the Job parameter to specify the job.
-------------------------- EXAMPLE 2 --------------------------
C:\PS>$job = start-job -scriptblock {get-process}
C:\PS> $job | receive-job
Description
-----------
This example is the same as Example 2, except that the command uses a pipeline operator (|) to send the job object to Receive-Job. As a result, t
he command does not need a Job parameter to specify the job.
-------------------------- EXAMPLE 3 --------------------------
C:\PS>$j = invoke-command -computername Server01, Server02, Server03 -scriptblock {get-service} -AsJob
C:\PS> $j.childjobs
Id Name State HasMoreData Location Command
-- ---- ----- ----------- -------- -------
2 Job2 Completed True Server01 get-service
3 Job3 Completed True Server02 get-service
4 Job4 Completed True Server03 get-service
C:\PS> receive-job -name Job3 -keep
Status Name DisplayName PSComputerName
------ ----------- ----------- --------------
Running AeLookupSvc Application Experience Server02
Stopped ALG Application Layer Gateway Service Server02
Running Appinfo Application Information Server02
Running AppMgmt Application Management Server02
Description
-----------
These commands use the Name parameter of Receive-Job to get the results of one of several background jobs run on remote computers.
The first command uses the Invoke-Command cmdlet to start a background job that runs a Get-Service command on three remote computers. The command
uses the AsJob parameter to run the command as a background job. The command saves the resulting job object in the $j variable.
When you use the AsJob parameter of Invoke-Command to start a job, the job object is created on the local computer, even though the job runs on t
he remote computers. As a result, you use local commands to manage the job.
Also, when you use AsJob, Windows PowerShell returns one job object that contains a child job for each job that was started. In this case, the jo
b object contains three child jobs, one for each job on each remote computer.
The second command uses the dot method to display the value of the ChildJobs property of the job object in $j. The display shows that the command
created three child jobs, one for the job on each remote computer.
The third command uses the Receive-Job cmdlet to get the results of the Job3 child job that ran on the Server02 computer. It uses the Name parame
ter to specify the name of the child job and the Keep parameter to save the job results even after they are received.
-------------------------- EXAMPLE 4 --------------------------
C:\PS>$s = new-pssession -computername Server01, Server02, Server03
C:\PS> $j = invoke-command -session $s -scriptblock {start-job -scriptblock {get-eventlog -logname system}}
C:\PS> $j
Id Name State HasMoreData Location Command
-- ---- ----- ----------- -------- -------
1 Job1 Completed True Localhost get-eventlog system
2 Job2 Completed True Localhost get-eventlog system
3 Job3 Completed True Localhost get-eventlog system
C:\PS> $results = invoke-command -session $s -scriptblock {param($j) receive-job -job $j} -ArgumentList $j
Description
-----------
This example shows how to get the results of background jobs run on three remote computers.
The first command uses the New-PSSession cmdlet to create three PSSessions, one on each of the servers specified in the command. It saves the PSS
essions in the $s variable.
The second command uses the Invoke-Command cmdlet to run a Start-Job command in each of the PSSessions in the $s variable. The job runs a Get-Eve
ntlog command that gets the events in the System log. The command saves the results in the $j variable.
Because the command used Invoke-Command to run the Start-Job command, the command actually started three independent jobs on each of the three co
mputers. As a result, the command returned three job objects representing three jobs run locally on three different computers.
The third command displays the three job objects in $j.
The fourth command uses Invoke-Command to run a Receive-Job command in each of the PSSessions in $s and save the results in the $results variable
.
Because $j is a local variable, the script block uses the "param" keyword to declare the variables in the command and the ArgumentList parameter
to supply the value of $j.