Problems starting windows application remotely

[galactus08]

Hello,

I have been trying to kill and start an application remotely. The kill part isn't an issue. Starting requires access to a USB license dongle. If I connect to terminal services with a mstsc console session, the application starts properly, including an icon in the application / system tray. I need to be able to automate this process remotely from a Linux server. I have tried using the telnet server from SFU in console mode (using expect on the Linux side), the WinRSH server in SFU (trying to rsh in to start it), and the std telnet server. In all cases the process gets started, but the icon doesn't show up and the program is unresponsive. I suspect that when coming in remotely something is preventing access to the USB dongle. Is there a registry setting or something that may change this behavior? Any input greatly appreciated. I have been banging my head on this far too long. Much thanks.

 

[itsp1965]

Here's a thought.. don't know what Linux distro you are using, but have you considered using rdesktop from the Linux box to connect to your application instead?

 

[allywilson]

Try using psexec.exe from SysInternals (neé Microsoft).

It allows you to remotely execute commands from one workstation to another.

Also, it might be worth investigating as to whether it's a profile thing (try "runas /noprofile /user:domain\username 'whatever.exe'")

 

[galactus08]

Thanks for the responses. I appreciate it. psexec may be the long term way to go on this and I will look into it.

In the meantime I was able to get around the issue by adding a scheduled task to 'run once' and then setting the runtime to a date in the past. I can now rsh in and use the schtasks command to start up and it looks to be working.

Thanks for your help.