Remember Terminal Server? And then Terminal Services? We’ve now renamed it to Remote Desktop Services (RDS). The core functionality of Terminal Services is now included in the new RDS functionality. We renamed it because it now encompasses more than just Terminal Services. It now also supports VDI and our Remote Applications (RemoteApp) functionality. Not only have we enhanced the feature set, but we also improved the fidelity of the remote desktop experience. Our Remote Desktop sessions now support Aero graphics and even VOIP.
I think one of the biggest things we added in R2 to RDS is the Desktop Gateway Services. Desktop Gateway Services allow access to not only the traditional Terminal Servers, but they also allow connections to VDI solutions. This is cool because you can connect to multiple solutions via a unified gateway interface.
We need start to start with Getting Started with Remote Desktop Services this will give you a good overview of what’s new and how to get the most out of RDS.
How do you set this stuff up? We have a number of step-by-step guides. The first one talks about how to setup the initial infrastructure.
Once we get the Remote Desktop Session Hosts configured, we can then look at the Remote Desktop Gateway Services. This allows us to securely publish our Remote Desktop Services to anyone that has an internet connection.
Before you can take this solution into production, you need to be sure to get the licensing server setup. Here’s the licensing server setup guide:
So I’ve told you about the technical solution, but how do you license it properly?? What if you already own Terminal Server CALs? Do they have to be upgraded to R2? NO! Check out the overview below, but the great part is that existing TS CALs will work for the new Remote Desktop Services in R2. Please check out the overview below for the important details.
I’m going to spend more time with the new Remote Desktop Services and I’ll share more as I build it out.
Until next time,