Summary

The user interface for a program, script, etc. run by adTempus or the Arcana Scheduler is visible only if you are logged in to the "console" session for the computer. If you are connected to the computer using Terminal Services or Remote Desktop, you will not be able to see the program's user interface.

More Information

Using Terminal Services or Remote Desktop, Windows allows more than one user to be connected to a computer at the same time. Each connected user is hosted in a separate user session, which is isolated from all other sessions.

Each computer has a "console" session, which is either the session for the user physically at the computer, or a remote session configured to connect to the console session.

When adTempus or the Arcana Scheduler runs a job that is configured to allow user interaction, the program is run in the console session. Therefore, only the user logged in to the console session can interact with the program. If you are connected to a different session, you will not see the program's user interface.

Connecting to the Console Session

To view interactive programs, you must be connected to the console session. You can do this in one of three ways:

  • Log in at the computer itself (i.e., the monitor and keyboard physically attached to the computer).
  • Use Remote Desktop/Terminal Services to connect to the console session. By default, when you connect to the computer through Remote Desktop or Terminal Services, Windows creates a new session for you, and does not connect you to the console session. However, it is possible to connect to the console session as described in Microsoft Knowledge Base article How to Connect to and Shadow the Console Session with Windows Server (278845).
  • Use another remote access tool such as VNC or pcAnywhere that connects to the console session.

Running Programs in a User Session

Beginning with version 3.0, adTempus has the ability to start programs in a user's logon session rather than the console session. See article K00000294 for more information.

Changes in Windows Vista, Windows Server 2008, and Later

Beginning in Windows Vista and Windows Server 2008, the behavior and availability of the console session have changed. See article K00000369 for more information.