Boot images fails to update due to Lenovo drivers

Question

Have two customers with SCCM 2107 with HF Rollup that can't update anymore the default SCCM boot images. The process starts and ends with several red ticks. Have clean up all the outdated drivers, but this doesnt makes a difference.

Have then examined dism.log and found a very strange behaviour. When updating the boot image in the SCCM admin console, dism.exe logs entries like the following:

2021-11-25 18:30:41, Info DISM DISM.EXE: Executing command line: "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /image:"C:\Windows\TEMP\BootImages{83D93D6A-1AF2-4D17-A693-04E95067E12A}\mount" /Add-Driver /Driver:"\srv-sccm01\CM_OSDeployment\DriverSources\Lenovo-WinPE-270\WIN10\64\rtux64w10.INF"

What I can't understand at all is where and why SCCM is adding the parameter "/add-driver..." to the dism.exe process. The Lenovo driver logged above is indeed outdated. Has anyone a hint or idea where SCCM is taken this information from, and how we can delete this?

Thanky you all in advance for any help.
Franz

Answer 1

Thank you for your proposal.

According our experience, it takes hours of phone calls and log collections when opening a Microsoft support case until they even start to looking at the problem (despite we are a MS Gold Partner).

What we have done is that we imported the x64 vanilla boot image from ADK and customized it in the SCCM Admin console identically like the non working boot image. This new boot image can be distributed and works fine.

Answer 2

These are drivers you have added to the boot image in the ConfigMgr console per the guidance at https://learn.microsoft.com/en-us/mem/configmgr/osd/get-started/manage-boot-images#drivers. Whenever you update a boot image, the drivers are re-injected as updating is really creating a new boot image from the base boot image and injecting all necessary components. For drivers, the original source location that you imported the drivers from is what is used to (re-)inject them into the boot image and thus, these must still exist in the location specified. If not, the process will fail and you will need to address this.

Answer 3

Thank you for your explications.

I have should clarify that we have removed these Lenovo Drivers from the Boot Image Properties as described in https://learn.microsoft.com/en-us/mem/configmgr/osd/get-started/manage-boot-images#drivers, and have removed these drivers as well from the drivers node in the SCCM console. Despite that, SCCM has stored these removed drivers somewhere (in the database?) and tries to reinject them and then fails when why try to "update distribution points" on the boot image.

Franz

Answer 4

That sounds like some more investigation may be needed as this could be a bug. You should open a support case to investigate further.

Answer 5

While that's a valid path, I don't really consider that a good path going-forward although that's for you to decide.

As for getting bugs addressed and support, the process can sometimes be time consuming for sure but is generally required so that we can investigate the problem in-depth and determine what the root cause is. Without this, there's no way for us to know what actually needs to be done here as many issues are configuration or environment related while some are truly design or code defects. Opening support cases helps us as well as we don't know about every possible issue that customers may or have hit and thus can't address what we don't know about.

At the very least, please file feedback on this in the ConfigMgr admin console.