Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I am trying to use the powershell call operator to essentially run the following command:

"C:\Program Files (x86)\PuTTY\plink.exe" "-v -agent -m C:\Scripts\idrac_powerup_commands.txt root@[servername]"

Current Code

$runputtyscript = @()
$runputtyscript += "-v"
$runputtyscript += "-agent"
$runputtyscript += "-m C:\Scripts\idrac_powerup_commands.txt"

& 'C:\Program Files (x86)\PuTTY\plink.exe' $allArgs root@servername

Problem

This executes, but the script doesn't execute the file with the commands the same that it does if the original string was executed from the command line.. It shows me the admin console (so it has logged in, authenticated with the public key, etc.) but it just hasn't run the script I asked it to run.

Things I've tried

  • Moving the filename component of -m to its own argument
  • Putting quotes around the filename component of -m

Question

Maybe more succinct way of asking: What is the proper way to use arguments that then have their own arguments (e.g. "-m [filename] -v -a" with the call operator (&) in powershell?

share|improve this question

2 Answers 2

For some reason, writing it in the following way causes it to work perfectly from a powershell prompt, and from a command prompt calling powershell.exe C:\Path\To\Script.ps1

& 'C:\Program Files (x86)\PuTTY\plink.exe' -v -agent -m C:\Scripts\idrac_powerup_commands.txt root@servername | Write-Host

Go figure.

share|improve this answer

You may be running into the case where your variable is not being handled by the Win32 binary. You can ease this along through double-quotes:

'C:\Program Files (x86)\PuTTY\plink.exe' "$allArgs" root@servername

I had the same problem with netsh a while back.

share|improve this answer
    
Interestingly enough, that didn't fix it, but writing out the entire string does...from the command line. See my answer. It works for the console, and when I call powershell.exe C:\Scripts\script.ps1 but doesn't work from a scheduled task (which I think is a separate problem) –  SeanKilleen Feb 8 '13 at 13:07

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.