Search This Blog

Friday, January 11, 2013

Failed to insert OSD binaries into the WIM file

I have seen this problem when trying to create a MDT task sequence or MDT boot image in System Center Configuration Manager 2012 SP1.

Started processing.

Creating boot image.

Copying WIM file.

Mounting WIM file.

WIM file mounted.

Setting Windows PE system root.

Set Windows PE system root.

Set Windows PE scratch space.

Adding standard components.

Adding component: winpe-mdac

Adding extra content from: C:\Users\Lars\AppData\Local\Temp\2\crv0zctm.r3q

Unmounting WIM.

Copying WIM to the package source directory.

Creating boot image package.

Error while importing Microsoft Deployment Toolkit Task Sequence.Failed to insert OSD binaries into the WIM file

Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException: The SMS Provider reported an error. ---> System.Management.ManagementException: Generic failure

at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)

at System.Management.ManagementObject.Put(PutOptions options)

at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)

--- End of inner exception stack trace ---

at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)

at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put()

at Microsoft.BDD.Wizards.SCCM_ImportTaskSequenceTask.DoWork(SmsPageData smspageData, Dictionary`2 data)


The solution for me was to disable Mcafee Access protection, then everything worked as expected – sigh.


Tuesday, January 8, 2013

System Center Configuration Manager 2012 Cumulative Update 2 (CU2)

Just as the CU1 update, the easiest way to see if CU2 is installed is to check the control panel or directly on an updated DLL. (CU1 post)

Updated DLL version will be 5.00.7711.301