WinBatch Tech Support Home

Database Search

If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.

TechHome

Miscellaneous

Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.

Winbatch Running in Disconnected Citrix Session


Question:

I was wondering if anyone has experience running a WinBatch program in a disconnected Citrix session. I wrote a program that schedules programs to run at specific times on a Citrix farm. It uses TimeYmdHms to get the current time and compare it to the time that I set for the job to run.

The thought process was that I would run the scheduling program in a session on the Citrix farm, then disconnect from the session. The scheduled program then would kick off at the specified time. It does not seem to work that way. Apparently the scheduled program starts only when I reconnect to the disconnected session.

Any help will be appreciated.

Answer:

I've had scripts running in a session that accidentally went into a disconnected state due to a network problem, but always re-connected again immediately to continue the session. I can't say that I've deliberately tried to run a script in a session that stays disconnected all of the time.

At a guess, I'd think that a disconnected session would be functionally equivalent to being on a WinNT/2K/XP/03 system which is locked. The "default" desktop is not the current desktop because the session doesn't have a keyboard & mouse present while in the disconnected state. That shouldn't prevent a program from continuing to execute in the session, but it will prevent all activities that are dependent upon the keyboard & mouse being present [e.g. SendKey(), SendKeysTo(), MouseMove(), etc...].

A simple test would be to write a script that doesn't do anything at all except update the timestamp on a file once every 15 or 20 seconds and run the script and then disconnect the session. Then, from another session or from a remote workstation, check the timestamp on the file to see if it is in fact being updated. That will tell you if your script is continuing to execute. --------------------------------------------------------------------------------


Article ID:   W16508
File Created: 2005:02:18:12:21:06
Last Updated: 2005:02:18:12:21:06