![]() ![]() On the Add applications page, add applications if desired. On the Account Management page, choose Enroll in Azure AD, select Get Bulk Token, sign in, and add the bulk token using your organizations credentials. Under Name, enter Desktop Bulk Enrollment, select Finish, and then on the Set up device page enter a device name. Under Enter product key enter the Pro GVLK key: W269N-WFGWX-YVC9B-4J6C9-T83GX. Under Name, enter Desktop Bulk Enrollment Token Pro GVLK, select Finish, and then on the Set up device page enter a device name. If you must activate Windows Pro as described for scenario 3, complete the following steps. When attempting to access the VM using remote desktop, you'll need to create a custom RDP settings file as described below in Create custom RDP settings for Azure. For example, Desktop Bulk Enrollment Token Pro GVLK.ppkg When entering the PackagePath, use the project name you previously entered. Existing virtual machines that are Azure AD-joined and deployed won't need to be recreated.įor Azure AD-joined VMs, follow the same instructions as for Active Directory-joined VMs with the following exceptions:ĭuring setup with Windows Configuration Designer, under Name, enter a name for the project that indicates it isn't for Active Directory-joined VMs, such as Desktop Bulk Enrollment Token Pro GVLK.ĭuring setup with Windows Configuration Designer, on the Account Management page, instead of enrolling in Active Directory, choose Enroll in Azure AD, select Get Bulk Token, sign in, and add the bulk token using your organization's credentials. After 180 days, you'll need to update the provisioning package and re-inject it into the image. Under Name, enter Desktop AD Enrollment Pro GVLK, select Finish, and then on the Set up device page enter a device name.Īzure AD provisioning packages have a 180 day limit on bulk token usage. Open Windows Configuration Designer and select Provision desktop services. If you must activate Windows Pro as described for scenario 3, complete the following steps to use Windows Configuration Designer and inject an activation key. ![]() Select Add, enter Authenticated users, and then select OK three times.įollow the instructions to use sysprep at Steps to generalize a VHD and then start the VM again. On the Remote tab, choose Allow remote connections to this computer and then select Select Users. (Optional) To disable network level authentication, enter the following command at an elevated command prompt: REG.exe ADD "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp" /v UserAuthentication /t REG_DWORD /d 0 /fĪt an elevated command prompt, enter sysdm.cpl. ![]() Use the following instructions to prepare the VM for Azure: Prepare a Windows VHD or VHDX to upload to Azure For more information, see Troubleshoot Azure Windows virtual machine activation problems.įor examples of activation issues, see Troubleshoot the user experience. KMS activation is provided for Azure VMs. Alternatively, a KMS activation server can be used. Activation is accomplished using a generic volume license key (GVLK) and a volume license KMS activation server provided by the hoster. In this scenario, the underlying Windows Pro license must be activated prior to using subscription activation Windows Enterprise. 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, an authorized outsourcer, 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |