When Updating x64 Boot Image to the DP's, getting ErrorCode = 2152205056

Question

_{Tuesday, May 24, 2016 1:50 PM}

SCCM Environtment SCCM 2012 R2 Version 5.00.8239.1000 and Build 8239

Laptop attempting to image is Dell Latitude E7470

For some context, I have been working on setting up OS Deployment via boot media and PXE boot, and have successfully gotten the task sequence to come up on our older laptops, however on our newer laptops it can not pull an IP address once it loads the boot image, which research indicated was a driver issue. I have tried adding the various network related drivers from the vendors site (Dell), pulling the .inf files from the installers, put them on a network accessible drive, imported them into drivers in the SCCM console, added them to the correct driver package, and added them to the boot image being used. I run into the following errors when I try to update the DP's:

Error: Boot image to update: 

• Microsoft Windows PE (x64)

  Error: Actions to perform: 

• Add ConfigMgr binaries

• Set scratch space

• Enable Windows PE command line support

• Add drivers

  Success: Boot image will include these drivers after update:

• Intel(R) Advanced Network Services Virtual Adapter

• Intel(R) Ethernet Connection I217-LM

• Intel(R) 82580 Gigabit Network Connection

• Intel(R) 82579LM Gigabit Network Connection

• Intel(R) Ethernet Connection I217-LM

• Intel(R) 82580 Gigabit Network Connection

 Optional components:

• Scripting (WinPE-Scripting)

• Startup (WinPE-SecureStartup)

• Network (WinPE-WDS-Tools)

• Scripting (WinPE-WMI)

  Error: Failed to import the following drivers:

• Intel(R) 82579LM 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

The SMS Provider reported an error.: ConfigMgr Error Object:

instance of SMS_ExtendedStatus

{

• Description = "Failed to inject OSD binaries into mounted WIM file (often happens if unsigned drivers are inserted into x64 boot image)";

• ErrorCode = 2152205056;

• File = "e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\sspbootimagepackage.cpp";

• Line = 4969;

• ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";

• Operation = "ExecMethod";

• ParameterInfo = "SMS_BootImagePackage.PackageID=\P0100093\";

• ProviderName = "WinMgmt";

• StatusCode = 2147749889;

};

I am not sure if I just missed something along the way, or if I just need some sort of work around because it picks it up as unsigned. Any help or advice is greatly appreciated, I have only been working with SCCM for a few months so I am not exceptionally well versed on its inner workings.

Thanks,

Chris Skeen

All replies (5)

_{Tuesday, May 24, 2016 2:46 PM | 1 vote}

Did you know that Dell has a CAB with all drivers that you typically need to inject into your boot images: http://en.community.dell.com/techcenter/enterprise-client/w/wiki/5029.winpe-5-0-driver-cab

Did you delete the location you imported the driver(s) from? When creating or updating boot images, the driver is pulled from the import location and not the package source location. Thus, you must maintain the import location exactly as is -- don't delete, don't rename, don't rename, etc. The driver import location must remain as is and in tact.

Jason | http://blog.configmgrftw.com | @jasonsandys

_{Tuesday, May 24, 2016 9:04 PM}

Jason,

No I did not know about that, thank you! I found the issue, or at least a major piece of it, I checked the locations and found a typo had been made when updating the locations in the properties of the drivers. I fixed the typo, and it works for the ones it picks up as signed, but there is one it sees as unsigned and it still gets the same error. I will try the CAB file you mentioned first thing tomorrow and see if that resolves the issue.

Thanks, Chris Skeen

_{Wednesday, May 25, 2016 8:28 PM}

Jason,

I tried importing the .inf files from the CAB dell offers at the link you provided, after pulling them down and adding them to the image I am still getting errors similar to the one below on the various network drivers. When I imported them, they all showed up as not signed, and that is referenced in the error below, is that normal for them to show up as unsigned and if so how can I resolve the below error?

Error: Failed to import the following drivers:
• Intel(R) Ethernet Connection I217-LM - 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 inject OSD binaries into mounted WIM file (often happens if unsigned drivers are inserted into x64 boot image)";
• ErrorCode = 2152205056;
• File = "e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\sspbootimagepackage.cpp";
• Line = 4969;
• ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
• Operation = "ExecMethod";
• ParameterInfo = "SMS_BootImagePackage.PackageID=\P0100093\";
• ProviderName = "WinMgmt";
• StatusCode = 2147749889;
};

Thanks, Chris Skeen

_{Tuesday, June 7, 2016 2:23 PM}

Dear Sir,

    You'd better remove all the previous drivers from your boot image or create a new boot image first, then try to import these drivers again.

Best regards,

Jimmy  

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Tuesday, June 28, 2016 8:20 PM}

Thank you for your response Jimmy, I had already tried that as well with no luck.

Thanks, Chris Skeen