Invoke-Command + Get-ChildItem = Output?

[izShell57]

Hello!

I have a script that used Start-Job to start Get-ChildItem script. For reasons that are too long to get into, I wanted to try this methodology with Invoke-Command instead!

The command looks like this:

PowerShell

$a = Invoke-Command -AsJob -ComputerName $env:computername -ScriptBlock { Get-ChildItem -Path C:\ *.exe } echo $a

1 2 3

$a = Invoke-Command -AsJob -ComputerName $env:computername -ScriptBlock { Get-ChildItem -Path C:\ *.exe } echo $a

However, instead of $a containing the output for the Get-Childitem command ( a list of executables), it instead contains the output for the job!

PowerShell

Id Name PSJobTypeName State HasMoreData Location Command -- ---- ------------- ----- ----------- -------- ------- 15 Job15 RemoteJob Running True WIN-GNNG6UDHR6J ...  

1 2 3

Id Name PSJobTypeName State HasMoreData Location Command -- ---- ------------- ----- ----------- -------- ------- 15 Job15 RemoteJob Running True WIN-GNNG6UDHR6J ...

What am I doing wrong?
I have attempted to use Receive-Job but have had no success yet. This is the error I get when I try to receive-job

PowerShell

Connecting to remote server WIN-GNNG6UDHR6J failed with the following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic. + CategoryInfo : OpenError: (WIN-GNNG6UDHR6J:String) [], PSRemotingTransportException + FullyQualifiedErrorId : AccessDenied,PSSessionStateBroken

1 2 3

Connecting to remote server WIN-GNNG6UDHR6J failed with the following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic. + CategoryInfo : OpenError: (WIN-GNNG6UDHR6J:String) [], PSRemotingTransportException + FullyQualifiedErrorId : AccessDenied,PSSessionStateBroken

Thanks ahead of time!

• This topic was modified 4 months, 2 weeks ago by izShell57.
• This topic was modified 4 months, 2 weeks ago by grokkit.

[AdminOfThings45 Participant Topics: 1 Replies: 97 Points: 446Rank: Contributor]

If you want the output of the remote command to be stored in $a, don’t use the -AsJob switch. If you continue to use a job, then once $a shows a State other than Running, you can use $a | Receive-Job for the output. Access denied errors could be a number of things. I’d make sure the account running Invoke-Command has access to perform the remote command as if it were running the command locally on the target system. Admin elevation may be required in the shell as well.

[js Participant Topics: 32 Replies: 852 Points: 2,780Rank: Community Hero]

Here’s an example. In powershell 7 it comes out blank though, lol. For this example, the prompt has to be elevated.

PowerShell

invoke-command localhost -asjob { dir } | receive-job -wait -AutoRemoveJob

1	invoke-command localhost -asjob { dir } | receive-job -wait -AutoRemoveJob

[Author]

Posts