Score:0

Wrong 'executing account name' on Azure AD joined machines (Windows 11, Autopilot)

uz flag

Currently we have 'Azure AD Domain Services' activated in our tenant, which is a managed AD through Azure. Data is being synchronised between Azure and the managed AD. We're preparing to migrate away from this solution, so we can go full cloud using Intune and Azure AD as identity provider.

I started testing on migrating some machines for testing. Everything went fine: the machines were 'Azure AD joined' and enrolled using Autopilot. After a while I noticed some (legacy) software was not working as intended. Did some research and I found out the username on the machines was not always in the same format.

For example, the user 'Jason Green'. If this user logs on to our Azure AD joined-machine, the user profile is created as C:\Users\JasonGreen. But if I ask another user (for example: Harry Smith) to log on to that same machine, the user profile is created as C:\Users\h.smith. So there is variation in the user profile name.

Other users experiencing the same:

Because we have software assigning specific settings based on the username, I can't get it to work properly. Users with the format C:\Users\JasonGreen do get the settings, but users with format C:\Users\h.smith do not.

After some more research I also collected the following output from the command dsregcmd /status.

First user logging on to the machine (working situation):

AadRecoveryEnabled : NO
Executing Account Name : AzureAD\JasonGreen, [email protected]
KeySignTest : PASSED

Second user logging on to the same machine (non-working situation):

AadRecoveryEnabled : NO
Executing Account Name : DOMAIN\h.smith, [email protected]
KeySignTest : PASSED

Notice how there's no AzureAD\ in the Executing Account Name-field, but instead the local domain name is being shown.

Important to know: we did install and configure Azure AD Connect in the past, but just for testing purposes. After a few hours we decided this solution would not work for us, as we did not had a local AD to synchronise to Azure. Therefore we uninstalled the software. See here: https://i.imgur.com/5ypQOOG.png

To be sure, I did check if we still have any old settings enabled, such as federation settings, but that was not the case.

I've pretty much tried everything I can think of, but I really don't understand what is causing the variation in user profile names. If someone has a suggestion, please let me know! Thanks for reading :-)

Codemeister avatar
uz flag
Solution: I contacted Microsoft Azure Support by creating a ticket. I sent in a CSV file with all users experiencing the problem. Microsoft deleted the following attributes linked to their accounts: DNSDomainName, NetBiosName, OnPremisesDistinguishedName, OnPremisesSamAccountName. After that, the problem was resolved. Hope this helps!
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.