Select whether or not to always use the same credentials for logging on, enable ‘always prompt for password’
The following table will describe what actions you may take on each tab.Īdd a comment, change the encryption level, enable standard windows authentication Double click a connection to open the properties page. The screenshot below is that of the Terminal Services Configuration.Īny connections that have been setup will be displayed in the connections part of the console. These will be listed in the ‘All Listed Servers’ node. You are able to connect to multiple terminal servers by press Actions > Connect to computer. ‘Favorite servers’ will list all the servers that you have added as a favourite - you can do this by right clicking a server and selecting ‘add to favorites’. Note: The #12 number will be different for each session. If you select the RDP-Tcp#12 (username) option you can view the processes and session information specific to that user.
The image below shows the Terminal Services Manager with an active connection initiated by a user (andrew). Select a user, click the right mouse button and choose ‘end process’ to kill the process. The processes tab shows all the processes that are running and which user they belong to (this is a simplified version of the processes tab found on the windows task manager). You can right click a session and select the status to see the incoming and outgoing data or reset to reset the session. The Sessions tab permits the viewing and control of the terminal server sessions. If you select a user and right click you can disconnect or reset the user’s session, send a message (which will be displayed as a pop-up message box on the client side), view the status or log the person out of the terminal server session. The Users tab allows you to see who is connected, how long they have been connected and the state of their connection. If you had to disconnect it, the icons would be gray. The green icons indicate that the server is online. When you select the server name you can choose to view and manage the Users, Sessions or Processes tab.
To make your machine a terminal server license server you will have to install it separately. Microsoft have introduced a ‘per user’ license to add to the already familiar ‘per device’ method.
This is probably where the most changes have been made. If you do not obtain a license within that period then terminal services clients will no longer be able to initiate a session. It is important to take note that a 120-day evaluation period has been allocated for unlicensed clients. After the machine has booted and you logon, you are presented with a confirmation screen that states the computer is now a terminal server. The installation will continue for a few minutes before the machine is restarted. The wizard will then start to install the required files and warn you that the machine will have to be restarted during the installation process. Open the ‘configure your server’ wizard from Administrative Tools and in the select a role section, choose Terminal Server and click Next twice to confirm your actions.
Setting up Windows 2003 as a Terminal Server To benefit from these new features, the terminal services client must be using RDP 5.1 (included in Windows XP) and the server must have RDP 5.2 (included in Windows 2003).