Powershell – Having trouble passing a PowerShell variable to a command line argument

powershell

I am working on a script that takes a powershell variable and uses it in a script block running the net command.

Here is the code:

$User = "domain\user"
Invoke-Command -ComputerName $ComputerName -ScriptBlock { net localgroup administrators $User /add } -Credential $cred

When I run it, this is the error message I get:

The group already exists.
+ CategoryInfo          : NotSpecified: (The group already exists.:String) [], RemoteException
+ FullyQualifiedErrorId : NativeCommandError
+ PSComputerName        : GMCR77569

More help is available by typing NET HELPMSG 2223.

So it appears that the net command is trying to create the administrators group. I haven't found much on Google for that.

Also, I am using Invoke-Command because I need to be able to pass credentials.

I am sure this is something simple, but I cannot figure it out. Thank you in advance!

Best Answer

Because you are invoking a remote command, the script portion is trying to resolve the $User variable in the remote session. If you want to pass a variable, then you could modify your Invoke-Command with the -Args parameter. I think something like the following should work:

Invoke-Command -ComputerName $ComputerName -ScriptBlock { net localgroup administrators $args[0] /add } -Credential $cred -Args $User

This PowerShell Blog article does a good job explaining things and gives some other ways you could resolve your issue.

https://blogs.msdn.microsoft.com/powershell/2009/12/29/how-to-pass-arguments-for-remote-commands/

Related Solutions

Powershell error when adding filepath

One fix: the format and out need to follow the pipeline of the outer Foreach-Object:

$searchOU='ou=Servers,dc=mydomain,dc=NET'
Get-ADComputer -filter * -SearchBase $searchOU | 
  Foreach-Object {
    $server = $_.Name
    ([ADSI]"WinNT://$($_.Name)/Administrators").psbase.invoke('Members') | 
      ForEach-Object {
            $user = $_.GetType().InvokeMember('Name', 'GetProperty', $null, $_, $null)

            New-Object 'PSObject' -property @{'Server'=$server; 'Admin'=$user}
       }
 } | Format-Table -AutoSize Server, Name | Out-File C:\Scripts\servers.txt

Second: the error is coming from the ADSI Invoke call, probably unable to resolve the machine name.

Windows – Executing a git command using remote powershell results in a NativeCommmandError

As far as Powershell is concerned, it is the correct behaviour.

Unfortunately (at least in my opinon), git outputs a lot of information to stderr even when there isn't any error. For example git checkout -b somenewbranch will output things like modified file lists to stdout but the Switched to new branch somenewbranch message (which I think is the most relevant one) to stderr.

One of the most common ways to deal with this is to redirect stderr output to stdout, e.g:

git rebase master 2>&1

This is enough for most use cases I've seen. If you want to do something with the textual output itself you'll need to go a bit further as Powershell will store the stderr-originating lines as a RemoteException instead of a string. A brief example of how you might deal with something that needs to log output to the console:

$result  = Invoke-Expression "& git checkout -b somefeaturebranch 2>&1"

$output = ""
foreach($line in $result)
{
    $val = ""
    if($line.GetType().Name -eq "ErrorRecord")
    {        
        $val = $line.Exception.Message
    }else{
        $val = $line
    }   
    $output = "$output`r`n$val"
}

Write-Host $output

Best Answer

Related Solutions

Powershell error when adding filepath

Windows – Executing a git command using remote powershell results in a NativeCommmandError

Related Topic