Passing Parameters to a PowerShell Script in MDT 2013

Question

I have a PowerShell script that takes an array as an input parameter:

Param( 
    Parameter(Mandatory=$true)]
    [System.String[]] $Adapters
)
Write-Output "Disabling network adapter(s)."
foreach ($adapter in $Adapters) {
    Disable-NetAdapterBinding -Name $adapter -ComponentID ms_tcpip6  
    Write-Host $adapter
}

I get the following error when I call the function from an MDT 2013 task sequence:

+ ..."E:\Deploy\Scripts\Disable-IPV6.ps1" -Adapters @(Teamed_NIC1, Teamed_...
    Missing argument in parameter list.

This is what my call to the function in MDT 2013 looks like:

$PowerShell script: <code>%SCRIPTROOT%\Disable-IPV6.ps1</code>; Parameters: <code>-Adapters @("Teamed_NIC1", "Teamed_NIC2")</code>$

I suspect that MDT is handling the quotation marks in an unexpected way.

In the parameters block, try calling like this --> `-Adapters "Teamed_NIC1" "Teamed_NIC2"` — Vivek Kumar Singh, Mar 05 '18 at 15:53
@VivekKumarSingh That would invoke the script with one named parameter (`-Adapters "Teamed_NIC1"`) and one unnamed parameter (`"Teamed_NIC2"`). — Ansgar Wiechers, Mar 05 '18 at 16:57
Yes @AnsgarWiechers - I realize that now, looking at your answer. Thank you for pointing that out and educating us folks. :) — Vivek Kumar Singh, Mar 06 '18 at 10:02
@AnsgarWiechers Good clarification. The key part I needed was _is only recognized within PowerShell_. — BFerg, Mar 06 '18 at 20:13

Ansgar Wiechers · Accepted Answer · 2018-03-05T16:54:46.930

@("Teamed_NIC1","Teamed_NIC2") is a PowerShell array. That construct is only recognized within PowerShell, but not by the environment from which you invoke the PowerShell script. The same applies if you remove the @().

You cannot really pass array values to a parameter when invoking a PowerShell script from outside PowerShell. A common workaround is to pass the argument as a delimited string and split it:

Param(
    Parameter(Mandatory=$true)]
    [String]$Adapters
)
$AdapterList = $Adapters -split ','
foreach ($adapter in $AdapterList) {
    ...
}

with an invocation like this:

%SCRIPTROOT%\Disable-IPV6.ps1 "Teamed_NIC1,Teamed_NIC2"

Or you can drop the parameter definition and use the automatic variable $args:

if (-not $args) { throw 'Missing argument.' }

foreach ($adapter in $args) {
    ...
}

with an invocation like this:

%SCRIPTROOT%\Disable-IPV6.ps1 "Teamed_NIC1" "Teamed_NIC2"

Thanks! I knew it'd be something simple like this. – BFerg Mar 05 '18 at 16:27 — BFerg, Mar 05 '18 at 16:27

Passing Parameters to a PowerShell Script in MDT 2013

1 Answers1