BilliAm
BilliAm

Reputation: 589

Powershell Passing Parameters to Nested Start-Job

I am attempting to pass paramters to a nested job.

$executepath = "D:\nttools\CoreAutomation\$patch.zipfilename\$ntupdatefilename"

$sb = {Start-Job -Name $NTUpdate -ScriptBlock {& cmd.exe /c $executepath}}

Invoke-Command -Session $NTSession -ScriptBlock $sb -ArgumentList $executepath

With this output showing the command is not actually rendering the parameter in the string:

State          : Running
PSComputerName : LKS.nt.isg.local
RunspaceId     : 8a1c9cc2-1cd0-42a6-a1d0-89d977aabf04
HasMoreData    : True
StatusMessage  :
Location       : localhost
Command        : & cmd.exe /c $executepath
JobStateInfo   : Running
InstanceId     : 9e95c0d8-d177-4a1a-9283-56f07ff5f0a8
Id             : 1
Name           : Job1
ChildJobs      : {System.Management.Automation.PSRemotingChildJob}
PSJobTypeName  : BackgroundJob
PSBeginTime    : 5/9/2017 2:00:49 PM
PSEndTime      :

I have tried to add this parameters in the script block as well with the same result:

$executepath = "D:\nttools\CoreAutomation\$patch.zipfilename\$ntupdatefilename"

$sb = {Start-Job -Name $NTUpdate -ScriptBlock {param($executepath) & cmd.exe /c $executepath} -ArgumentList $executepath}

Invoke-Command -Session $NTSession -ScriptBlock $sb -ArgumentList $executepath


State          : Running
PSComputerName : LKS.nt.isg.local
RunspaceId     : 7e039382-d8a6-4298-9983-8f3f6fd2a6c3
HasMoreData    : True
StatusMessage  :
Location       : localhost
Command        : param($executepath) & cmd.exe /c $executepath
JobStateInfo   : Running
InstanceId     : 77e80c13-2801-4726-81f4-8c960319cd0b
Id             : 1
Name           : Job1
ChildJobs      : {System.Management.Automation.PSRemotingChildJob}
PSJobTypeName  : BackgroundJob
PSBeginTime    : 5/9/2017 2:08:38 PM
PSEndTime      :

Updated:

Tried what was listed in comments. No luck, same result.

$executepath = "D:\nttools\CoreAutomation\$patch.zipfilename\$ntupdatefilename"

$sb = {param($executepath) Start-Job -Name NTUpdate -ScriptBlock {param($executepath) & cmd.exe /c $executepath} -ArgumentList $executepath}

Invoke-Command -Session $NTSession -ScriptBlock  $sb -ArgumentList $executepath


State          : Running
PSComputerName : LKS.nt.isg.local
RunspaceId     : 7b7b86df-a216-494e-b7e7-2336e6994a06
HasMoreData    : True
StatusMessage  :
Location       : localhost
Command        : param($executepath) & cmd.exe /c $executepath
JobStateInfo   : Running
InstanceId     : 4d5dd307-2158-4b38-b118-987f1e56cb12
Id             : 1
Name           : NTUpdate
ChildJobs      : {System.Management.Automation.PSRemotingChildJob}
PSJobTypeName  : BackgroundJob
PSBeginTime    : 5/9/2017 2:25:19 PM
PSEndTime      :

Update 2 -$using:executepath

Invoke-Command -Session $NTSession -ScriptBlock {Start-Job -Name NTUpdate -ScriptBlock {& cmd.exe /c $Using:executepath}}

I have tried with and I get this error:

The value of the using variable '$using:executepath' cannot be retrieved because it has not been set in the local
session.
    + CategoryInfo          : InvalidOperation: (:) [Start-Job], RuntimeException
    + FullyQualifiedErrorId : UsingVariableIsUndefined,Microsoft.PowerShell.Commands.StartJobCommand
    + PSComputerName        : LKSNTADM01.nt.isg.local

Upvotes: 0

Views: 1750

Answers (1)

TheMadTechnician
TheMadTechnician

Reputation: 36297

Ok, so if I understand correctly, your main issue here is that when you look at the command in the job you see:

& cmd.exe /c $executepath

When you expect to see:

& cmd.exe /c D:\nttools\CoreAutomation\Defect1126511_CD_2017-04-24_1800_A‌​\nttest_genlog.cmd

The scriptblock will not interpolate the string variable, so if you want to see it all expanded what you can do is define the scriptblock as a string, and then convert it to a scriptblock.

$sbtext = "Start-Job -Name $NTUpdate -ScriptBlock {& cmd.exe /c $executepath}"
$sb = [scriptblock]::Create($sbtext)

That should get you the results that you desire.

Upvotes: 1

Related Questions