heres how you can check if your boot wim needs a nic driver or not http://www.niallbrady.com/2011/08/31/missing-nic-driver-in-winpe-boot-image-no-problem/
On Thu, Apr 10, 2014 at 9:59 PM, Daniel Ratliff <[email protected]> wrote: > You may want to re-verify your issues, we are on WinPE 4.0, have 35+ > Lenovo models and have four drivers added to our Boot .wim. One of those 4 > are the VMxnet3 drivers for VM testing. > > > > Keep in mind drivers for one version of WinPE may or may not work for a > later version, the WinPE versions are based on different OS. > > > > WinPE 3.0 - Windows 7 > > WinPE 4.0 - Windows 8 > > WinPE 5.0 - Windows 8.1 > > > > *Daniel Ratliff* > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Hun boy > *Sent:* Thursday, April 10, 2014 3:30 PM > *To:* [email protected] > *Subject:* Re: [mssms] SCCM 2012 R2 Boot WIM DISM - Drivers Failing > -hr:0xc0000135 > > > > Yes I have ADK installed on my system and also on sccm server where I > tried add driver package....... > > > > We have around ~100 models from all vendors ... And I have to build ~100 > models and get the feed back from my felid engineers would take another 30 > days at least as they are lazy... And in between any changes must to be > update the boot WIM Image packed agin going this over the wan would effect > the plan...and sending the USB sticks for slower sites and not would really > painful task .... Hope I will have some solution... > > > > I have given randomly different models but it failed to inject.... Ex > model T440 and M83... Even tried to give only one model ...still no luck > .... I have tried only NIC even same issue... > > > > You mean...Does the latest winPE 5.0 has all the latest models drivers > till at least 2013 models???? > > > > > > > > Sent from iPhone....sorry for typos > > > On 11-Apr-2014, at 12:48 am, "Jason Sandys" <[email protected]> wrote: > > Does your local workstation have the ADK for Win 8.1 installed? > > > > And, what Chris just asked? > > > > And, you shouldn't just inject every NIC and mass-storage driver that you > have. You should only inject them when the boot image doesn't already > include and suitable driver. > > > > J > > > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *[email protected] > *Sent:* Thursday, April 10, 2014 2:11 PM > *To:* [email protected] > *Subject:* Re: [mssms] SCCM 2012 R2 Boot WIM DISM - Drivers Failing > -hr:0xc0000135 > > > > why not use the built-in driver injection for the boot images? > > > > Sent from Windows Mail > > > > *From:* Hun boy <[email protected]> > *Sent:* Thursday, April 10, 2014 2:53 PM > *To:* [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 > > > > > > > > > > The information transmitted is intended only for the person or entity to > which it is addressed > and may contain CONFIDENTIAL material. If you receive this > material/information in error, > please contact the sender and delete or destroy the material/information. > >
