Recently I was troubleshooting a strange issue with OSD Driverpacks in SCCM 2007. I would like to share the solution for my issue because I spent a lot of time on this issue and there is not a lot of info on the Internet. The SCCM 2007 environment that I was troubleshooting was with MDT 2010 integration.
Every driver package was failing to apply drivers to a Windows 7 x86 Edition. I first thought it was a malfunctionning driver because all driver packages were downloading fine but were not injecting the drivers to the Windows 7 driver store. I changed the driver packages to only a few essential drivers but it kept failing.
I had the following errors in the SMSTS.log:
Failed to add driver to driver store. Code 0x8022001b
Failed to provision driver. Code 0x8022001b
Image may be NSFW.
Clik here to view.
Further in the DISM.log file I found the following:
8022001b [Error,Facility=FACILITY_STATE_MANAGEMENT,Code=27 (0x001b)] #28# from CChildContextStore::CreateListSetting(path = /settings/DriverPaths, settingName = PathAndCredentials[@keyValue="1"], enumerator = @0x346f08, settingType = 16 (0x00000010))[gle=0x80004005]
Image may be NSFW.
Clik here to view.
The Dism.log file contains all info about injecting drivers to Windows 7 because WINPE is using DISM.exe to inject the drivers to the Windows 7 drivers store.
So I tried a lot of things to solve this but I ended up to solve this via the following way:
- Generate a new MDT 2010 WINPE boot image.
- Launch a new image capture with the newly generated WINPE image.
- Create a new Operating System Image Package.
- Deploy the New image with the newly generated WINPE image.
Firstly I already created a new image but with the old WINPE image but this didn’t solve the problem. It’s very important to create a completely fresh WINPE image to solve this issue. I am not sure what exactly the problem but it must be somewhere in the WINPE image.
My advice is also don’t use special characters in the names of the driver packages and folder names.
Hope this can help someone.
Image may be NSFW.
Clik here to view.
Image may be NSFW.Clik here to view.
