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.
The following is a screenshot of the terminal server licensing console demonstrating what you would have to do to start the activation process. Activation of the licensing server can be done via a direct connection to the internet, a web browser or over the telephone. You will have to activate the server before it can start distributing licenses. Once you have installed this option your server will be listed in the terminal server licensing console. This can be done from the windows components wizard section in the add/remove window from the control panel.
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 We continue by pressing the “Next” button.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). I select the RDSH and RDL roles to continue with the installation. Firstly, our license is device-based, and our second license is based on user-based needs and demands, you can continue your use by choosing user or device-based license models. Two different types of licenses are available for RDS. Once your 120-day RDS role expires, you will need to purchase a license to continue using the service.
Microsoft offers 120 days of free use for this role.
You can install and test for free on Windows Server Roles and Features. The RDS role is offered by Microsoft as an additional licensed product.
Ur RDL service provides license management services for our RDS role infrastructure. After examining the relevant step, click the “Next” button. Featuresįrom the “Remote Desktop Services” step it gives you a brief overview of the capabilities and usage of this role. If you are going to use it only for RDS, continue by pressing the “next” button without selecting any features.
You do not need to do anything in the “Features” step, but if you are going to install a different software after RDS, such as ERP, CRM, you can select the extra features you think you need from this section.