Forum Discussion
Eirinn_1975
Nov 09, 2021Copper Contributor
UPN missing from Devices in Endpoint
Hello all, At my workplace we have a mixed AD/AAD environment. We need to deploy a specific configuration profile through Endpoint, which, I've found out, is pending for all of those devices which a...
Eirinn_1975
Nov 11, 2021Copper Contributor
Just in case, if anyone's wondering, I've found a solution, most probably not the best, but it works:
-create local windows admin on the machine without UPN
-remove machine from domain
-login with local admin, settings -> accounts > school & work accounts -> add account
-select the last option, "join to Azure AD domain", use the primary user credential
-after a while windows will give an error: the client is already enrolled
-don't try again. Add an account again, but this time select "join local AD domain"
-set the primary user as main client user.
- reboot and login with primary user client credential, making sure you're entering the full address, so with the @part as well, eg. name.surname@companyAD.com
-once logged in, the client should now have a UPN in Intune.
This has been useful to deploy the use of security USB keys on some older clients, so it might be useful to others as well.
-create local windows admin on the machine without UPN
-remove machine from domain
-login with local admin, settings -> accounts > school & work accounts -> add account
-select the last option, "join to Azure AD domain", use the primary user credential
-after a while windows will give an error: the client is already enrolled
-don't try again. Add an account again, but this time select "join local AD domain"
-set the primary user as main client user.
- reboot and login with primary user client credential, making sure you're entering the full address, so with the @part as well, eg. name.surname@companyAD.com
-once logged in, the client should now have a UPN in Intune.
This has been useful to deploy the use of security USB keys on some older clients, so it might be useful to others as well.