This week I delivered a couple of sessions for Microsoft on Microsoft VDI/RDS as part of their People Centric IT Road show which WMUG hosted the Reading session. I thought it only right that I should therefore share some of that information with those who couldn’t attend, that and it’s a subject I don’t often write about but is pretty cool and often forgotten about.
So what is Microsoft VDI and RDS?
Well VDI is a fairly generic term meaning Virtual Desktop Infrastructure. RDS is the technology term meaning Remote Desktop services. So you could refer to it as Microsoft VDI powered by RDS.
Now you could also lend those terms to the 2 different options available to us and really the naming conventions we should become accustomed to.
VDI to Virtual Machine based desktop deployment OR RDS to Session based desktop deployment.
For clarity, I’m going to refer to this as RDS. As you can see you can deploy RDS in 3 ways
Session based is according to the stats the most popular. In fact 70% of all customers that investigate Microsoft RDS choose this solution. If you are familiar with RDP (I imagine most of us are) then you are effectively using the technology in a session based way. Another session based option is Microsoft RemoteApp.
Virtual machine based combines with a hyper-v virtual host and allows you to use a standard ‘gold’ image to deliver to your users. If you already have a corporate WIM then you can convert this into a VHDX or even build a VHDX from a ConfigMgr task sequence as described by Rob Marshall here, either should work well.
So what are the features of each method?
The benefits of using this solution are many but will also depend on the requirements of your organisation. I highlighted some of the benefits of using Microsoft VDI solution for desktop and application delivery as follows:
In case you missed it, Brad Anderson announced at TechEd US 2014 that Azure RemoteApp is on it’s way. You can get your demo now here.
This will allow you to run your remote applications leveraging Microsoft Azure platform either fully or in a hybrid set-up. Full Azure obviously means hosting your servers in the cloud whilst the hybrid allows you to retain your on-premise servers whilst leveraging Azure for delivery of your applications. The layout would be something like this: