Geeks With Blogs

News Clicky Web Analytics

web stats View David Caddick (davidcaddick@gmail.com)'s profile on LinkedIn

Search this Site!

Locations of visitors to this page
View My Stats eXTReMe Tracker
This posting is provided "AS IS" with no warranties, and confers no rights. The opinions expressed within are my own and should not be attributed to any other Individual, Company or the one I work for. I just happen to be a classic techie who is passionate about getting things to work as they should do (and are sometimes advertised and marketed as being able to?) and when I can I drop notes here to help others falling in to the same traps that I have fallen in to. If this has helped then please pass it on - if you feel that I have commented in error or disagree then please feel free to discuss with me either publically or privately? Cheers, Dave

Thin Clients, VDI and Linux integration from the front lines.... Raw and sometimes unedited notes based on my experiences with VMware, Thin Clients, Linux etc.
Hi All,
 
I had an Integrator ask me for the details on how they could solve the MS Licensing dilemma around a relatively simple (??) VMware XP SP2 Desktops being delivered from an ESX VMware Server. As this was essentially a VDI scenario I found it somewhat interesting that this info didn't appear to be readily available.
 
As I knew that Prudential UK was listed as a Success Story by VMware at
 http://www.vmware.com/customers/stories/prudential.html 
I was able to find that a chap called Andy Ruby was the guy who designed/installed this. Via LinkedIn I was able to contact him and the answer is listed below
 
As I also have some contacts here in Australia with VMware I was also able to get their response as well (see link to VECD from MS) and below I have passed on my 2 cents worth to the Integrator. I hope all of this makes sense? and I hope you find it useful? VECD Datasheet
 
With regards to Prudential in the UK:
++++++++++++++++++++++++++++++++++++++++++
Hi David
Prudential used an OEM licence issued by HP. Each XP OEM licences was tied to the serial number of the DL360 servers Prudential deployed. However, I'm not sure this helps you since MS were reluctant to continue with this policy and wanted full XP licences to be purchased for future deployments.

Andy
++++++++++++++++++++++++++++++++++++++++++
 
And this ties in neatly with the Answer from VMware:
++++++++++++++++++++++++++++++++++++++++++
The above licensing discusses the Licensing for Vista and the bullet point below is at the bottom of the text. So if all you have is the XPSP2 license then you are not going to be covered. Smart move by Microsoft, as it make any VMware customer a Microsoft customer.  
  • In both cases customers can install an unlimited number of copies of Windows Vista Enterprise or downgrade operating systems on server hardware and access up to 4 concurrent running instances from a licensed device.
++++++++++++++++++++++++++++++++++++++++++
 
So in Summary, my reading on it at the moment is that if you want to deploy the XP SP2 solution today you effectively have 2 options:
  • Purchase full XP SP2 Licenses and go ahead, although you might be on thin ice but it is unlikely MS will complain too loudly
  • Purchase Vista with VECD - this leaves you completely in the clear, but at a significant cost disadvantage
That sums it up pretty much at the moment? Please let me know if you disagree or you'd like to discuss this further?
 
Posted on Thursday, May 31, 2007 1:10 PM IT Management , VMware and other Virtualization tools | Back to top


Comments on this post: MS Licensing for XP Desktops in VDI/DDI/Virtual Desktop design - VECD (Vista Enteprise Centralized Desktop) - how does it work, and what License do you have to buy?

No comments posted yet.
Your comment:
 (will show your gravatar)


Copyright © Dave Caddick | Powered by: GeeksWithBlogs.net