Timeline for My domain user profile is not listed in Local Users and Groups - Windows 11
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 18, 2022 at 14:33 | comment | added | grawity_u1686 |
As for DOMAIN.LOCAL, if it's shown in klist then it is actually the Kerberos realm name, which is case-sensitive and traditionally the uppercase version of the corresponding DNS domain. So your AD domain really has three names – DNS, Kerberos, and NT, and the same AD account name can be written as [email protected] in AD UPN format, [email protected] in Kerberos principal format, and DOMAIN\user in NT format.
|
|
| Nov 18, 2022 at 14:29 | comment | added | grawity_u1686 |
A bare DOMAIN is an "Windows NT domain" name that comes from the NetBIOS-based domain system which existed before AD. Every AD domain still has a corresponding NetBIOS / NT domain name (which can have completely different spelling from the AD DNS domain name), but when joining a machine to the domain you should always use the DNS name, i.e. domain.local – support for NT-style domain joins has been gone for a few years now, so It's normal that joining a machine to DOMAIN will not work. (Once the machine is joined though, console logins can still use DOMAIN\user though.)
|
|
| Nov 18, 2022 at 14:15 | comment | added | jabroni |
however this also makes me wonder the other reference to my domain wasn't working. The one that it should be is DOMAIN, whereas the one that works is domain.local. On the AD server the domain name is DOMAIN.LOCAL and the Domain NetBIOS Name is DOMAIN
|
|
| Nov 18, 2022 at 14:13 | comment | added | jabroni | thank you! This helped me figure out that my domain was listed as two separate entries. Fixing that resolved my issue. | |
| Nov 18, 2022 at 14:08 | vote | accept | jabroni | ||
| Nov 18, 2022 at 8:22 | history | answered | grawity_u1686 | CC BY-SA 4.0 |