User Profile
Daniel_Gatley
Copper Contributor
Joined Dec 02, 2019
User Widgets
Recent Discussions
Re: Azure AD Endpoint Manager User Profile Corruption: Black Screen Flashing Taskbar Explorer Crash Loop
slider484 I would suggest reaching out to Microsoft support on this, I had a running ticket with them and they advised there is a fix which is behind a feature flag which they enabled in my environment and it works without issue now (since mid April). The wording from Microsoft seems to suggest it should be turned on "in production" but if there are still reports of issue then it would seem not. Microsoft advised "This feature is released to production, but it is behind a feature flag that is disabled in production. I am going to enable this in production over the next 2 weeks. Please confirm that the customer is okay to enable this feature in production. Once the feature is enabled, cloud sync will fix the domainNetBiosName for all users for the customer's tenant." Not sure if it helps but the ticket tracking ID was TrackingID#2404090050003764.856Views0likes0CommentsRe: Azure AD Endpoint Manager User Profile Corruption: Black Screen Flashing Taskbar Explorer Crash Loop
We have been experiencing the same issue and in our situation managed to find a fix. On machines with the issue we had two subkey under the following registry key, on working machine only one. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IdentityStore\LogonCache\B16898C6-A148-4967-9171-64D755DA8520\SubPkgs The keys should represent the NetBIOS name of the on-prem domain, in our situation we had ABC and ABC-GLOBAL, ABC represented the actual NetBIOS name while ABC-GLOBAL was the first part of the FQDN (looking at the domain properties in powershell it was it's "Name"). Both of these keys had a value for "AuthenticatingAuthorityDns" which matched our domain FQDN so the assumption here is some kind of conflict. The solution was to simply delete the key which wasn't out domain NetBIOS name (required taking ownership etc). After a reboot the users could login again. The value for netBIOSName in AzureAD is populated using %Domain.Netbios% for AD Connect and %DomainNetBios% in Cloud Sync. I've not been able to find anymore information about how these values are obtained. I can only assume that Cloud Sync isn't using exactly the same value as AD Connect. Maybe this only impacts where the "Name" and "NetbiosName" (from a get-addomain) are different. Anyway that was my experience, I hope this helps people in the future or gives people pointers to allow cloud sync migrations without this issue,5.9KViews2likes6Comments
Recent Blog Articles
No content to show