Note that there is a different between disconnecting and ending a session. When disconnected, a session is still running on the server and can be reconnected later. When ended, the session is removed from the server completely. To disconnect a session, the user simply needs to close the session window. To end a session, the user should choose to log off as if they were sitting at an actual Windows 2000 client.
Windows 2000 terminal services also provides the ability to remote control user sessions, but only terminal service sessions. As such, an administrator can remotely take control of a user’s terminal session, in order to help the user through a task or something similar. By default remote controls enabled, but requires the user’s permission to access a session:
The actual management of all sessions is handled via the Terminal Services Manager administrative tool,which allows you to send console messages,disconnect sessions, view connected users, and view process activity.
When exploring terminal services, it is also important to note that not all applications will function correctly in this simultaneous multi-user environment. As such, for some applications you will be required to first run an application compatibility script in order for it to function correctly. A number of these scripts are provided,and can be found in the %systemroot%\Application Compatibility Scripts\Install folder. Another note– when installing applications on a terminal server, you should be sure to use Add/Remove programs in control panel, since this will ensure that the application is installed for all users.However, when installing items that cannot be installed in this manner (such as a web browserplug-in), you will need to run the change user command. To do this:
- Run the command change user /install prior to installation
- Install the application
- Run the command change user /execute after the installation
This will ensure that the program is available to all users. Add/Remove programs runs both commands automatically.
