'Failed to insert OSD binaries into the WIM file' when injecting network drivers into Boot Image SCCM 2012




Issue: Today when I was trying to PXE boot Lenovo T440s for the first time, image started failing at “Task Sequence Window comes” (TS window wasn’t appearing).
Tried This…After this I assumed that can be a problem with the LAN drivers, immediately I started injecting boot image with Lenovo’s Latest LAN drivers BUT it failed with following below error.
Error Message: “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 = “e:\nts_sms_fre\sms\siteserver\sdk_provider\smsprov\sspbootimagepackage.cpp”;
Line = 4262;
ObjectInfo = “CSspBootImagePackage: reRefreshPkgSrcHook”;
Operation = “ExecMethod”;
ParameterInfo = “SMS_BootImagePackage.PackageID=”S0100002″”;
ProviderName = “WinMgmt”;
StatusCode = 2147749889;
};
Resolution: Tried following steps:

  1.  We created a new boot Image named “New Boot Image” Under Operating System>Boot Images><Site Code>.
  2.  Downloaded latest drivers from Lenovo websites http://support.lenovo.com/de_DE/downloads/detail.page?DocID=DS03881
  3.  Create a new driver package using above downloaded drivers including network drivers.
  4.  Injected network drivers from above package and it imported successfully this time.
  5. So we removed Old Boot Image (“Boot Image(x64)”) from <Site Code>Distribution Point so that we could enable new boot image at PXE.

So far it’s working fine for us.

You can look for other troubleshooting steps as well like:

Check if there is enough space on SQL HDDs or LUNs

Check also if you are trying to insert only network drivers. Remove all other Drivers from the "insert list".

Comments

Post a Comment

Popular posts from this blog

Enterprise CA option is greyed out / unavailable

Many times, when installing Active Directory Certificate Services they cannot choose to install Enterprise Certification Authority, because it’s unavailable as in following picture: Well, you need to fulfill basic requirements: Server machine has to be a member server (domain joined). You can run an Enterprise CA on the Standard, Enterprise, or Data Center Windows Edition. The difference is the number of ADCS features and components that can be enabled. To get full functionality, you need to run on Enterprise or Data Center Windows Server 2008 /12/R2/ Editions.  In order to install an Enterprise CA, you must be a member of either Enterprise Admins or Domain Admins in the forest root domain (either directly or through a group nesting). If issue still persists, there is probably a problem with getting correct credentials of your account. There are many thing that can cause it (network blockage, domain settings, server configuration, and other issues). In al...
Read more

Rearm the Office 2013 installation

Image
There is a 25-day grace period from the time of installation of Key Management Service (KMS) clients before notifications to activate are displayed to the user. If you want to deploy an image, you must rearm your Office 2013 installation before you capture the image. If you do not rearm, users see notification dialog boxes at the time that the image is deployed, instead of 25 days after deployment. The 25-day grace period gives ample time for a KMS host to be found and activation to succeed. If activation is successful, users do not see notifications to activate. Rearm the Office installation Rearming does the following important tasks: Resets the grace timer to 30 days. Freezes the grace timer until either an Office application is run, or the ospp.vbs script is run. Resets the client computer ID (CMID). This is important because the KMS host uses the CMID to determine the num...
Read more

MP has rejected registration request due to failure in client certificate

Image
Issue:- We have System Center Configuration Manager 2012 R2 deployed on Windows Server 2008R2 host. Recently we have moved our Certification Authority to Windows Server 2012 , renewed Root CA Certificate and intermediate Certificates also migrated Hashing algorithm from 'sha1' to 'sha2'  . New Root CA and intermediate CA also present on client machines and on SCCM. However, i have discovered these errors on MP: MP has rejected registration request due to failure in client certificate (Subject Name: ) chain validation. If this is a valid client ,  Even though Newly imaged machines are getting SCCM client installed but won't see all the client cycle under 'Actions tab' and also  'client certificate shows "None".  The operating system reported error 2148204809: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.  Solution:- Register  new Certificate of Root CA    under SCCM20...
Read more