Server 2008 R2 Terminal Server Setup - Remote Desktop Services
Installing Terminal Services on Server 2008 R2
This article details the process of installing Terminal Services, also referred to as Remote Desktop Services, on a server running the Server 2008 R2 operating system.
It’s important to recognize that this guide is presented as part of a larger curriculum focused on fundamental IT administration principles.
Understanding Terminal Services
Terminal Services allows users to remotely access and control a server's desktop environment. This functionality is crucial for remote administration and providing centralized application access.
Alternatively known as Remote Desktop Services, this feature enables efficient management of server resources from various locations.
Installation Steps
The installation process is straightforward and can be completed through the Server Manager console.
- First, open Server Manager.
- Select “Roles” from the left-hand navigation pane.
- Click “Add Roles” to begin the installation wizard.
Configuring the Role
Within the Add Roles Wizard, select the Terminal Services role.
The wizard will prompt you to add any required features. Accept the defaults and proceed.
Completing the Installation
Review the installation selections and confirm to initiate the installation of Terminal Services.
Once the installation is complete, the server may require a reboot to fully activate the service.
Further Considerations
This installation provides the base Remote Desktop Services functionality. Additional configuration, such as user permissions and licensing, may be necessary.
Remember that this guide is intended for those building a foundation in IT administration, and specific needs may vary depending on the environment.
Understanding Terminal Services (Remote Desktop Services)
Beginning with the release of Server 2008 R2, Terminal Services was rebranded as Remote Desktop Services. Commonly referred to as RDS, this technology enables the utilization of a robust server to which multiple users can connect simultaneously via the Remote Desktop Protocol (RDP).
Consider it a centralized computer accessed remotely by numerous individuals. Each user maintains a distinct session and desktop environment, operating independently of others.
Applications are installed only once on the server, yet remain accessible to all authorized users. Users can establish a connection utilizing the Remote Desktop Connection Manager integrated within Windows, or frequently, through thin clients.
In fact, connectivity is possible from any device supporting the Remote Desktop Protocol. For organizations seeking cost savings and possessing older hardware, Microsoft’s Windows Thin PC offers a solution, effectively transforming existing machines into thin client devices.
Important Considerations
Several factors require careful attention when implementing RDS. These include licensing requirements and application compatibility.
- Application Licensing: Not all software is suitable for installation on a Remote Desktop Server. For instance, Office 2010 necessitates a Volume License version for proper functionality on an RDS server.
- Client Access Licenses: Accessing an RDS Server requires appropriate licenses, available as either Per User or Per Device Client Access Licenses (CALs). These licenses authorize connections from more than a single user.
Purchasing CALs generally proves more economical than acquiring individual Windows 7 licenses for each user.
It’s crucial to remember that applications intended for use on the Remote Desktop Server should not be installed prior to the installation of the Remote Desktop Session Host Role.
Installation should occur after the role has been successfully implemented.
Implementing Remote Desktop Services
Initiate the installation process by opening Server Manager. Subsequently, right-click on the 'Roles' section and choose 'Add Roles' from the displayed menu.
Advance to the next stage by clicking 'Next' on the 'Before You Begin' screen. This action will reveal a comprehensive list of available Roles. Select 'Remote Desktop Services' from this list and proceed by clicking 'Next' again.
On the 'Introduction To Remote Desktop Services' page, click 'Next'. This will navigate you to the 'Role Services' page. Select both 'Remote Desktop Session Host' and 'Remote Desktop Licensing Service', then click 'Next' to continue.
The 'Application Compatibility' page advises installing the Session Host Role prior to application installations. Click 'Next' as applications haven't been installed yet. You will then be prompted regarding Network Level Authentication (NLA).
Enabling NLA restricts connections to only Windows clients utilizing a Remote Desktop Client that supports Network Level Authentication. NLA is recommended for enhanced security. Proceed by selecting the option to require NLA and then clicking 'Next'.
The next step involves selecting a licensing approach. Many users will not initially possess Remote Desktop Client Access Licenses. Therefore, the option to 'Configure Later' can be chosen. This grants unrestricted access to the Remote Desktop Server for a period of four months, equivalent to 120 days.
However, if licenses are available, the following information will assist in making an informed decision:
Licensing Options
Purchased licenses can be deployed using either a Per User or Per Device model. The selection is dependent on your specific needs. If an RDS Licensing Server is already in place, consistency with the original license import settings is recommended.
- RDS Per User CAL – A license is required for each user connecting to the RDS Server. The license is assigned to the user, irrespective of the devices they utilize for connection. This is ideal for users accessing the server from multiple computers or devices, such as iPads, personal computers, laptops, or smartphones.
- RDS Per Device CAL – This model assigns licenses to devices rather than users. Multiple individuals can connect from a single device. However, connections from different devices by the same user will be prevented without an additional license.
For this example, we will proceed with 'Configure Later' and then click 'Next'.
Now, you must define which users are permitted to connect to the Remote Desktop Server. In this case, the user account 'Windows Geek' will be added, and then 'Next' will be selected.
An option is presented to align the RDS Server’s appearance and functionality with Windows 7. This aims to minimize user confusion caused by the classic theme. All settings will be enabled here, though increased bandwidth consumption should be considered before selecting all options. Click 'Next' after making your selections.
As we are utilizing Server 2008 R2, specifying a Discovery Scope is unnecessary. Simply click 'Next' again to proceed.
Finally, initiate the installation process by clicking 'Install'.
Upon completion of the installation, a server reboot is required. The configuration will then finalize during the login process. This concludes the installation of a Remote Desktop Server.
License Activation
The installation of your licenses can be performed via the RD Licensing Manager if required. Prior to this, activation of the Server itself is a necessary first step.
This initial server activation process is generally straightforward and won't be detailed here.
Following license installation, it’s crucial to designate a license server for the RDS Session Host. To accomplish this, launch the RDS Session Host Configuration MMC.
Within the console, locate and double-click the "Remote Desktop license servers" link to access the relevant settings.
You can then define your preferred licensing mode. Subsequently, click the "Add" button to specify the designated licensing server.
As previously mentioned, this activation phase can be bypassed initially. Remote Desktop Services can be utilized for a 120-day evaluation period before a Client Access License (CAL) purchase becomes mandatory.
Once licensing is configured, application installation is the next step. However, a specific methodology must be followed when installing applications on a Remote Desktop Server.