Using PSExec

[Tigerweld]

Can anyone tell me why this won't run?  I know I have to be close to makeing it work.

$ipAddress = InputBox("IP or Host", "Enter IP or Hostname","","")
$sRemoteLocalPath = "c:\temp\"
$LocalFile = "uninstall_java.bat"

Run('PsExec \\' & $ipAddress & ' "' & $sRemoteLocalPath & $LocalFile & '"', '', @SW_HIDE)

[JLogan3o13]

Tigerweld, can you please provide a little more insight as to what you mean by "won't run"? The code seems to be working just fine for me; you simply did not provide a way to capture the return from psexec. Is that what you are after, or are you receiving an error?

[Tigerweld]

After I enter the ip address for the input box nothing happens.  No error or anything.  Running the script from a windows 2008 server on a windows 7 workstation with domain admin rights.

[JLogan3o13]

PSExec is a command line tool. If you want some visual representation of what it is doing, you have to code that in. Try this to illustrate what I mean:

$ipAddress = InputBox("IP or Host", "Enter IP or Hostname","","")
$sRemoteLocalPath = "c:\temp\"
$LocalFile = "uninstall_java.bat"

Run('C:\PsExec.exe \\' & $ipAddress & ' ' & $sRemoteLocalPath & $LocalFile & ' > C:\Temp\My.log', "", @SW_HIDE)

Notice that it outputs to a log file - you'll find this in the temp directory on the machine you're connecting to. You can choose another location for the log file, but this should illustrate what I'm getting at.

Edited May 20, 2013 by JLogan3o13

[Tigerweld]

It still isn't working.  I can run just the psexec from a comand prompt and it works, but running psexec inside Autoit does not work.  Maybe it cannot be done.  Thanks for helping.

[JLogan3o13]

It can be done. The script that I provided works for me. I would suggest you begin by removing the variables from your script. Something like this:

Run('C:\PsExec.exe \\10.10.10.1 C:\Temp\Uninstall_java.bat > C:\Temp\My.log', "", @SW_SHOW)

If that works, it has something to do with the way you're dropping your variables in there.

[BrewManNH]

What do you get if you don't use @SW_HIDE and use @ComSpec /k?

Run(@ComSpec & ' /k C:\PsExec.exe \\' & $ipAddress & ' ' & $sRemoteLocalPath & $LocalFile & ' > C:\Temp\My.log')

Never use @SW_HIDE until you know the command is working the way you want it to. Otherwise, you're just guessing as to what is happening.

[Tigerweld]

JLogan, that works when I do that.  So how can I add my variables?  Is there a way to place the path in just one varible and use that?

[Tigerweld]

BrewMan it gives me a 'psexec.exe' is not recognized as an internal or external command.

[BrewManNH]

Use the full path to where the program is located, that was an example.

[JLogan3o13]

Add the variables in one at a time to figure out which one is causing you the problem. Go from this:

1.Run('C:\PsExec.exe \\10.10.10.1 C:\Temp\Uninstall_java.bat > C:\Temp\My.log', "", @SW_SHOW)

To this:

1.Run('C:\PsExec.exe \\' & $ipAddress & ' C:\Temp\Uninstall_java.bat > C:\Temp\My.log', "", @SW_SHOW)

If this works, add the next variable:

1.Run('C:\PsExec.exe \\' & $ipAddress & ' ' & $sRemoeteLocalPath & 'Uninstall_java.bat > C:\Temp\My.log', "", @SW_SHOW)

It's called troubleshooting

Edited May 21, 2013 by JLogan3o13

[jdelaney]

I also like to do logging of the run command, just before the execution, so I can check it's syntax.

ConsoleWrite('C:\PsExec.exe \\' & $ipAddress & ' ' & $sRemoeteLocalPath & 'Uninstall_java.bat > C:\Temp\My.log' & @CRLF)

Usually, something small, like forgetting a "", or omitting a space, somewhere.

[JLogan3o13]

Same here, jdelaney. I typically do it in a MsgBox, but same concept. Can't count the number of times I have banged my head against my desk over what turned out to be one too many or one too few spaces in a line.