The hoster isn't an authorized QMTH partner. All VMs created by a user with a Windows E3 or E5 license are automatically activated independent of whether a user signs in with a local account or using an Azure AD account. The Hyper-V host and the VM are both running a supported version of Windows. This functionality eliminates the need to maintain KMS or MAK in the qualifying cloud infrastructure. There's no need to do Windows Pro activation. When a user with VDA rights signs in to the VM using their Azure AD credentials, the VM is automatically stepped-up to Enterprise and activated. ![]() The VM is hosted in Azure or another Qualified Multitenant Hoster (QMTH). The VM is running a supported version of Windows. ![]() For more information, download the PDF that describes the Qualified Multitenant Hoster Program. VMs must be hosted by a Qualified Multitenant Hoster (QMTH). ![]() VMs must be joined to Active Directory or Azure Active Directory (Azure AD).VMs must be running a supported version of Windows Pro edition.Windows VDA is a device or user-based licensing mechanism for managing access to virtual desktops.ĭeployment instructions are provided for the following scenarios: This document describes how to configure virtual machines (VMs) to enable Windows subscription activation in a Windows Virtual Desktop Access (VDA) scenario.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |