Start a bat file on remote PC

Question

I am trying to execute a .bat or .cmd file on a remote pc with this:

PSEXEC \\192.0.0.230 "\Users\James\Desktop\BatchFiles\StopStart.cmd"

This will Disable a NIC and Enable another NIC, problem is, it ignores the timeout /t 10, because instead of opening the file on the remote computer, it runs the commands written in the batch file instead. So if it Disables the first NIC it will lose connection meaning it can't enable the other NIC. But if it can just run the file and let the lines run on the remote PC instead, this is not a problem, because then even if I lose connection due to the NIC being disabled, it should just keep running the .bat file on the remote PC instead of running the commands written in it from my own PC.

Is this possible? Thanks.

Answer 1

You might be able to use schtasks. I haven't tried this, but something like this might work:

schtasks /create /s SRV01 /tn MyApp /tr "cmd /c c:\path\to\my.bat"
schtasks /run /s SRV01 /tn MyApp

You can have a look at Microsoft reference for schtasks commands for more details.

Answer 2

Maybe you can use a second short script (that you launch with psexec instead) to have the remote machine copy that batch file locally, then in the last line use call to start that second local batch file copy (for example copied to %temp%)?

It'll lose connection to the network location, but as "call" was on the last line, that doesn't matter anymore.

Answer 3

If you have access to Powershell on both machines, you may be able to use Invoke-Command or Invoke-CommandAs to run the command

This admittedly might be more powerful than a regular .bat execution, but based on past experience, would be how in automation environments we've had our Jenkins instances run commands remotely on nodes from the Jenkins host server machine.

In Powershell, there's an Invoke-Command option, which since I last looked at it, appears to have added additional parameters for running effectively as another user on that remote machine (I'm more familiar with the Invoke-CommandAs additional installation component, so I'm not 100% of this particular solution.). That said, based on the documentation there, the following is an example I'm copying here in case that link dies, and for quick reference.

Invoke-Command -FilePath <Path_To_Script*> -ComputerName <ComputerName**>

If, however, you're hoping to use the Invoke-CommandAs approach, this works from at least Powershell version 3.0, as I understand.

That would then look like this:

Invoke-CommandAs -ComputerName '<ComputerName**>' -Credential $Credential -ScriptBlock { Get-Process }

Or:

Invoke-CommandAs -ComputerName '<ComputerName**>' -AsUser $Credential -ScriptBlock { <Path_To_Script*> }

* i.e. "c:\scripts\test.ps1" in their example, or in your case, "\Users\Bridge\Desktop\BatchFiles\StopStart.cmd" - just be sure to remove the angled brackets in the code examples above.

** NETBIOS name, IP address, or fully qualified domain name of one or more computers in a comma-separated list. If using an IP Address, you must also provided a Credential parameter, along the lines of, for example -Credential Domain01\User01

Answer 4

Please open Remote Desktop Connection and log into the system from there.

You'll then be able to run whatever program you use.

I was nearly able to run GUI programs in WSL 2.0 on Windows 10 Pro via using the above.

If this doesn't work, please advise as such.