Solved

SCCM cant add drivers to driver package

Posted on 2016-07-18
11
534 Views
Last Modified: 2016-07-31
Hi, I have imported drivers for HP 840 G3, under drivers in SCCM console, now i am trying to add them to drivers package, but i am getting the following error attached, even if i try to add one driver, it gives the same error.
thanks.
drivers.jpg
0
Comment
Question by:Leo
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 5
11 Comments
 
LVL 8

Author Comment

by:Leo
ID: 41718208
When I was trying to Distribute the Network driver to distribution points, i got the following errors;

  Error: Boot image to update:
•      Microsoft Windows PE (x86)
 
  Error: Actions to perform:
•      Add ConfigMgr binaries
•      Set scratch space
•      Enable Windows PE command line support
•      Add drivers

  Error: Failed to import the following drivers:
•      HP lt4120 Snapdragon X5 LTE Download Interface - 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 = 4566;
•      ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
•      Operation = "ExecMethod";
•      ParameterInfo = "SMS_BootImagePackage.PackageID=\"TT100084\"";
•      ProviderName = "WinMgmt";
•      StatusCode = 2147749889;
};
0
 
LVL 28

Expert Comment

by:Michael Pfister
ID: 41718239
What version, servicepack and maybe hotfix level are you running?

Have a look at smsprov.log on your server and look for the error.
0
 
LVL 8

Author Comment

by:Leo
ID: 41719103
I am away from my computer, its SCCM 2012 R2  and not sure about the hotfix.
0
SharePoint Admin?

Enable Your Employees To Focus On The Core With Intuitive Onscreen Guidance That is With You At The Moment of Need.

 
LVL 8

Author Comment

by:Leo
ID: 41720153
Sorry the correct version is SCCM 2012, SP1 version 5.0.7804.

Error in smsprov.log

*~*~e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\sspbootimagepackage.cpp(4566) : Failed to insert OSD binaries into the WIM file~*~*      SMS Provider      19/07/2016 3:38:22 PM      7312 (0x1C90)
*~*~Failed to insert OSD binaries into the WIM file ~*~*      SMS Provider      19/07/2016 3:38:22 PM      7312 (0x1C90)
0
 
LVL 28

Assisted Solution

by:Michael Pfister
Michael Pfister earned 500 total points
ID: 41720247
A good starting point is to replace the already modified boot.wim with the original one that came with the ADK:

"1.Rename the defect boot.wim file in the folder <sms install folder>\osd\boot\i386 to boot.bak
2.Now copy the winpe.wim file from %ProgramFiles(x86)%\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us\ to <sms install folder>\osd\boot\i386 and rename it to boot.wim
3.Repeat the copy for each boot.<packageid>.wim in the target folder
4.Now run Update distribution points to test if the boot image is updatable again

Repeat the process for the x64 boot image."

See http://blog.coretech.dk/rja/post-sccm-2012-sp1-failure-to-update-boot-images/
0
 
LVL 28

Expert Comment

by:Michael Pfister
ID: 41720249
Also make sure the original source of ALL injected drivers is still available/accessible
0
 
LVL 8

Author Comment

by:Leo
ID: 41720272
thanks, I will do as you suggested.
for permissions, which accounts needs to have access where boot.wim file resides?
0
 
LVL 8

Author Comment

by:Leo
ID: 41722185
sorry still getting the same error :-(

Error: Failed to import the following drivers:
•      HP lt4120 Snapdragon X5 LTE Download Interface - 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 = 4566;
•      ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
•      Operation = "ExecMethod";
•      ParameterInfo = "SMS_BootImagePackage.PackageID=\"TT100084\"";
•      ProviderName = "WinMgmt";
•      StatusCode = 2147749889;
0
 
LVL 28

Expert Comment

by:Michael Pfister
ID: 41722969
Try to remove the driver its complaining about.
0
 
LVL 8

Author Comment

by:Leo
ID: 41728811
I did, but the error is same.....
0
 
LVL 28

Accepted Solution

by:
Michael Pfister earned 500 total points
ID: 41729323
If you removed  HP lt4120 Snapdragon X5 LTE Download Interface it shouldn't complain about it.
Maybe another driver with similar name?
0

Featured Post

Free eBook: Backup on AWS

Everything you need to know about backup and disaster recovery with AWS, for FREE!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The following article is intended as a guide to using PowerShell as a more versatile and reliable form of application detection in SCCM.
Determining the an SCCM package name from the Package ID
In an interesting question (https://www.experts-exchange.com/questions/29008360/) here at Experts Exchange, a member asked how to split a single image into multiple images. The primary usage for this is to place many photographs on a flatbed scanner…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question