why not use the built-in driver injection for the boot images? Sent from Windows Mail
From: Hun boy<mailto:[email protected]> Sent: Thursday, April 10, 2014 2:53 PM To: [email protected]<mailto:[email protected]> Hi All, I have upgraded my SCCM 2012 RTM to SP1(Not installed any Cumulative updates) then to SCCM 2012 R2 Successfully... I did not get any errors. Before Upgrade my SCCM 2012 RTM/SP1 Images are removed from DP Targets. Now my next high priority task is I wanted to integrate my Hardware models NIC & Mass Storage Drivers to my Boot Images, So that my OSD will work without any issues. But am getting errors, when I try to add by DISM command to the Boot Images. I have taken Default boot.wim file from SCCM 2012 R2 and copy pasted to my work location and ran the DISM command... however I am not successful in this for integration. Has anyone have already have solution for this let me know. <<<AV is in Disabled state during DISM.. Still no Luck>>> Attached my DISM.Log file here... Failed to create Dism Image Session in host. - CDISMManager::LoadImageSession(hr:0xc0000135) DISM Manager: PID=3200 A problem ocurred loading the image session. Retrying... - CDISMManager::CreateImageSession(hr:0xc0000135) DISM.EXE: Unable to start the servicing process for the image at 'E:\Boot_WIM\SCCMR2_WIMS\X86\Temp'. HRESULT=C0000135 Thank you In Advance, Hunboy
