09-06-2018 09:51 AM - edited 09-06-2018 11:38 AM
I am using SCCM 1606
L380 1703 recent driver package from Sept 02, 2018 https://support.lenovo.com/us/en/downloads/ds502364 recommended from recipe card https://download.lenovo.com/cdrt/recipes/tp_l380_w1064.pdf
UEFI BIOS version: RORET29W (1.12)
My task sequence is essentially:
Format and Partition disk
Install OS (Clean boot 1703 wim. Captured from a VM with no embedded drivers (vmware tools uninstalled)
Install ONLY L380 Drivers
Bios settings adjusted in order to PxE Boot:
Security -> Secure Boot "Disabled"
Startup -> UEFI/Legacy Boot "Legacy Only"
Upgrading SCCM to support UEFI is on my list of things to do. However, we have been successful imaging 1703 on T470, T480, P51, and P52s with similar BIOS configurations.
Attached is a .zip with the smsts.log gathered from the beginning of the task sequence until warning at the reboot step (bottom of smsts2.log)
Each time the machine reboots it gets stuck on an unresponsive black screen. One of the examples of this is after install driver step, the machine reboots into the defualt operating system. Stays on unresponsive black screen with mouse cursor. Need to manually force restart the machine in order for task sequence to continue. It ends up finishing successfully (i.e. the task sequence completes and 1703 with all necessary apps comes out of the pipe), but each time it restarts, it gets stuck leading to a technician having to force restart again (7 times in total). It eventually finished, but obviously is clunky.
Changed boot method from MBR to GPT, problem persists.
Solved! Go to Solution.
09-07-2018 10:11 AM
09-07-2018 11:52 AM
Unfortunately, I deployed one of our L380's (20M5) with no issues like you're seeing. My task sequence is pretty simple, however, i did notice yours is an mdt integrated one. you mentioned your 1703 WIM was captured from a VM. What do you mean by clean boot WIM? If it was captured, is it patched with the latest (at least the last couple of months) cumulative update and servicing stack update?
i also set my system BIOS (revision 1.14) OS optimized defaults to disabled, which disables secure boot, and set the boot mode to legacy only. my format/partition disk step is configured as:
Disk Type: MBR
System Reservered (Primary): 350MB fixed-NTFS, marked as boot partition, no drive letter assigned
Windows (Primary): 99% free space with the variable OSDisk set
Recovery (Recovery): Remaing free space
to be honest, the black screen/cursor sounds more of a driver issue. i know you linked to the L380 support page with all 3 available windows 10 build driver packs but you're positive you're installing the 1703 drivers? looking back at the log, it looks like you're using native driver packages and have imported these drivers into the SCCM database. is that correct?
09-10-2018 09:37 AM
I meant "clean boot" as simply grabbing out 1703 iso from Microsoft Volume Licensing, building a VM from this, then capturing the .wim with the SCCM image capture tool. There are no native vmware drivers in this wim (Vmware tools uninstalled before capture). The last time I captured this wim with the latest updates/rollups was July.
Correct, MDT is integrated with the task sequence.
I'm positive that I'm including the latest 1703 drivers from that that these are installing. When I imported this package on 9/6, the package ID is OHQ00300. The attached capture.png from the same smsts.log shows how the WMI query I put in the task sequence logic is true and installed this (and only this) driver package from my driver repository.
09-10-2018 09:52 AM
correct, I did see the detection logic was evaluated to true when I originally reviewed your logs. the package ID is unique to your environment/Site Code so that won't verify if you're using the 1703 drivers or not. any chance you can screenshot your driver package in the console? what's the driver count?
09-10-2018 02:52 PM
I just created a non-mdt integrated task sequence- same issue unfortunately. After install drivers step, it will restart but not boot to OS. Same issue with the unresponsive black screen and mouse. Happy to hop on a call to further discuss.
09-10-2018 02:57 PM
This is essentially the same issue:
09-11-2018 06:40 AM