Forum Discussion
Microsoft E3 and Windows 10/11 E3 CSP Licenses and VDA Rights
LicensingConcierge1 I want to make sure I understand that you are agreeing that now the MS E3 or Windows 10/11 E3 does include onprem VDA rights. Is that correct? Also, I am assuming it does not matter if the user is accessing the VDI environment from a Windows device or a thin client since VDA includes rights from either of these devices, correct? I want to make sure I have it right. Thank you!
David_Priebe: Totally agree
And, maybe more importantly, also David Priebe - technically it does not work to deploy Windows E3 obtained in CSP/under MCA on the customer's own on-premises servers. There is neither media provided, nor a key - and subscription based activation technically requires an activated Windows client OS underneath to work - which is not applicable to a VDI scenario where there is Windows Server Hyper-V or even other hosts like VMware used. Hosting partners like QMTH or CSP Hosters have access to KMS keys and media enabling such scenario in their environment.
To the 2nd part of the question of Jennie Mayer - it does matter, respectively it may matter considering the complete picture. I'm sorry to provide such complicated answer below, but this matter of Windows licensing is really one of the most complicated at Microsoft...
[Below is based on the same Windows client license terms referenced in my first post - the beginning of the article mentions the license assignment requirements and defines what is a qualifying OS. Below is still a shortened version, so make sure to review the license terms in detail for definitions]
- The Windows E3/E5 license can only be assigned to a person which is the primary user of a client device with a "qualifying operating system license" - e.g. a workstation with a valid Windows 11 pro OEM license would count. Primary user means this person is using the device for the majority of the time the device is powered on. However, when this user/person fulfills this requirement, this user may also access the virtual desktop also from other non-windows devices they use.
- If the person which should access the virtual desktop is not primary user of any client device with a qualifying OS, e.g. their main working device is a Mac, it is required to obtain the more expensive VDA license for them, Windows E3/E5 is not allowed to be assigned to this user then. Alternatively, for the purpose of accessing a virtual desktop the Microsoft 365 F3/F5/E3/E5 license terms also waived the requirement of being a primary user of a device with a qualifying OS in October '22 license terms update, so when going for M365 it does not matter what the user has as primary device.
This last change is very beneficial for Partner providing hosted virtual desktops - before even QMTH Partners would need to ask their potential customers about what primary working device type their users have to determine if they could sell M365 suite licenses or need to go for the standalone plans combining VDA E3/E5 with O365E3 for example. Now, CSP HOsters can sell M365 suites no matter how the cluient base of their customer does look like.
Hi JanoschU , just to corroborate, from what you say I understand that I could license a vdi with Microsoft F3/E3/E5 for example in my on-premises infrastructure (Hyper-V, Vmware, etc.) regardless of the operating system of the end user device (Mac, Linux, Android, etc). as indicated in this article www.microsoft.com/en-us/licensing/news/options-for-hosted-cloud from October 3, 2022. that's correct?- JillArmour
Community Manager
JanoschU Nice to see you in the boards again! Welcome back. 🙂
The technical application of Windows is outside the scope of a concierge, because I don't have the technical understanding/expertise that you have, which is why I suggested that the OP ask one of our Windows specialists.
Thanks for chiming in JanoschU !
Regards,
LC
Thank you for the clear and detailed response. I had not thought about the availability of the client and keys, but that makes sense. Because it's a Software Assurance entitlement, I figured it was tied to agreement length (3 years). That said, I would argue that CSP customers are paying the same as EA/MPSA and although they don't have 3 year agreements for most skus, customers are sticking with the platform (M365 and/or Windows E3). It would not be difficult to bundle a download and key in the MAC licensing console for VDI use.
It's clear from igel Disrupt this year that all the major on prem VDI players acknowledge AVD and W365 are the future. It would greatly ease that transition if Microsoft made it easier for on prem customers to deploy VDI and not be financially restricted to RDS because of legacy licensing policies.
Furthermore, with Microsoft attempting to discontinue Office on Windows Server has many customers rethinking RDS as a long-term strategy anyway. It's time for an update.
