Why is VDI changing into Terminal Server?
VDI May 21st, 2009It is, and I’m about to try and prove it to you. Not only is VDI changing into Terminal Server it’s been done through a series of entirely logical and yet very stupid choices.
To work this out we need to start from first principles, way back in 2005ish. We had many expensively maintained fat desktops, spare CPU cycles in the data center and a virtualisation layer. This meant that we could take the fat desktops not already covered by terminal server (which only counted for around 20%) and move them into the data-center. These new desktops would allow our users to install apps, personalise their OS, and IT could keep the environment stable. People were saying things like ‘I can give my users local admin privileges!’.
That was the dream and it all sounded pretty good. Then people realised that they would have to change cheap storage on the end point for expensive storage in the data-center. Also it just seemed, well silly, to have 5000 copies of explorer.exe sitting on the SAN. The advantages of data de-dupe were talked about, but the model that everyone settled on was a golden OS image, Citrix had Provisioning Server and VMware had linked clones. Not only did this solve the high SAN demands, it enabled us to only update/patch one golden image and it worked for everyone! Double win!
So now we have thousands of users on one golden image, trouble is we need different application sets. No Problem! said the industry, we have application virtualisation, it’s even a fairly mature technology, ThinApp, Citrix Streaming, App-V and all the rest. Except not all applications are suitable for streaming, some have license requirements that rely on MAC addresses, some install drivers or services, etc. etc.
In any large organisation there are maybe 2% of these applications which are generally more than 10 years old, but that can’t be dumped. Out of say six hundred apps that’s only twelve apps that need to be in the golden image, so we increase the number of golden images to twelve, and the rest of the applications are streamed.
So far so good, although with this golden image model, we have hit a snag, to allow users to install applications, we need to use block level deltas to save the personal information. Over time these block level deltas can grow to the size of the original installation, ruining our nice SAN space saving ideas! Not only that, when you update the base image you can’t reconcile the deltas, you have to throw them away. That’s no good, you can’t give users a facility and then randomly remove their changes. OK, lets lock down the OS, we can use a profile solution to save user personalisation using the file system (although obviously no user installed apps). For a great explanation of block vs file see Brian Madden’s post “Atlantis Computing hopes to solve the “file-based” versus “block-based” VDI disk image challenge ”
Lots of vendors already in the Terminal Server space, immediately said ‘We have a profile solution!’ and Appsense, RES, RTO, Tricerat etc put out VDI profile solutions.
All of this worked great in the POCs and pilots, trouble is when it scaled up to 1000s of users we found that the power users who were moving gigs of VMDK’s around or working with large media files etc. meant we had to have REALLY expensive Tier 1 storage at the SAN, it became uneconomical to move those users to VDI so we left them on their fat desktops.
So where does that leave us on our big VDI project?
- Multiple users on an OS image
- Application silos
- Locked down desktops
- Profile solutions from Appsense, RTO, RES etc.
- Users limited to Task and knowledge workers
- Oh yeah, print solutions from Citrix and ThinPrint.
- Desktops accessed via RDP or ICA
I mean what does that sound like to you? To me it sounds EXACTLY like Terminal Server. What we have done is taken a VDI dream and apply terminal server thinking to it, unsurprisingly, it’s now looking just like terminal server, but with extra licensing costs.
We need to apply some brand new thinking, there are vendors out there trying to do this, like the afore mentioned Atlantis, but before VDI really takes off we need to rethink a lot of things or Gartners prediction of VDI being a $65 billion business with 40% of the worlds professional desktops seems to be a long way off.
May 23rd, 2009 at 1:41 pm
[...] This post was Twitted by pmarmignon – Real-url.org [...]
May 23rd, 2009 at 3:18 pm
Amen brotha! You’ve got some really good points here and they are the same things I’ve been discussing with my clients. While I haven’t made the specific points about it being just like Terminal Server, I have been saying “it’s sliced bread all over again” because VDI brings up many of the same things we’ve battled with over the last 10 years or so with Terminal Server. Unfortunately, the VDI fanboys would like everyone to think otherwise.
Shawn
May 24th, 2009 at 4:13 pm
Hi, nice posts there
thank’s for the intriguing information
June 5th, 2009 at 4:26 am
da best. Keep it going! Thank you
June 21st, 2009 at 8:09 am
love it. thanks for the post. Keep it going! Thank you
July 6th, 2009 at 4:12 pm
This is a great post
I learnt a lot about terminal servers.
July 13th, 2009 at 9:34 am
Hey
» Why is VDI changing into Terminal Server? – JimMoyle.com, great article, really well though out and very much enjoyed.
Cheers
July 22nd, 2009 at 7:54 pm
Your post was dead on. We had started a POC with XenDesktop. We had numerous issues with profile management, MAC address licenscing, application management and stability. It makes it even more diffucult to justify if you already have a Presentation server install. In my opinion if you do not have a locked down environment, like a bank or school you will ned to invest a lot of time(creating streamed packages, implementing advanced profile maagement and license tracking tools) and money to make this a viable solution at this point.
July 31st, 2009 at 6:05 am
Funny, I googled “VDI is like terminal server” and was hoping to stumble upon an article exactly like this. You stole the words right out of my mouth. Virtualization simply takes away from the user and gives back to the administrator (until support calls roll in).
All virtualization whinds up doing is burning a box out quicker, by utilizing much more of the hardware. It’s like the same truck that tow’s 200 lbs a day (my fat ass) is now towing 2000 lbs a day (10 of me). I’m no physicist, but an electronic appliance without the capability to heal, will degrade faster. Who cares about saving electricity when you have to pay atrocious VMWare prices or have to get bent over by open source solutions. These solutions reduce hardware lifetime and increase system failure/crashes. I mean sure, you have a farm of virtualized servers and can fail over, but it’s not knife-edge and it’s surely not a step up toward the future.
I think we’ve allowed the geek factor to get way out of hand on these concepts. Why not make servers cheaper and more efficient. Energy cannot be created or destroyed, but some IT guy thinks it can be virtualized… God help us.
August 12th, 2009 at 11:27 am
Agree and I wrote a similar piece on dabcc a while back –
http://www.dabcc.com/article.aspx?id=10214
Read today on Harry Labana’s site that even “Desktop virtualisation” isn’t the same as “server virtualisation” – I expect it 6 months it’ll be ‘but these TS based solutions are just like VDI, why don’t we just do VDI’
August 13th, 2009 at 1:53 pm
[...] of just a few days ago, and the one which is linked into Brian’s post written by Jim Moyle (http://www.jimmoyle.com/2009/05/why-is-vdi-changing-into-terminal-server/) some time before then, tend to hit the nail on the head rather [...]
August 13th, 2009 at 2:11 pm
[...] days ago, and the one which is linked into Brian’s post written by Jim Moyle of VisionApp (http://www.jimmoyle.com/2009/05/why-is-vdi-changing-into-terminal-server/) some time before then, tend to hit the nail on the head rather [...]
January 29th, 2010 at 12:26 am
[...] is the key differentiator for VDI over terminal services, as I said in a previous post Why is VDI changing into Terminal Server? the difference between Terminal Services and VDI is actually very small without it. If we want to [...]
July 24th, 2010 at 6:27 pm
[...] http://www.jimmoyle.com/2009/05/why-is-vdi-changing-into-terminal-server/ [...]