SCCM Task sequence not install client

[Sheridan]

I've copied a task sequence in SCCM (just to deploy a 'thin' version of W11 instead of the fully loaded version, so the only difference is the image) however when I deploy it the client pulls down and applies the image, reboots and goes to the login page

 

So it appears the client package isn't installed and any subsequent application installs are missed. I'm not seeing any errors though, so I'm a bit baffled as the 'full' version task works ok (albeit taking much longer, but that's expected due to the image size!)

 

Anyone seen this before? it seems like the client package has been pulled down, just not installed as I can see the folder _SMSTaskSequence on the client but I can't seen an error in the smsts.log

[slugshead]

Tick the box on each of the steps in the task sequence that says continue on error.

 

I suspect something is failing, it errors and reboots and skips the remaining steps. I've seen this a number of times with network driver packages that attempt to install, gives an unusual success code and bombs out the rest of the task sequence. Device reboots, you're sat at the login screen and lots of steps have been missed.

[CHiLL]

While it's probably not related, I experienced something similar earlier this week, the client wasn't being installed. In our MDT based TS, along with deploying driver packages in the step before "Setup Windows and ConfigMgr", we also deploy drivers as Applications using silent switches (because sometimes the drivers packages don't always install all the drivers), which is right after the "Setup Windows and ConfigMgr" step. For these driver applications, we use WQL queries to limit them to running on machines of a certain model. As it turns out, I had made a typo on one newly created WQL query and it was causing the TS to fail without failing. No error message would be displayed and Windows would restart on the next step "State Restore - Restart Computer". Since the OS had already installed and the Windows and Network configuration steps had already completed by this point, Windows would just assume it's working fine and boot. Once I fixed the typo, it worked immediately. Edited April 25, 2024 by CHiLL

[Sheridan]

Hmm I've tried with the continue on error and no joy - if I switch the OS to a clean copy of W11 - it completes the client install and then stops at that point, and no applications are installed

 

So it seems like it probably isn't a driver issue, as it can pull down the wim file and apply it - but the post client installs just don't start