Receive-Job

PS C:\> $job = Start-Job -ScriptBlock {Get-Process}
PS C:\> Receive-Job -Job $job

PS C:\> $job = Start-Job -ScriptBlock {Get-Process}
PS C:\> $job | Receive-Job

1. The first command uses the Invoke-Command cmdlet to start a background job that runs a Get-Service command on three remote computers:

   PS C:\> $j = Invoke-Command -ComputerName Server01, Server02, Server03 -ScriptBlock {Get-Service} -AsJob
   

   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 the 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 job object contains three child jobs, one for each job on each remote computer.

2. The second command uses the dot method to display the value of the **ChildJobs** property of the job object in $j:

   PS C:\> $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

   The display shows that the command created three child jobs, one for the job on each remote computer.

3. The third command uses the **Receive-Job** cmdlet to get the results of the Job3 child job that ran on the Server02 computer:

   PS C:\> 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

   It uses the *Name* parameter to specify the name of the child job and the *Keep* parameter to save the job results even after they are received.These commands get the results of one of several background jobs run on remote computers.

1. The first command uses the New-PSSession cmdlet to create three user-managed sessions (**PSSessions**), one on each of the servers specified in the command:

   PS C:\> $s = new-pssession -computername Server01, Server02, Server03
   

   It saves the sessions in the $s variable.

2. The second command uses the **Invoke-Command** cmdlet to run a **Start-Job** command in each of the **PSSessions** in the $s variable:

   PS C:\> $j = invoke-command -session $s -scriptblock {start-job -scriptblock {get-eventlog -logname system}}
   

   The job runs a Get-EventLog 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 computers. As a result, the command returned three job objects representing three jobs run locally on three different computers.

3. The third command displays the three job objects in $j:

   PS C:\> $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

4. The fourth command uses Invoke-Command to run a **Receive-Job** command in each of the sessions in $s and save the results in the $Results variable.Because $j is a local variable, the script block uses the **Using** scope modifier to identify the $j variable:

   PS C:\> $results = Invoke-Command -Session $s -ScriptBlock {Receive-Job -Job $Using:j}
   

   For more information about the **Using** scope modifier, see about_Remote_Variables (http://go.microsoft.com/fwlink/?LinkID=252653).This example shows how to get the results of background jobs run on three remote computers.