NEW Task Sequence fails before domain join - Administrator autologon to desktop, Incorrect Hostname, No SCCM client

[sccmsuffer]

Hello,

Currently we are using SCCM to image new computers with Windows 10 1909. We're looking to update our Windows image to 21H1. We've captured a new 21H1 image using MDT, installing Language Packs and Features on Demand during the process (this same process was used for our 1909 image). To test the new 21H1.wim, we've copied it to SCCM, created a copy of our existing 1909 task sequence, and edited it to use the new 21H1.wim.

When imaging, everything appears to work as expected, until right after the "Install Operating System" step completes. After the OS is installed, it appears to boot into the new installation under the Administrator account, then hangs indefinitely. The hostname is incorrect, but is not MININT-_____. It appears to be assigned part of our company name (example: Walma-1D2F3G4). The computer is also not joined to the domain and the SCCM Client is not installed.

This issue only appears to happen with our new 21H1.wim, but the older 1909 task sequence still works perfectly fine. If anyone may have any ideas what could be causing this, we would greatly appreciate some guidance.

Thank You

 

[sccmsuffer]

This appears to have been related to capturing the image from MDT using a Generation 2 Virtual Machine. After switching to a Generation 1 VM and recapturing a new image, the new image works as expected in our SCCM task sequence.

Lesson learned, use a Generation 1 VM for MDT Captures.