Windows 10 Task Sequence Failing

[thamoomin81]

Wondering if anyone can help, I have recently upgraded our SCCM environment to allow for us to start deploying Windows 10, I have created the Windows 10 image and imported it into SCCM and created the deployment task sequence. The issue I have is that I have tested a deployment on two different devices (Lenovo L470 laptop and HP 400 G4 DM), both appear to fail at the same point, from what I can tell from the smsts log (attached) just before joining the domain and installing any applications/packages, I can see no obvious red flags in the log, just a mention of not being able to release the task sequence related to the Windows image (BRS0007E) but this is further up the log, pretty much every other task sequence I have had failed in the past has been related to the NIC driver but there are none of the usual error messages and this task sequence isn't failing mid-way, the O/S reboots and boots up into Windows 10 but with no drivers or applications/packages installed and also not joined to our domain. If someone can please take a look smsts.log to see if I'm missing something glaringly obvious.

Details: SCCM 5.0.8412.1000 - Client 5.0.8412.1307 - ADK 10.1.14393.0 - Windows 10 1607 image

Thanks

 

smsts.log

[Config Mangler]

Looks like it's skipping installing your driver packages as it's evaluating them to be false.

"The action (HP ProDesk 400 G2.5 SFF) has been skipped because the condition is evaluated to be false"

Is that really the WMI name of that model?

 

[SCCMentor]

Run a WMIC query on the machine to get the details

CSProduct Get Name

https://sccmentor.com/2013/05/20/find-out-the-computers-model-type-from-a-wmi-query/

[thamoomin81]

34 minutes ago, Config Mangler said:

Looks like it's skipping installing your driver packages as it's evaluating them to be false.

"The action (HP ProDesk 400 G2.5 SFF) has been skipped because the condition is evaluated to be false"

Is that really the WMI name of that model?

 

Apologies, the model laptop for the log I attached was HP 400 G3 DM, not G4, it was the G3 model I tested it on and it does correctly find the driver package, it even downloads the drivers, they are in the _SMSTaskSequence folder.

Expand a string: SELECT * FROM Win32_ComputerSystem WHERE Model LIKE "%HP ProDesk 400 G3 DM%" 
 

[Config Mangler]

OK... You say it's doing the drivers. Are you getting an IP address - what does ipconfig /all tell you?

[thamoomin81]

On ‎23‎/‎06‎/‎2017 at 11:07 AM, Config Mangler said:

OK... You say it's doing the drivers. Are you getting an IP address - what does ipconfig /all tell you?

This is the issue really, usually when I have had a task sequence fail in the past it has failed while in WinPE with a specific error message/code, I can then F8 and check ipconfig etc but this is just failing and rebooting into Windows 10 with no drivers installed. This is looking like another NIC issue the more I look at it, tbh I just wanted someone to check the smsts.log to see if I was missing something. What was also making me think it was not NIC related was that for example the Lenovo laptop I had downloaded the SCCM package, which I would hope had the correct NIC drivers. Thanks for the input, I'm going down the path of NIC related and will try some different driver versions.

[CripWalk]

Looking at the log file, it looks like the machine you are imaging is grabbing an IP address.

I think you named the SCCM task/action wrong. The TS action "HP ProDesk 400 G4 DM" (which should be your drivers package for G4 DM) has a condition "SELECT * FROM Win32_ComputerSystem WHERE Model LIKE "%HP ProDesk 400 G3 DM%". 

I would make sure to correct the action name to match the machine name being evaluated by the query and confirm that the drivers included in the G3 DM package are correct.

 

[CripWalk]

I would check the drivers package BRS0007C that was evaluated and installed. Is it pointing to drivers for HP Prodesk 400 G3 DM or HP ProDesk 400 G4 DM or any other model for that matter?.