Vda microsoft8/30/2023 ![]() ![]() 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.įurthermore, with Microsoft attempting to discontinue Office on Windows Server has many customers rethinking RDS as a long-term strategy anyway. 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 not be difficult to bundle a download and key in the MAC licensing console for VDI use. 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). ![]() Because it's a Software Assurance entitlement, I figured it was tied to agreement length (3 years). I had not thought about the availability of the client and keys, but that makes sense. Thank you for the clear and detailed response. Now, CSP HOsters can sell M365 suites no matter how the cluient base of their customer does look like. 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. 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. 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. If the person which should access the virtual desktop is not primary user of any client device with a qualifying OS, e.g. ![]() However, when this user/person fulfills this requirement, this user may also access the virtual desktop also from other non-windows devices they use. Primary user means this person is using the device for the majority of the time the device is powered on. a workstation with a valid Windows 11 pro OEM license would count. 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. I'm sorry to provide such complicated answer below, but this matter of Windows licensing is really one of the most complicated at Microsoft. To the 2nd part of the question of Jennie Mayer - it does matter, respectively it may matter considering the complete picture. Hosting partners like QMTH or CSP Hosters have access to KMS keys and media enabling such scenario in their environment. 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. The product terms are authoritative since they are referenced in the Totally agreeĪnd, maybe more importantly, also Priebe - technically it does not work to deploy Windows E3 obtained in CSP/under MCA on the customer's own on-premises servers. ![]() Personally I would recommend to wait until the language in the product terms is updated properly to have an official answer - evrything stated in the webinars or here on the forums is not part of the agreement and may simply disappear - and if the past and current product terms do not document any such right officially it might be an issue. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |