Understanding Remote Desktop Services on Windows Server 2008

I have to configure RemoteApp for a client during the next couple of days and thought it would be the perfect opportunity to write a few turorials on how to configure the whole spectrum of Remote Desktop Services on Windows Server 2008 R2 considering I also have to write work instructions for the clients in-house techies.

To start we can have a look at the basics components of Remote Desktop Services on Windows Server 2008 R2:

What is Remote Desktop Services?

Remote Desktop Services in Windows Server 2008 R2 allows a user to access applications and data on a remote computer over a network, using the Remote Desktop Protocol (RDP).
In other words it allows you to open programs (and Operating Systems) installed on another computer ass if it was installed on yours.
This is achieved by installing various Remote Desktop Services Roles, not all of which are always needed depending on the requirements of deployment.
 
Remote Desktop Services Roles

RD Session Host - Programs and OS that will be accessed remotely are installed/hosted on the RD Session Host.

Remote Desktop Licence Server Role - A CAL is used for each connection made to a RD Session Host or RD Connection Broker, the RD License Server manages process.

Remote Desktop Web Access - Enables users to access RemoteApp and Desktop Connection through the Start Menu or through a web browser.

Remote Desktop Connection Broker - Acts as a load balancer for multiple RD Session Host. Instead of connecting directly to RD Session Host, clients connect to the RD Connection Broker which passes connection to a RD Session Host.

Remote Desktop Gateway - Allows users to connect to RD Session Host or RD Connection Brokers from external networks.

Remote Desktop Virtualization - RD Virtualization Host enables users to connect to virtual desktops by using RemoteApp and Desktop Connection.