The company I'm working for is in the middle of a View 4 implementation involving 100-ish workstations which are to be used by a large number of people periodically. We're implementing Windows XP on the VM end, and using Windows Vista for the physical endpoint with the View Client.
Now, we were under the impression that the required licensing for this solution is;
1. Microsoft VECD using Downgrade Rights to cover the O/S for the physical endpoint and the VM end
2. VMware View licensing to cover the concurrent use
3. VMware ESX Server licensing to cover the ESX servers
4. Microsoft Windows Server licenses to cover the infrastructure servers
5. Microsoft Windows Server CALs to cover A/D connectivity from the VMs to our Active Directory domain
6. Microsoft Office licenses to cover the Office installs on the VMs (Office is not installed on the physical machines)
We've been engaged in some discussions with Microsoft and their partners to confirm that this is indeed the case, and there appears to be some enormous confusion about what's really required. In particular, we've just had someone from MS drop a bomb on us regarding licensing.
They're claming that we need Terminal Services CALs for every physical endpoint because View talks through RDP, and in addition that we need MED-V licenses for every VM because we're using virtualization.
This strikes me as mildly insane. As far as I'm aware, the Windows XP use rights allow you to use RDP to connect to a Windows XP machine as long as only one person is doing it at a time to a single instance (this is the case), And with MED-V, we're not using any Microsoft virtualization product at all.
Has anyone else heard about this, or does anyone have access to any material that proves exactly what is required?
