Lenovo E560 Laptops PXE Boot OK But SCCM Crashes Out - Help!

[Fazza]

I've come back to work after having 2wks off annual leave and my boss has left me a pile of shiny new Lenovo Laptops (E560 models). I need to get them set up ready for September but they wont SCCM for some reason.

 

They PXE Boot OK and actually start to load SCCM - they get as far as displaying our personalised 'splash screen' and just when they should be showing the list of available Task Sequences they reboot!

 

Help!

[ReadTheNetwork]

Sounds like drivers, have you enabled the debug F8 prompt? If so press F8 and check it's got an IP address, then check if you can see a local HDD. Let me know if you need more info. If it is missing a driver, after downloading it onto a USB stick you can test it on the machine by using drvload in the F8 command prompt to test loading a driver and see if it picks it up.

 

Then add that driver the the boot.wim

Edited August 1, 2016 by ReadTheNetwork

[Fazza]

Sounds like drivers

 

Of course it is! This is what happens when you have two weeks off in a row (well for me anyway) it takes a while for all the knowledge to creep back in to my brain!

 

No IP address at the command prompt confirms that you're right, the NIC driver needs to be injected in to the boot.wim file - done this a few times before so should have remembered!

 

Thanks

[ReadTheNetwork]

Hope it was a good holiday . Holidays are made to forget about work. Out of curiousity have you updated your sccm to 1511? Came out in December, has a few more tools like Virtual Hard Disks, and supports 10 more. It's pretty straight forward to upgrade.

[Fazza]

We're on 1602 with 3 1602 hotfixes via the Cloud Services Updates and Servicing section

[Fazza]

The driver has injected OK in to the PXE boot.wim file so I now have an IP address so it can connect to the SCCM server and run the Task Sequence.

 

Only issue now is none of the drivers are getting installed in to the image that is part of the task sequence! I've even tried adding them as an Application during the task sequence taking advantage of silent installs (done this numerous times before and it's always worked).

 

Had this problem before with another Lenovo (T410 I think) so we have to manually install the drivers after imaging via SCCM.

 

Is there something special that needs to be done on these particular models of Lenovo laptops?

[ReadTheNetwork]

I presume it does start the driver install process but just crashes out!? I'd try the auto apply drivers (limiting it to just that driver package), with the wmi query aiming to that laptop. Auto apply drivers just continues adding drivers I think certain drivers like Bluetooth may cause issues. Edited August 3, 2016 by ReadTheNetwork

[Fazza]

I presume it does start the driver install process but just crashes out!? I'd try the auto apply drivers (limiting it to just that driver package), with the wmi query aiming to that laptop. Auto apply drivers just continues adding drivers I think certain drivers like Bluetooth may cause issues.

 

That was the first thing I tried. As a test, using the same Driver that was successfully injected in to Windows PE - but after it completes the Task Sequence the Laptop is still in a Workgroup and the Network card driver is not installed. If I run the same Task Sequence on another computer (completely different brand/model) then it works OK and puts the computer on the domain so it's definitely something to do with these laptops.

[ReadTheNetwork]

How are you injecting the drivers into your image? Do you have a task sequence similar to:

Apply Drivers - Driver Package (Lenovo e560 drivers); Options/Add Condition (select * from win32 computersystem where model like %e560%)?

Double check the model is correct on the laptop within the PE in the command prompt type X:\wmic computersystem get model.

 

The above should confirm the model is typed correctly.

 

If the above works, and it 'bombs out' try disabling that task sequence and adding the Auto Apply Drivers task, and limit it to the driver package for the laptop. Then within options do the same condition as above for the wmi query.