Window 11 24H2 / Can't Join Domain

Anonymous
2024-08-28T15:27:07+00:00

We have about 500 PCs on our domain. Functional level is Server 2016. We received our first laptop from Dell which shipped with Windows 11 Pro 24H2 and it will not join. Since it's failure, I've tested various versions of Win10 and Win11 not running 24H2 and they all join just fine.

netsetup.log shows:

08/28/2024 08:09:17:784 -----------------------------------------------------------------

08/28/2024 08:09:17:784 NetpValidateName: checking to see if 'XPS' is valid as type 1 name

08/28/2024 08:09:17:784 NetpCheckNetBiosNameNotInUse for 'XPS' [MACHINE] returned 0x0

08/28/2024 08:09:17:784 NetpValidateName: name 'XPS' is valid for type 1

08/28/2024 08:09:17:810 -----------------------------------------------------------------

08/28/2024 08:09:17:810 NetpValidateName: checking to see if 'xps' is valid as type 5 name

08/28/2024 08:09:17:810 NetpValidateName: name 'xps' is valid for type 5

08/28/2024 08:09:17:816 -----------------------------------------------------------------

08/28/2024 08:09:17:816 NetpValidateName: checking to see if 'domainname' is valid as type 3 name

08/28/2024 08:09:17:816 NetpValidateName: 'domainname' is not a valid NetBIOS domain name: 0x7b

08/28/2024 08:09:28:877 NetpCheckDomainNameIsValid for domainname returned 0x54b, last error is 0x0

08/28/2024 08:09:28:877 NetpCheckDomainNameIsValid [ Exists ] for 'domainname' returned 0x54b

The PC attempting to join sits on the same subnet as our DCs and there are no security appliances/firewalls filtering traffic.

From the 24H2 PC that won't join, I have tried or am able to:

  • perform name resolution to various hostnames via nslookup
  • verified inbound/outbound AD ports are open on our DCs
  • DCs are replicating and are healthy (other PCs join w/o issue)
  • Access any other resource on our LAN
  • Tried statically assigning DNS servers (which are our DCs) on the PCs NIC
  • Disabled Windows firewall on the PC
  • Factory reset the laptop (Dell XPS 13 9345) and attempted again with no success

Another post suggest searching for a registry key relating to NT4Emulator on the DCs in the event the domain ever had an NT4 DC. This key doesn't exist on our DCs and if we had a DC running NT4 here, it was way before my arrival.

I can't think of any reason why this laptop is different other than it's the first running 24H2. I can't seem to find anyone having this issue.

Any help or suggestions is appreciated.

Windows for business | Windows Server | Directory services | Active Directory

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

72 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2024-10-29T11:07:09+00:00

    Still I too facing this issue,

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-10-29T11:19:37+00:00

    I tried this method, changes in gpedit and registry, but not solved. Still my laptop is not connecting with domain.

    Is there any other options.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2024-11-07T17:43:55+00:00

    Please note the following update from Microsoft.

    DFCI enrollment fails for Professional editions of Windows 11, version 24H2

    Date added: October 9, 2024

    DFCI can't currently be used on devices with Professional editions of Windows 11, version 24H2. The issue is being investigated. As a workaround, ensure the device is upgraded to the Enterprise edition of Windows 11, version 24H2 during or after OOBE onboarding. After upgrading to the Enterprise edition of Windows 11, version 24H2, sync the device. Once the device is synced, reboot it to get it enrolled in DFCI.

    Windows Autopilot known issues | Microsoft Learn

    DFCI Management | Microsoft Learn

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-11-08T17:39:16+00:00

    thanks for your input. this has to do with OOBE and UEFI. Rather not the problem of; not be able to join a corporate domain.

    Patch KB5044384 will solve the issue you mentioned. (OS Build 26100.2161)

    our problem is still pending....

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2024-11-08T17:42:25+00:00

    any news yet?

    still working around with VPN.

    as if it was possible to still get 23H2 version somewhere, that would help. Then we were able to roll back, even trough reinstall.

    Now we are stuck with 24H2 that has this big issue with domains......

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments