Invoke-Command in a background job

powershell invoke-command start-job
bones picture bones · Jul 17, 2013 · Viewed 13.7k times · Source

I have a powershell 2.0 script which should run a command on several servers and process the output. I want to run the command and the processing for each server in a background job.

The comand works without any problems and terminates within half a second or less:

Invoke-Command -ComputerName $client -ScriptBlock { #do some stuff }

But when I run this in a background job, the job doesn't terminate:

Start-Job { Invoke-Command -ComputerName $client -ScriptBlock { #do some stuff } }

Has someone a idea what the problem could be?

Answer

Andy Arismendi picture Andy Arismendi · Jul 17, 2013

Looks like you should do it the other way:

http://technet.microsoft.com/en-us/library/hh849698.aspx

To run a background job on a remote computer, use the AsJob parameter that is available on many cmdlets, or use the Invoke-Command cmdlet to run a Start-Job command on the remote computer. For more information, see about_Remote_Jobs.

Related questions

Invoke a second script with arguments from a script

I have a script that reads a configuration file that results in a set of name value pairs that I would like to pass as arguments to a function in a second PowerShell script. I do not know what parameters …

Read More
Start-job vs. Invoke-command -asjob

I'm trying to do basic background jobs in PowerShell 2.0, and I'm seeing different things with start-job and invoke-command -asjob. If I do this: start-job -scriptblock {get-process} I get a job object, but the child job (which is created automatically by …

Read More
How do I pass named parameters with Invoke-Command?

I have a script that I can run remotely via Invoke-Command Invoke-Command -ComputerName (Get-Content C:\Scripts\Servers.txt) ` -FilePath C:\Scripts\ArchiveEventLogs\ver5\ArchiveEventLogs.ps1 As long as I use default parameters, it works fine. However, the script has 2 named […

Read More