05-08-2020 06:50 PM
05-08-2020 06:50 PM
We recently purchased some licensing of Windows 10 E3 VDA that we want to assign to users to allow access to some Windows 10 Pro virtual desktops. As of now I've setup AD Connect with AD Forest credentials from on prem AD to sync password hash, write-back, and sync devices. I can confirm that password sync is working, and devices show up as hybrid synced when placed in my test OU. When I attempt to login to the computer with my test account, with Win10-VDA assigned to 365, the computer remains licensed for Windows 10 Pro. If I setup a new VM, and choose to join the Azure AD directly, it works and the license is assigned properly. I'm not sure what I'm missing, but the option to enable write-back and user password unlock are also grayed out in Azure, even though I've setup write-back with proper credentials, I checked the MSO_ account and permissions are correct. Any help is highly appreciated.
05-11-2020 06:14 AM
@Chris_Menuey Did you configure device registration as described in https://blog.alschneiter.com/2018/08/16/configure-device-registration-with-azure-ad-connect/?
If a device is registered by an AAD user who has the appropriate license assigned it is switched from Pro to Enterprise.
05-11-2020 08:10 AM
@Simon TaylorI had a support ticket with MS open this morning, out of sheer miracle when I logged in to show him my VDI on Pro, it said the enterprise license was activate. To attempt to test I tried to removed the licensing from Office 365 but it didn't seem to take effect right away. I'm not sure if it just needed time to sync or what. The devices had been registering correctly, and showing Hybrid Join. I guess for now my problem is solved. I was also curious, in case you know, does the computer I'm logging into, the VDI, already have to be licensed for Windows? I read somewhere that the machine will activate with subscription but that the license doesn't cover the machine itself only the user?
05-12-2020 09:31 AM
@Chris_Menuey The basic requirement is that the device is properly activated re the underlying W10 Pro license. There a different ways to get there as described in https://docs.microsoft.com/en-us/windows/deployment/deploy-enterprise-licenses so that for example with 1803 and newer the device must not have been activated before but can be activated automatically based on the UEFI embedded key when using subsription activation to switch from Pro to Ent