Terminal services may be provided by Windows 2000 server computers. Terminal services can allow remote computers to run desktops and applications on a server as though it is running locally. This is similar to the functionality provided by X on UNIX and Linux platforms. Keystrokes and mouse action information is sent from the client to the server over the network and visual display information is sent back to the client from the server. Terminal services offer the following advantages:
No license is required for remote administration mode, but licensing is required for application server mode. The application server mode will run for 90 days without a license. Licensing is done on a per seat basis which means there must be a license for each computer that will access the terminal server. To set up licensing:
Required licenses:
Additional licenses that may be purchased:
Terminal Services licensing uses the Microsoft Clearinghouse database to verify licensing.
The control panel "Add/Remove Programs" applet is used to install terminal services. Select "Add/Remove Windows Components", and select "terminal Services". Set up terminal services in remote administration mode or application server mode during installation. Another option is to make permissions compatible with Windows 2000 users or make permissions compatible with Terminal Server 4.0 users. The former setting is more secure, but most legacy applications won't run with that setting. If running in application server mode, the recommended server hardware includes:
Components that are installed when Terminal Services is installed:
Win16 on Win32 (WOW) is used to translate 16 bit applications to a 32 bit operating environment by terminal services. Running 16 bit windows or MS-DOS applications is not recommended since it will cost additional processing power and memory due to the overhead of rinning the Win16 or DOS virtual machines.
Applications to be used with terminal services must be installed after terminal services is installed. The applications must be installed in a multiuser format and on an NTFS partition. Terminal Services must be in "Install Mode" when an application is being installed. Once applications are installed, to run applications from terminals, Terminal Services must be in "Execute Mode". The control panel "Add/Remove Programs" applet is used to install the applications. Procedure:
The Change User command prompt command can also be used to install applications, but should be used to set up or confirm multiuser access capability for the application.
The most secure terminal services permissions mode is "permissions compatible with Windows 2000 users".
The Terminal Services Client uses Remote Desktop Protocol (RDP) to connect to the server. Supported client systems:
The Terminal Services Client creator was installed with the Terminal Services. This can be used to create a floppy disk for Win32 or Win16 systems to get the Terminal Services Client to the client machines. Another method is to share the terminal services directory in SystemRoot\system32\clients\tsclient\net\Win32 or Win16 and access the software across the network. The Windows for Workgroups system must use the Win16 folder.
Commands:
| Command | Meaning |
|---|---|
| change logon | Used to disable, enable, or check the status of logons |
| change port | Modify DOS com ports or query for the status of ports. |
| change user | Change .ini file mapping for the current user. Applicable change user parameters are install, execute, and query. |
| cprofile | Remove user's profile file associations |
| dbgtrace | Enable or disable debug tracing |
| flattemp | Enable or disable temporary flat directories |
| logoff | End a client session |
| msg | Send a message to a client |
| query process | Display process information |
| query session | Display terminal services session information |
| query termserver | Display terminal server list |
| query user | Display logged on user list with information. Like "who" in UNIX. |
| register | Register a program |
| reset session | Reset or delete a terminal session. |
| shadow | Monitor or remotely control a Terminal Service session |
| tscon | Start a Terminal Services session |
| tsdiscon | End a Terminal Services session |
| tskill | Terminate a Terminal Server process |
| tsprof | Change a user profile path or copy user information |
| tsshutdn | Shut down a terminal server. |
The Terminal Services Manager is a graphical based administrative tool used to manage terminal services. It is used on the terminal server or on a client during a session. It will perform the same functions as the command set listed above. The most important functions include using remote control and monitoring and managing terminal services usage. The remote control ability will allow the administrator to take over a user's session. The user's remote control tab of the user's properties dialog box in "Active Directory Users and Computers" determines if the administrator can remotely control a user's session. Additionally it allows:
This is the Administrative Tool called "Terminal Services Configuration". To open the RDP-Tcp properties sheet, click on connections, right click on "RDP-Tcp", and select "Properties". The properties RDP-Tcp properties dialog box tabs are:
Terminal Services can be used to remotely administer the server computer, but Microsoft recommends setting the following parameters:
These are settings in Active Directory Users and Computers that affect user Terminal Services sessions.
User's Properties Dialog box Tabs:
The client can end a session by using the hot key combination that they selected.