Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, April 30, 2020 2:00 PM
We have a problem with some (but not all) of our Windows 10 Pro desktops upgrading to Enterprise. We have set up a domain with an on-premises Server 2016 domain controller, installed AD Connect and joined it to Azure, and so now have a hybrid set up. Everything seems to work - AD Connect reports successful syncs, and new users created on-premises appear in the Azure AD portal. Single domain, single subnet, all desktops getting group policy from the same domain controller.
We have purchased Enterprise E3 licences, and assigned them to users in the Azure AD portal.
The Microsoft instructions imply that all is required is that a user with an Enterprise licence assigned to them simply logs in to Windows 10 Pro using the synced credentials, and the Enterprise features should be automagically enabled.
This has worked for about half of our desktops, but not the other half. I can't see any obvious difference between the ones that have upgraded to Enterprise and those that haven't.
Running dsregcmd /status on the desktops reports they are AzureAdJoined and DomainJoined. Also reports "IsDeviceJoined : YES" and "IsUserAzureAD : YES".
The Azure AD portal shows all the desktops in the Devices section, and all the user logins are showing in the Azure logs, regardless of whether they have upgraded to Enterprise or not.
The Microsoft documentation for enabling Windows 10 Enterprise in a hybrid environment is very sparse, and I can't find any guides to troubleshooting the upgrade process, or forcing it. Can anyone point me in the right direction?
Thanks.....
All replies (6)
Friday, May 1, 2020 5:38 AM
Hello，
If a device is running a previous version of Windows 10 Pro (for example, version 1511), it will not be upgraded to Windows 10 Enterprise when a user signs in, even if the user has been assigned a subscription in the CSP portal.
Ref: /en-us/windows/deployment/deploy-enterprise-licenses
Best regard,
Sylvia
Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact [email protected].
Friday, May 1, 2020 6:55 AM
Hi Sylvia
All PCs are on Windows 10 1903 or 1909 (initially installed as Pro).
As I say, about half have upgraded as expected, but half haven't, and I can't see any difference between the two. Same Windows version, same hardware, same domain, same subnet, same group policy, all Azure AD joined in a hybrid environment...…..
Nick
Tuesday, May 5, 2020 7:49 AM
Hi Nick：
In settings-activation, are there any error prompt there? If so, please provide the error here.
And you need to notice that if a user signs into a device using their Active Directory account and MFA（multi-factor authentication）is enabled, the device will not successfully upgrade to their Windows Enterprise subscription. When the user signs in on a Hybrid Azure AD joined device with MFA enabled, a notification will indicate that there is a problem. Click the notification on the setting and then click Fix now to step through the subscription activation process.
Best regard,
Sylvia
Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, May 5, 2020 8:12 AM
Hi Sylvia
No, no errors showing in the activation page.
I did an experiment - my desktop PC was one that hadn't upgraded to Enterprise when I logged in, and I did have an Enterprise E3 licence assigned to me. My logins are showing in the Azure logs, and my PC is listed under Devices in Azure.
I borrowed the credentials of a user whose PC had successfully upgraded to Enterprise, and used those credentials to log in to my PC. My PC upgraded to Enterprise straight away when logged in as the other user.
I then logged out as the other user, and back in as me, and my PC has kept the Enterprise status.
I've now been through 3 reboot cycles over several days, and my PC is still Enterprise when logged in with my credentials, even though it remained at Pro previously before logging in with the other user's credentials.
I can't see any reason for the above behaviour, but it demonstrates that both the PC was capable of achieving the upgrade, and the User (me) was eligible. The question is why the upgrade didn't automatically happen earlier, and how I get the other affected users upgraded without manually going around to all their PCs and logging in as a different user.
Nick
Thursday, May 7, 2020 8:57 AM
Hi nick:
I have to say that on forum platform, we can do limited for you, I advise you to open a support ticket with Microsoft. There are best resources can help you.
https://support.microsoft.com/en-gb/hub/4343728/support-for-business
Thank you for understanding and cooperating.
Best regard,
Sylvia
Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact [email protected].
Thursday, June 25, 2020 5:02 PM
Hi,
We have had this issue with Windows 10 1909 Hybrid AD joined with MFA enabled. Devices are dropping to Pro (the PC's default) and needed to Fix Now to be clicked to go back to enterprise. What's worse is devices are also dropping back to Pro after 30 days when there renewal comes up leaving quite a lot of Pro devices in our estate when we should have enterprise. Has anyone else noticed this or even better been able to solve it?
Kind Regards