Well, it would be easier if you had UFT installed on the remote machine, then you could use UFT's Automation Model to remotely execute the script which would run a SystemUtil.Run ''batchfilename.bat'' or something similar.
I did find an article that talks about using WMI events to kick off remote files like in this example:
This example runs the batch file C:test.bat located on the remote computer TEST-MACH1.
strComputer = ''TEST-MACH1''
Set objWMIService = GetObject(''winmgmts:\'' & strComputer & ''rootcimv2:Win32_Process'')
objWMIService.Create ''C:test.bat'', null, null, intProcessID
You can find a lot of more details if you are interested on this website:
http://blogs.technet.com/b/heyscriptingguy/archive/2006/12/08/how-can-i-start-a-process-and-then-wait-for-the-process-to-end-before-terminating-the-script.aspx
Of course, this is not an officially supported solution, so your success may be limited and you would be on the hook for supporting your code that you use.
Good luck.