nhottinger Posted December 29, 2015 Report post Posted December 29, 2015 Bear with me, I'm new and don't know a lot about how this all works yet. I've had very little training and trying to figure it out on my own. I'm having issues importing new nic drivers into existing boot images so I can image new devices as they come in. Currently trying to image a Dell Optiplex 7040. When I try to add the drivers to my default x64 boot image, it errors out and says failed to inject a configmgr driver to the mounted wim file. No idea how to fix that. Could I just create a new boot wim with only the new drivers I need? If so, how can I make the PXE boot look at that boot image instead of the previous one I have been using. Each time I try, it looks at the old boot image to pxe boot, which then the osd task fails to even start. Quote Share this post Link to post Share on other sites More sharing options...
YPCC Posted December 29, 2015 Report post Posted December 29, 2015 Firstly temporarily disable AV software on your sccm server. I have had countless problems with McAfee blocking me from creating a Boot Image in SCCM as it detects it as a threat. Everytime I change a boot image I have to disable McAfee (I have been to lazy to put exceptions in McAfee) Secondly, what specific errors are you getting. Error codes are vital for narrowing down issues in sccm. In order to make PXE boot directly to your new boot image, you need to make sure the option of "Deploy this image from a PXE enabled point" is enabled (re-distribute the boot image to the DP after doing this). Then also ensure you deploy a task sequence that uses your new boot image. SCCM uses a "last deployed" rule, so whatever boot image you last deployed, will be the one that gets used by PXE. Quote Share this post Link to post Share on other sites More sharing options...
nhottinger Posted December 29, 2015 Report post Posted December 29, 2015 I created a new boot image (x86) and verified there were no drivers associated with it already. At that point, I'm able to update the distribution point successfully. I then went through all the driver packages I need drivers for and added the NIC drivers to the new boot image. When I attempt to update the distribution points after that, it fails "Failed to inject a ConfigMgr drive into the mounted WIM file. Looks like most of the drivers made it though. Is that a correct assumption? Error: Boot image to update: • Microsoft Windows PE (x86) Error: Actions to perform: • Add ConfigMgr binaries • Disable Windows PE command line support • Add drivers Success: Drivers that will be included: • Intel® 82580 Gigabit Network Connection • Intel® 82575EB Gigabit Network Connection • Dell Wireless 5620 (EV-DO-HSPA) Mobile Broadband Mini-Card Network Adaptor • Dell TrueMobile 1300 WLAN Mini-PCI Card • 3Com Dual Port 1000-SX PCI-X Server NIC • Dell TrueMobile 1300 WLAN Mini-PCI Card • Realtek PCI GBE Family Controller • Realtek PCI GBE Family Controller • Intel® 82580 Gigabit Network Connection • Intel® Centrino® Wireless-N 100 • Broadcom NetLink Gigabit Ethernet • Realtek PCI GBE Family Controller • Dell Wireless 5540 HSPA Mini-Card Network Adapter • Intel® 82579LM Gigabit Network Connection • Intel® Dual Band Wireless-N 7260 • Intel® Ethernet Connection I217-LM • Realtek PCI GBE Family Controller • Intel® 82575EB Gigabit Network Connection • Dell TrueMobile 1300 WLAN Mini-PCI Card • Dell Wireless 5630 (EVDO-HSPA) Mobile Broadband Mini-Card (Composite WWAN Device) Network Adapter • Intel® Ethernet Connection I217-LM • 3Com Dual Port 1000-SX PCI-X Server NIC • Dell Wireless 5620 (EV-DO-HSPA) Mobile Broadband Mini-Card • Dell TrueMobile 1300 WLAN Mini-PCI Card • Broadcom Virtual Wireless Adapter • Dell Wireless 5620 (EV-DO-HSPA) Mobile Broadband Mini-Card • Dell Wireless 5540 HSPA Mini-Card Network Adapter • 3Com Dual Port 1000-SX PCI-X Server NIC • Intel® Centrino® WiMAX 6250 • Dell Wireless 5806 Gobi 4G LTE Mobile Broadband Card • Intel® Ethernet Connection I217-LM • Broadcom NetLink Gigabit Ethernet • 3Com Dual Port 1000-SX PCI-X Server NIC • Intel® 82575EB Gigabit Network Connection • Dell Wireless 5630 (EVDO-HSPA) Mobile Broadband Mini-Card (Composite WWAN Device) Network Adapter • Intel® Dual Band Wireless-AC 3160 • Broadcom NetLink Gigabit Ethernet • Realtek PCI GBE Family Controller • Realtek PCI GBE Family Controller • Dell Wireless 5620 (EV-DO-HSPA) Mobile Broadband Mini-Card • Dell Wireless 5730 Sprint Mobile Broadband (EVDO Rev-A) Minicard Network Adapter • Intel® WiFi Link 5300 AGN • Dell Wireless 1515 Wireless-N Adapter • Realtek PCI GBE Family Controller • Dell TrueMobile 1300 WLAN Mini-PCI Card • Intel® 82567LM-3 Gigabit Network Connection • Broadcom Virtual Wireless Adapter • Intel® Ethernet Connection I217-LM • Intel® WiFi Link 5300 AGN • Intel® 82579LM Gigabit Network Connection • Realtek PCI GBE Family Controller • Intel® 82579LM Gigabit Network Connection • LAN7500 USB 2.0 to Ethernet 10/100/1000 Adapter • Intel® 82567LM Gigabit Network Connection • Intel® 82580 Gigabit Network Connection • Intel® 82579LM Gigabit Network Connection • Broadcom NetLink Gigabit Ethernet • Dell Wireless 5806 Gobi 4G LTE Mobile Broadband Card • Intel® WiFi Link 5300 AGN • Intel® Centrino® Wireless-N 100 • Broadcom NetLink Gigabit Ethernet • 3Com Dual Port 1000-SX PCI-X Server NIC • Dell Wireless 5730 Sprint Mobile Broadband (EVDO Rev-A) Minicard Network Adapter • Intel® 82575EB Gigabit Network Connection • Intel® Dual Band Wireless-N 7260 • Dell Wireless 1515 Wireless-N Adapter • Broadcom NetLink Gigabit Ethernet • Intel® Ethernet Connection I217-LM • Dell Wireless 5630 (EVDO-HSPA) Mobile Broadband Mini-Card (Composite WWAN Device) Network Adapter • Intel® Centrino® Wireless-N 100 • Intel® 82567LM-3 Gigabit Network Connection • Intel® 82567LM-3 Gigabit Network Connection • Dell Wireless 5620 (EV-DO-HSPA) Mobile Broadband Mini-Card • Intel® Centrino® Wireless-N 100 • Dell TrueMobile 1300 WLAN Mini-PCI Card • Broadcom Virtual Wireless Adapter • Dell Wireless 1515 Wireless-N Adapter • Broadcom NetLink Gigabit Ethernet • Intel® Centrino® Wireless-N 100 • Intel® Dual Band Wireless-AC 3160 • Intel® Ethernet Connection I217-LM • Intel® 82579LM Gigabit Network Connection • Realtek PCI GBE Family Controller • Intel® 82579LM Gigabit Network Connection • Broadcom NetLink Gigabit Ethernet • Dell Wireless 5806 Gobi 4G LTE Mobile Broadband Card • Dell Wireless 5620 (EV-DO-HSPA) Mobile Broadband Mini-Card • Dell TrueMobile 1300 WLAN Mini-PCI Card • Intel® 82579LM Gigabit Network Connection • Broadcom Virtual Wireless Adapter • Intel® 82567LM Gigabit Network Connection • Broadcom NetLink Gigabit Ethernet • Broadcom NetLink Gigabit Ethernet • Dell TrueMobile 1300 WLAN Mini-PCI Card • Intel® Dual Band Wireless-N 7260 • Intel® WiFi Link 5350 • Intel® 82567LM-3 Gigabit Network Connection • Intel® WiFi Link 5300 AGN • Intel® Dual Band Wireless-AC 3160 • Intel® Centrino® WiMAX 6250 • Dell Wireless 5540 HSPA Mini-Card Network Adapter • Intel® Centrino® Wireless-N 100 • 3Com Dual Port 1000-SX PCI-X Server NIC • Intel® Dual Band Wireless-N 7260 • Broadcom NetLink Gigabit Ethernet • Broadcom Virtual Wireless Adapter • Intel® Centrino® WiMAX 6250 • Intel® 82575EB Gigabit Network Connection • Intel® WiFi Link 5300 AGN • 3Com Dual Port 1000-SX PCI-X Server NIC • 3Com Dual Port 1000-SX PCI-X Server NIC • Intel® Centrino® Wireless-N 100 • Intel® WiFi Link 5300 AGN • Intel® Centrino® Advanced-N 6235 • Intel® Centrino® Advanced-N 6235 • Intel® Centrino® Advanced-N 6235 • 3Com Dual Port 1000-SX PCI-X Server NIC • 3Com Dual Port 1000-SX PCI-X Server NIC • Intel® 82579LM Gigabit Network Connection • Atheros Osprey Emulation Wireless Network Adapter • Broadcom NetLink Gigabit Ethernet • LAN7500 USB 2.0 to Ethernet 10/100/1000 Adapter • F3507g Mobile Broadband Driver • Intel® WiFi Link 5300 AGN • 3Com Dual Port 1000-SX PCI-X Server NIC • Intel® 82579LM Gigabit Network Connection • Broadcom NetLink Gigabit Ethernet • Dell TrueMobile 1300 WLAN Mini-PCI Card • Dell TrueMobile 1300 WLAN Mini-PCI Card • Intel® 82579LM Gigabit Network Connection • Intel® Centrino® Advanced-N 6235 • Intel® 82580 Gigabit Network Connection • Intel® Centrino® Wireless-N 105 • Intel® Centrino® Wireless-N 100 • Intel® Dual Band Wireless-N 7260 • Intel® Dual Band Wireless-N 7260 • Intel® 82579LM Gigabit Network Connection • Dell Wireless 5630 (EVDO-HSPA) Mobile Broadband Mini-Card (Composite WWAN Device) Network Adapter • 3Com Dual Port 1000-SX PCI-X Server NIC • Broadcom NetLink Gigabit Ethernet • Broadcom Virtual Wireless Adapter • Intel® WiFi Link 5350 • 3Com Dual Port 1000-SX PCI-X Server NIC • Intel® Ethernet Connection I217-LM • Dell Wireless 5806 Gobi 4G LTE Mobile Broadband Card • Dell Wireless 1515 Wireless-N Adapter • Dell Wireless 5630 (EVDO-HSPA) Mobile Broadband Mini-Card (Composite WWAN Device) Network Adapter • DW5800 4G (LTE-3G) Mobile Broadband Mini-Card Network Adapter • Broadcom Virtual Wireless Adapter • Intel® Centrino® Advanced-N 6235 • Realtek PCI GBE Family Controller • Intel® Centrino® Wireless-N 105 • Intel® Centrino® Wireless-N 100 • 3Com Dual Port 1000-SX PCI-X Server NIC • Intel® Centrino® Wireless-N 100 • Dell TrueMobile 1300 WLAN Mini-PCI Card • 3Com Dual Port 1000-SX PCI-X Server NIC • 3Com Dual Port 1000-SX PCI-X Server NIC • Intel® 82580 Gigabit Network Connection • Dell Wireless 5730 Sprint Mobile Broadband (EVDO Rev-A) Minicard Network Adapter • Intel® 82580 Gigabit Network Connection • Intel® Centrino® WiMAX 6250 • Intel® Centrino® Advanced-N 6235 • Intel® Centrino® Wireless-N 100 • Broadcom NetLink Gigabit Ethernet • Intel® 82580 Gigabit Network Connection • Intel® 82580 Gigabit Network Connection • Broadcom NetLink Gigabit Ethernet • Intel® 82567LM-3 Gigabit Network Connection • Intel® WiFi Link 5300 AGN • Intel® Centrino® Wireless-N 100 • Dell Wireless 1515 Wireless-N Adapter • Intel® Centrino® Wireless-N 100 • Dell Wireless 5806 Gobi 4G LTE Mobile Broadband Card Error: Failed to import the following drivers: • Dell TrueMobile 1300 WLAN Mini-PCI Card - 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 The SMS Provider reported an error.: ConfigMgr Error Object: instance of SMS_ExtendedStatus { • Description = "Failed to insert OSD binaries into the WIM file"; • ErrorCode = 2152205056; • File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp"; • Line = 4318; • ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook"; • Operation = "ExecMethod"; • ParameterInfo = "SMS_BootImagePackage.PackageID=\"BV100150\""; • ProviderName = "WinMgmt"; • StatusCode = 2147749889; }; Quote Share this post Link to post Share on other sites More sharing options...
YPCC Posted December 29, 2015 Report post Posted December 29, 2015 Ah, so theres something to work with. Google: "boot image" 2152205056. Lots of varying issues. I'd start with the simplest - Open SCCM console using "run as administrator" - Clear the Windows\Temp folder as sccm uses that to build your temporary WIM before copying it to your chosen location - Try importing a few drivers only - Double check the driver source is all intact and hasnt been deleted or modified If you are not too concerned, there is an alternative way of injecting drivers into your boot image, although personally i would advise doing it via sccm so you can remove driver easily later on. The alternative method is using DISMGUI. It allows you to modify the .wim file directly, bypassing sccm completely. See this for how to: http://www.deploymentninja.com/home/easily-add-drivers-and-updates-to-images-with-gui-dismI used this method at my current organisation as we were gtting various issues injecting drivers and in the end i got fed up and injected them offline using DISMGUI. Works without issues, the only downside is removing a driver (if you ever needto) will be tricky 1 Quote Share this post Link to post Share on other sites More sharing options...
nhottinger Posted December 30, 2015 Report post Posted December 30, 2015 Thanks, I ended up removing the drivers it didn't like (it took a while, about 20 drivers or so) but I finally got it to go through. I'll delete the Windows\Temp files as well. Thank you for all your help. Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted December 31, 2015 Report post Posted December 31, 2015 id suggest you only add network (or storage) drivers as needed, adding hundreds of drivers will bloat the boot wim and make it harder to service later on... also, you are importing wireless drivers in the mix and theres no need for them they are not supported at all during pxe boot even if some people come up with hacks to make it work, so, long story short, i'd recommend you start with a clean boot image again, and ONLY import the nic drivers needed, here's some videos where i go into lots of details about adding drivers to boot images (surface pro 3 is the example but there's good info in there), lastly, since you are new to this i'd recommend you get some training or buy one of the many excellent books out there, for example these the first one in the list was written by yours truly and covers managing boot images with drivers manually as well as via powershell good luck ! Quote Share this post Link to post Share on other sites More sharing options...
nhottinger Posted January 4, 2016 Report post Posted January 4, 2016 (edited) I've created a new boot.wim specifically for the testing of this Optiplex 7040. I've cleaned out all drivers that are not needed and only imported the ones related to the 7040. Still no luck. When I update the distribution point with only 5 network drivers, it will fail on one, but says it was successful on the other 4. I remove the one that failed and try to redistribute. It then fails on one that was previously successful. I keep doing this until I have no drivers left. Now I'm going back through and trying to redistribute other .wims that had previously worked just fine and getting the same error that it can't inject the drivers. Edited January 4, 2016 by nhottinger Quote Share this post Link to post Share on other sites More sharing options...
nhottinger Posted January 5, 2016 Report post Posted January 5, 2016 Dumb question, why don't some drivers import into the boot.wim? Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted January 5, 2016 Report post Posted January 5, 2016 because they are probably not applicable, can you post any errors you are seeing, and also at the time of the import failure what does the smsprov.log file tell you about the problem ? Quote Share this post Link to post Share on other sites More sharing options...
nhottinger Posted January 5, 2016 Report post Posted January 5, 2016 I was able to get us somewhat limping along, but still can't get the Optiplex 7040. I was able to add three drivers successfully from the driver package to the boot.wim, but when we start the image process, it never gets to the password screen to start. F8 command does not show I have a valid IP address and the pc just reboots. I'm assuming this is a driver issue but nothing is working. Quote Share this post Link to post Share on other sites More sharing options...