RDP Task Scheduler problem

We need to restart a program every day at 5:30am (Kronos timekeeping system). On our stand alone PC's we use the 'Task Scheduler' to run a batch file that uses kill.exe to end the previous instance of the program, browse to the directory of the application, and re-launch the application.

We are now trying to use Remote Desktop Protocol with Thin client technology. We have been trying the same approach as above but ran into a problem. The kill.exe call functions properly (killing only the current user's program) but when restarting the program it is launched in the Console (sessionID 0)'s memory space, not the current user's, and is not displayed on the terminal's monitor (or the console's monitor for that matter). Any info on this problem would be greatly appreciated!

ps
Windows 2000 Server
ComputerLabs ET3000 terminals using RDP
...ask if you need more info

 

Using the /INTERACTIVE switch with AT or SOON will make the task appear in the console session (but not the user session).

I suppose you could launch your batch commands in a logon script running in the background and calaculate how long to sleep before running kill.

 

Thanks for the response and sorry for not checking it for a few days.

I found a different solution in using a third party application called Windows Scheduler. It wasn't perfect but by removing all permissions, save for the user who needs it, from the *.ini files (where the schedule is stored with this program) it restarts our programs, in the proper session, without launching in the console.