PENDING SCCM Cannot Domain join using Windows 11 24H2 in Task sequence

[BP_0233]

Hey,

I've been trying to create a task sequence for Windows 11 24H2 where i want it to simply domain join.

Once the task sequence finishes, the unattend.xml file is present on the computer it was applied to, but it seems as if the unattend.xml file doesn't apply, hence why it isn't domain joining.
Below is a picture of the task sequence step in question, along with the apply network settings after in the sequence where it should domain join.

If anyone has any idea, please let me know

 

[MaxSJD]

Hey @BP_0233
there is literally a extra Step for the Domain-Join in SCCM:


In english the Name should be "Apply Network Settings".

 

[BP_0233]

Hey @BP_0233
there is literally a extra Step for the Domain-Join in SCCM:
View attachment 6781

In english the Name should be "Apply Network Settings".

Hi Max,

In my task sequence that is included.
It still won't work. My steps are listed down the left hand side.

 

[MaxSJD]

Hi Max,

In my task sequence that is included.
It still won't work. My steps are listed down the left hand side.

Hi @BP_0233 maybe attach a Screenshot of the Step "Apply Network Settings" including the "Options"-Tab of this Step.

 

[RRD]

Hey,

I've been trying to create a task sequence for Windows 11 24H2 where i want it to simply domain join.

Once the task sequence finishes, the unattend.xml file is present on the computer it was applied to, but it seems as if the unattend.xml file doesn't apply, hence why it isn't domain joining.
Below is a picture of the task sequence step in question, along with the apply network settings after in the sequence where it should domain join.

If anyone has any idea, please let me know

I am facing similar issue. any fix for this issue???

 

[Stanley Road]

I had the very same issue with a custom image, once I started using the install.wim for builds all the issues stopped. Maybe this isn't your case but worth mentioning

 

[Martin Little]

I've had no end of issues with deploying 24H2. I eventually got Domain join to work in a 2 step approach.

First I use a "Apply Network Settings" step just before the "Setup Windows and ConfigMgr" step and then a "Join Domain or Workgroup" step after. I do have a few custom steps between those, but nothing directly network related. That seems to have ironed out any problems.

I also had to stop using custom images for 24H2 as there was WMI corruption on any deployed system. Classes such as the Win32_LogicalDisk were simply missing or corrupted so much they appeared to be. I've had to switch to just using Install.WIM and shifting any actions to either the production Task Sequence or a post-build setting through SCCM Compliance or Group Policy.

The other thing that I found broke was Driver Package deployment with the Recursive option selected, which pretty much made it pointless, at least with how our packages are. Don't think I do anything special with them, but I always had to have Recurse specified to get them all to install properly. I have a new way of applying Drivers that I'm in the process of implementing that I am happy to share if anyone wants a nerdy infodump.