Solved

SCCM cant add drivers to driver package

Posted on 2016-07-18
11
635 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
Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

 
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

Increase Agility with Enabled Toolchains

Connect your existing build, deployment, management, monitoring, and collaboration platforms. From Puppet to Chef, HipChat to Slack, ServiceNow to JIRA, Splunk to New Relic and beyond, hand off data between systems to engage the right people.

Connect with xMatters.

Question has a verified solution.

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

Back in July, I blogged about how Microsoft's new server pricing model, combined with the end of the Small Business Server package, would result in significant cost increases for many small businesses (see SBS End of Life: Microsoft Punishes Small B…
I have put this article together as i needed to get all the information that might be available already into one general document that could be referenced once without searching the Internet for the different pieces. I have had a few issues where…
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…
Do you want to know how to make a graph with Microsoft Access? First, create a query with the data for the chart. Then make a blank form and add a chart control. This video also shows how to change what data is displayed on the graph as well as form…

691 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