![]() So now you need to buy it from the Open Value program that is still available and "replace" the Open Licence program. These products where bought previously in the Open Licence Volume (for SMB custommers) that is no more available since January 2022. If the VDI are on-prem (not QMTH) the ONLY way to activate the Windows OS of those VDI's is to buy a VDA (Virtual Desktop Access) if the client computer accessing the VDI have not a Windows activated device (like smartphone, linux thinclient etc.) or a SA (Software Assurance) if the client device (not the VDI thus) have a Windows activated OS I get an update about this and I finally have a clear vision of the process : ![]() Well, if I don't license the Windows 10 VM, then the VM won't get activated, correct? This is what I tested earlier in that while the AAD user was able to sign-in and the Windows 10 Pro got converted to Windows 10 Enterprise, the VM itself still wasn't properly activated. What I still don't understand is the writer says DO NOT license the individual Windows 10 VM. ![]() However, if the users have a primary device with Windows 10 Pro, then the VDA license is technically not needed and only regular E3 license would be needed, saving a few bucks. ![]() With VDA, the user can use any sort of thin client or device with a non-qualifying OS to remote into the VM. I understand now that the VDA license applies to the 'user' accessing the remote Windows 10 VM hosted by the SP. I am mainly concerned with Option 3 in that article: Per-User with CSP. My brain is seriously hurting right now reading all this stuff but I think I'm on the right path and how I think this works is totally wrong based on this excellent write-up: However, this is just a test and sooner or later I will have to join the VM to a local DC. Understanding that E3 VDA costs the most, I would have believed that everything in that license would cover the Windows 10 license inside the VM.Īt the moment it is joined to AAD. With the standalone E3 or E5 licenses, I understand that the user's underlying Windows 10 Pro would need to be activated first before the "add-on" of the E3 or E5 license would be applied. The Windows version is correctly upgraded to Windows 10 Enterprise from Pro so I know that is working but how does this activate without having to first using a MAK key or KMS server to activate the base Windows 10 Pro? However, I checked the Activation status and although it says my subscription is active, under Activation it says "Windows is activated using your organization's activation service". I then signed in using the AAD user of which the VDA license was assigned to. I've then installed Windows 10 Pro version 1909 in a VM without any activation. What I have done is purchased a Windows 10 Enterprise E3 VDA license and have assigned it to a Azure AD user which has been synced from on-prem Active Directory using Azure AD Connect. Since some of them use thin clients or Linux, the VDA license was the best way to go as well as it will be hosted in our cloud (virtualization rights needed)Īccording to Microsoft in this article under Scenario 1, installing Windows 10 Pro version 1803 or later will not require you to having to first activating Windows 10 Pro. I want to deploy virtual Windows 10 Enterprise VMs to users. I'm just learning this whole subscription thing being offered by Microsoft.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |