Well, you might be able to accomplish this, but there are some caveats.
The Deployment feature of BatchPatch will not allow you to execute the remote process interactively.
However, Remote Commands 1 and 2 do support psexec switches, and so they WILL let you specify the -i switch to execute processes interactively. That said, the file to execute would have to already exist on the target machine (or you might be able to use the psexec -c switch to get the file there – haven’t tested it).
There are a couple of things to be aware of if you try this…
First, if you use -i without also specifying -d, then psexec and consequently BatchPatch will wait for the process to complete. You probably don’t want this, so you would generally want to use -d in addition to -i. When you do this the exit code that appears in BatchPatch should be the PID of the remote process.
Second, the way Windows deals with multiple desktop sessions can give you unwanted results. For example, if you use -i to execute a process interactively on a non-server OS, like Windows 7, it will work as expected if you’re sitting at the console. But if you are using an RDP session to the Windows 7 machine, you probably will not see the process, and instead it will still run hidden. On a server OS you might be able to deal with this by connecting to the console session using the /admin switch in the RDP client. However, I’m not positive if this will work, so you’ll want to test.
I hope this helps.
-Doug