Remote Desktop Services in Windows Server 2012 R2 - Single Server Deployment - Session-based

Remote Desktop Services provides desktop and application deployments to any device.  Remote Desktop Services enables virtual desktop infrastructure, session-based desktops, and applications, allowing users to work anywhere.  Previously called Terminal Services prior to Windows 2008 R2, there are many more features and it provides a much more robust environment than previous versions.  

Further reading on RDS can be found here:

http://technet.microsoft.com/en-us/library/hh831447.aspx

The purpose of this article is to provide instructions for a basic deployment to get you started.

Topics include:

• Session-based Single server Deployment
• RD Licensing Deployment
• RD Gateway

Step 1. RDS Role Installation/Deployment

We will start with Server Manager and adding the Role to the server.   The computer must be available for a reboot for this process.

From Server Manager click Manage > Add Roles and Features Wizard

Click Next.

Select Remote Desktop Services installation.

Click Next.

Select Quick Start for a single server deployment.

Note: Minimal configuration is required when this option is selected.  Options can be modified after deployment from Server Manager.

Click Next.

For this walkthrough, select Session-based desktop deployment.   

This provides users with a full desktop experience on the server operating system itself whereas virtual based deployment connects users to Virtual Machines. 

Click Next.

Click the server name and click the arrow to add it to the right column.

Click Next.

Note: Multiple servers can be added to Server manager on one server.  When this is done, you would see those servers listed here as well and RDS could be Installed and deployed on all of them simultaneously.  This can be done for deploying any role in Windows Server 2012. For further reading on configuring adding multiple servers to Server Manager see article:

If a reboot is possible check "Restart the destination server" and click Deploy.

The computer will reboot one time during this process, and it is required for the role to be installed.

Once complete, Remote Desktop Services will be listed in Server Manager. A quick session collection is created automatically as part of choosing the "Quick Start" deployment.   A Standard deployment requires a manual collection to be created on the Connection Broker server.  In this scenario one server contains all roles.

You are given the option of adding more RD Session Host servers or create a collection of Session hosts.

Note: More than one Session Host can be added by clicking "Add RD Session Host Servers"

Step 2. RD Licensing

• The RDS Licensing feature is not added to this machine during the RDS deployment, however it can be added to this machine or a different one within the domain.
• RDS CALs (Client Access License) must be added to the license server. 

Note: The licensing grace period will run out at the end of 120 days. At this point no more than 2 RDP connections will be able to concurrently connect.

Note: RDS CALs are not the same as "Server CALS", which are a documentation-only type CAL for allowing connections to shared folders, ftp, etc.

Click  RD Licensing.

Click the server name and then click the arrow to move the server name to the right-hand column.

Click Next.

The wizard will add the server as the license server and install the license server service when you click Add.

Click Add.

The licensing service is now installed, and configured as the license server for this deployment.  But the license server must still activated and RDS CALs added. 

To do this open Administrative Tools > Remote Desktop Services > Remote Desktop Licensing Manager.

Note: Remote Desktop Licensing Manager will not be available until the RD Licensing has been added through Server Manager.

As we see our license server is yet to be activated and the default scope was set to Domain.

Note: The default scope is fine for our purposes but can be changed if desired.

IMPORTANT: The license server is not added to the AD Group "Terminal Server License Servers" automatically.  This will prevent Per User CALs from being issued and also will prevent tracking of Per User CALs.

Right click the server name and click Review Configuration.

This setting will not be relevant if the Per Device CALs are being used.  However if Per User CALs are going to be used, click Add to Group and it will be added to the AD group.

Right click the server name again and click Activate Server.

For further instructions on activating the License server see article:

Now that the server is activated with Microsoft, Install Licenses is no longer greyed out.

CALs may now be added to the License server.

RD Gateway - Optional

Remote Desktop Gateway is used to allow secure connections using HTTPS from computers outside the corporate network.

It offers the following benefits:

• Secure connections via HTTPS (Port 443 Default) without the use of a VPN
• Enables connections through firewalls without opening additional ports IE:3389

For configuration and more information see article: https://www.dell.com/support/article/HOW10137