Good Afternoon All - I've been having issues adding drivers to my boot images for over a month now. For a while, i thought I may be using the wrong drivers, but now am pretty sure that's not the issue. Here's why: I performed a test this morning on my default SCCM Boot Image x86. I didn't add/remove any drivers from it, I just Updated the dist points. It gave me the results between the next two lines: --------------------------------------------------------------------------------------------------------------------------------- Error: Boot image to update: · Microsoft Windows PE (x86) Error: Actions to perform: · Add ConfigMgr binaries · Enable Windows PE command line support · Add drivers Success: Drivers that will be included: · Smart Array B400I Controller · HP ProLiant Enhanced Management Controller · Intel(R) PRO/1000 PT Dual Port Network Connection · Smart Array P800 Controller · VMware SVGA 3D (Microsoft Corporation - WDDM) Error: Failed to import the following drivers: · Intel(R) 82567LM-3 Gigabit Network Connection - Failed to inject a ConfigMgr driver into the mounted WIM file Error: The wizard detected the following problems when updating the boot image. · Failed to inject a ConfigMgr driver into the mounted WIM file Failed to inject a ConfigMgr driver into the mounted WIM file Failed to inject a ConfigMgr driver into the mounted WIM file Failed to inject a ConfigMgr driver into the mounted WIM file Failed to inject a ConfigMgr driver into the mounted WIM file Failed to inject a ConfigMgr driver into the mounted WIM file Failed to inject a ConfigMgr driver into the mounted WIM file Failed to inject a ConfigMgr driver into the mounted WIM file Failed to inject a ConfigMgr driver into the mounted WIM file Failed to inject a ConfigMgr driver into the mounted WIM file Failed to inject a ConfigMgr driver into the mounted WIM file Failed to inject a ConfigMgr driver into the mounted WIM file Failed to inject a ConfigMgr driver into the mounted WIM file Failed to inject a ConfigMgr driver into the mounted WIM file The ConfigMgr Provider reported an error.: ConfigMgr Error Object: instance of SMS_ExtendedStatus { Description = "Failed to insert OSD binaries into the WIM file"; ErrorCode = 2152205056; File = "c:\\qfe\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp"; Line = 4262; ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook"; Operation = "ExecMethod"; ParameterInfo = "SMS_BootImagePackage.PackageID=\"PEN00001\""; ProviderName = "WinMgmt"; StatusCode = 2147749889; }; --------------------------------------------------------------------------------------------------------------------------------- I noted which drivers were successful and what one failed. I opened the properties of the boot image and removed the one NIC driver which it said failed. I then updated the dist points again. Here are the next results: --------------------------------------------------------------------------------------------------------------------------------- Error: Boot image to update: · Microsoft Windows PE (x86) Error: Actions to perform: · Add ConfigMgr binaries · Enable Windows PE command line support · Add drivers Success: Drivers that will be included: · HP ProLiant Enhanced Management Controller · Intel(R) PRO/1000 PT Dual Port Network Connection · Smart Array P800 Controller · VMware SVGA 3D (Microsoft Corporation - WDDM) Error: Failed to import the following drivers: · Smart Array B400I Controller - Failed to inject a ConfigMgr driver into the mounted WIM file Error: The wizard detected the following problems when updating the boot image. · Failed to inject a ConfigMgr driver into the mounted WIM file Failed to inject a ConfigMgr driver into the mounted WIM file Failed to inject a ConfigMgr driver into the mounted WIM file Failed to inject a ConfigMgr driver into the mounted WIM file Failed to inject a ConfigMgr driver into the mounted WIM file Failed to inject a ConfigMgr driver into the mounted WIM file Failed to inject a ConfigMgr driver into the mounted WIM file Failed to inject a ConfigMgr driver into the mounted WIM file Failed to inject a ConfigMgr driver into the mounted WIM file The ConfigMgr Provider reported an error.: ConfigMgr Error Object: instance of SMS_ExtendedStatus { Description = "Failed to insert OSD binaries into the WIM file"; ErrorCode = 2152205056; File = "c:\\qfe\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp"; Line = 4262; ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook"; Operation = "ExecMethod"; ParameterInfo = "SMS_BootImagePackage.PackageID=\"PEN00001\""; ProviderName = "WinMgmt"; StatusCode = 2147749889; }; --------------------------------------------------------------------------------------------------------------------------------- As you can see in this one, a different driver that was successful before failed this time. I've tried this before and it will keep doing this until all drivers are removed. Previously, I've tried reinstalling WAIK, but don't believe that fixed it. I will be happy to post any log files or try anything you suggest. I was going to attempt the WAIK uninstall/reinstall again today, but didn't know which WAIK version to use. I was going to use the newest one for Win7 SP1, but didn't know if it was compatible - Any suggestions would be greatly appreciated - Thanks! Ben K.

A couple of comments here. You shouldn't add drivers to the the boot image unless you need them. That means there is no reason to add anything expect NIC drivers and sometimes storage drivers. Also, don't add them until you know the boot image doesn't already have them included: The boot images for SP2 are based on Win 7 and therefore include a lot of drivers already. As for your specific error above, this usually is cause by the server account for the system hosting the SMS Provider not having access to or unable to locate the driver in the orginal location that you imported the driver from. The boot image injection process does not pull drivers from the driver packages, but instead from the location you imported the driver from so make sure that this is still available and accessible by the server SMS PROVider's server account via UNC.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

Hi, You can take this document as a reference: http://technet.microsoft.com/en-us/library/bb680705.aspx Also the 2152205056 error can be generated when there is a loop in the distribution process for instance when you have dependencies on one or more packages that wait for each other. Thanks

Also, make sure you have started your SCCM console with "Run as Administrator". WAIK likes that...http://scug.be/blogs/nico Twitter: @nsienaert

You must be kidding... I try to keep things organized so below is how I import drivers... Extract and copy drivers locally onto primary SCCM server Import drivers and choose the UNC pat of the local folder they are in After importing, delete the local source So, this is why they may be failing? Is it only the boot images that pull from the source driver folder instead of DP or does another process too? Luckily, I still have all the drivers. Guess I'll delete and recreate the DB today. Thanks!Ben K.

Don't delete the local source. If you look at the properties of any driver, they reference this path explicitly and it is this path that used when insert the drivers into boot images.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys