Xendesktop 7 server vdi has 3 vmdk windows 10#
Xendesktop 7 server vdi has 3 vmdk software#

I know of no user, personally, that has ever purchased or even been offered SA when buying a personal computer for home use. So, that document sheds no light on my questions or options, since those offerings either weren't around or in very early adoption stages when that document was written. The problem with referencing a Microsoft document from 2012 is that it makes no mention of InTune or Microsoft E3 subscriptions. Hope this helps and please help to accept as Answer if the response is useful. Last but not least, you could reach VLSC support for a call and consult the questions of CAL.

Microsoft does not guarantee the accuracy and effectiveness of information. Please note: Information posted in the given link is hosted by a third party.

Xendesktop 7 server vdi has 3 vmdk software#

Licensing the Windows Desktop for VDI Environmentsīesides, quoted explanation from Dashrender 'To use VDI (Virtual Desktop Interface) you need and OS license (either a workstation license with Software Assurance or VDA or Intune ) and a connection method license, such as RDS or VMWare View or XenDesktop.' in a similar discussion. Remote-desktop-services azure-virtual-desktop azure-ad-licensingĪs for CAL used in VDI, you could check below FAQ to understand better.

Xendesktop 7 server vdi has 3 vmdk windows 10#

So, we are unsure what's proper.Īre any licenses required for the Windows 10 VMs themselves (the OS)? but, the Microsoft brief seems to indicate it's either/or and not both. Some licensing vendors have suggested that both VDA and E3 subscriptions are necessary. From that, I am assuming that since we cannot ascertain whether a remote user's personal device (the device they connect from) has Software Assurance, and is unlikely to have a VDA subscription, the users will need either an E3 or VDA subscription, but not both. We've referenced the April 2020 licensing brief ' Licensing Windows desktop operating system for use with virtual machines.' On, our intended scenario is the first one listed. Users will continue to connect to their existing FortiNet VPN and from there, RDP to their own Windows 10 VM hosted on the server.Ĭustomer already has necessary Server 2019 User and RDS CALs from prior session-based implementation. Users are all off-site, using their own personal devices (not company owned). We'd remove the session-based implementation and replace with VDI.

We have a customer who wants to switch from session-based RDS running on a Server 2019 VM to a VDI deployment (Windows Server 2019 Remote Desktop Virtualization Host role), where users would connect to 'personal' Windows 10 VMs.