Terminal Services is a feature available on Windows server platforms such as Windows 2000 Server. In Windows NT, these services were included only in Windows NT Terminal Server. Terminal Services functionality is not installed by default; the system administrator must explicitly install and enable it. Once installed and enabled, these services allow a single computer to host multiple simultaneous user sessions.

Although each session has its own desktop, they all share the same set of system services and resources.

Since Automate is a system based software service as opposed to a user-based software application, there are a few important issues to be aware of when using Automate in a Terminal Services environment.

In a Terminal Services environment there are two types of sessions. Automate behaves differently depending on what type of session it is running in.

Console Session

A console session is a traditional windows session that occurs as a result of logging onto the physical server.

Automate functionality
Automate is capable of functioning normally when being used from the console. Tasks can be edited, created, deleted and run. The tasks will run on the current session.

Remote Session

A windows session on a terminal services enabled computer takes place from a remote location using the Terminal Services client, or Windows XP Remote Desktop Connection client.

Automate functionality
When running under a Remote session, Automate operates differently. Tasks can be edited, created, and deleted. If a managed task triggers or is run from the Task Administrator, however, the task will run on the console and not the Remote Desktop. If the console is logged out, the properties specified in the Run As tab of the task properties will be applied. Tasks can be run for debugging purposes using the Task Builder only.

Task will not trigger as a result of conditions on a remote session. For example, the Key Watcher trigger will not trigger a task as a result of keystrokes typed during a remote session. Additionally, the Window Watcher trigger will not trigger as a result of open windows on a remote session. Only the console session is monitored for trigger conditions.

Applies To: Automate 5, Automate 6 

Still have questions? We can help. Submit a case to technical support

Last Modified On:
You don't have the appropriate permissions.
No, open a new Support Case