What about running that command through Task Scheduler, which is built-in at any Windows?

Are you trying to pass the command line arguments to the program AS you launch it? I am working on something right now that does exactly this, and it was a lot simpler than I thought. If I go into the command line, and type

C:\folder\app.exe/xC:\folder\file.txt

then my application launches, and creates a file in the specified directory with the specified name.

I wanted to do this through a Powershell script on a remote machine, and figured out that all I needed to do was put

$s = New-PSSession -computername NAME -credential LOGIN
    Invoke-Command -session $s -scriptblock {C:\folder\app.exe /xC:\folder\file.txt}
Remove-PSSession $s

(I have a bunch more similar commands inside the session, this is just the minimum it requires to run) notice the space between the executable, and the command line arguments. It works for me, but I am not sure exactly how your application works, or if that is even how you pass arguments to it.

*I can also have my application push the file back to my own local computer by changing the script-block to

C:\folder\app.exe /x"\\LocalPC\DATA (C)\localfolder\localfile.txt"

You need the quotes if your file-path has a space in it.

EDIT: actually, this brought up some silly problems with Powershell launching the application as a service or something, so I did some searching, and figured out that you can call CMD to execute commands for you on the remote computer. This way, the command is carried out EXACTLY as if you had just typed it into a CMD window on the remote machine. Put the command in the scriptblock into double quotes, and then put a cmd.exe /C before it. like this:

cmd.exe /C "C:\folder\app.exe/xC:\folder\file.txt"

this solved all of the problems that I have been having recently.

EDIT EDIT: Had more problems, and found a much better way to do it.

start-process -filepath C:\folder\app.exe -argumentlist "/xC:\folder\file.txt"

and this doesn't hang up your terminal window waiting for the remote process to end. Just make sure you have a way to terminate the process if it doesn't do that on it's own. (mine doesn't, required the coding of another argument)

psexec \\RemoteComputer cmd.exe

or use ssh or TeamViewer or RemoteDesktop!

Hi, given that this post has been quiet for a while, this is a quick question and answer. Has your question been solved? If so, please mark it as an answer so that users with the same question can find and get help.
（ Does the latest problem idea from RichMatheisen-8856 help you? ）

you need to add credential as well to run that exe.(Pass the credential in PSEXEC command) Make sure that your account also has the write and modify permission at the location at which file is being generated

I am trying to create either a VBS or CMD script that will allow me, to run an executable that is already located in the same location on every single machine we have, there is a folder to the .exe that is the same location on each machine and instead of walking around to 300 machines, i’d like to just have it run from my desk.

Group Policy is out of the question because not all machines are defined in AD.

I wanted to use the script reference a list of IP’s.

Is that possible or anyone have something similar i could use?

Thanks!

I’ve got the .exe copied locally to a remote computer but I can’t get the command correct to trigger it to run on the remote computer. The .exe is located on the remote computer at c:\folder\file.exe. Any help is appreciated.

I think you've a problem with your local/remote execution.

(Get-WmiObject win32_process -ComputerName $computer -Credential $mycreds | ?{ $_.ProcessName -match "Workbench3.helper" }).Terminate()

Above line returns all processes from the remote computer to your local computer. Than you're fitering the returned process-objects on your LOCAL machine, and call Terminate() on your LOCAL machine. I would suggest you use the following line instead:

Invoke-command -session $pers -ScriptBlock { (Get-WmiObject win32_process -ComputerName $computer -Credential $mycreds | ?{ $_.ProcessName -like"*Workbench3.helper*" }).Terminate()}

This should kill the Workbench3 process(es). I used the like operator to make filtering less strict.

After that, you can reuse the session stored in $pers to start the process again.

Invoke-command -session $pers -scriptblock {Start-Process -filepath "C:\Program Files (x86)\Company Security\Workbench3 Helper\WorkBench3.Helper.exe" -Wait }

I additionally used the -Waitswitch. The switch forces Start-Process to wait for the programm to be started (and return afterwards).

When doing remote operations I would always suggest to perform these operations via Invoke-Commandand not via the -ComputerName parameters of the several commands. Invoke-Command uses WS-MAN via HTTP(S), while the remote-implemenation of commands offering the -ComputerNameparameter differ in implementation from cmdlet to cmdlet. This advantage of invoke-commandmakes it easier to configure e.g. firewalls.

Hope that helps.

On more option is the built in winrs

winrs.exe -r:<RemoteComputerName> <TheCommandToRun>
winrs.exe -r:MyRemoteServer ipconfig

winrs vs. psexec

advantages winrs

• Built in, no download needed
• Faster and more reliable than psexec

advantages psexec

• Works with IP (winrs needs the computername (NetBIOS name) of the machine)
• Can run processes in system-context