>From my quick search of the interwebs, I can see that this card is really a Broadcom card:
http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdHome/ ?sp4ts.oid=3660137 <http://h20566.www2.hp.com/portal/site/hpsc/template.PAGE/public/psi/swdHome /?sp4ts.oid=3660137&spf_p.tpst=swdMain&spf_p.prp_swdMain=wsrp-navigationalSt ate%3DswEnvOID%253D4138%257CswLang%253D%257Caction%253DlistDriver&javax.port let.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignet te.cachetoken> &spf_p.tpst=swdMain&spf_p.prp_swdMain=wsrp-navigationalState%3DswEnvOID%253D 4138%257CswLang%253D%257Caction%253DlistDriver&javax.portlet.begCacheTok=com .vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken Broadcom cards are notorious for being multi-function cards which have problems loading in WinPE due to the limited PNP Driver Support. Get the correct driver from Broadcom, search for "Broadcom RIS" From: [email protected] [mailto:[email protected]] On Behalf Of HELMS, DAVID C Sent: Wednesday, January 15, 2014 7:31 AM To: [email protected] Subject: RE: [MDT-OSD] WinPE NIC drivers I know I can assign a boot image to a task sequence but WinPE isn't loading all the way to where I can view the available task sequences. When booting using PXE, I don't know how to choose which boot image it chooses (x86 or x64). So far it has chosen the x86 image every time. So it looks like I have a x64 driver in the x86 boot image and that must be causing me the issue. This is the error that I am receiving in the smsts.log From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Miller, Todd Sent: Wednesday, January 15, 2014 10:15 AM To: [email protected] <mailto:[email protected]> Subject: RE: [MDT-OSD] WinPE NIC drivers The drivers included in WinPE depend on the version of WinPE you are using. If the WinPE image is based on Windows 8, then you have the same NIC drivers that are built in to Windows 8. Same for WinPE based on Windows 7. The drivers included in the base OS are known as inbox drivers. You might be able to locate a list by searching for Windows 7 inbox drivers. The bitness of the driver has to match the bitness of WinPE. You tell your Task Sequence what WinPE boot disk to use, the OSD process doesn't just choose what WinPE boot disk to use on its own. If you are using WinPE x86 (which I think all here would suggest) then you MUST load x86 drivers for the NIC you are using and for the Mass Storage you need if those drivers are not included in inbox drivers. Drivers for those two pieces of hardware are critical for a successful deployment. If the drivers for those two devices are not included in the WinPE image by default - you must import them into WinPE. It is not enough to just add the drivers to a driver package in SCCM - you must also add those drivers to your WinPE image. You can use WinPE 64bit to deploy OSes, but WinPE 64bit can only deploy 64bit images. WinPE 32bit can deploy both 32 and 64bit oses, which is why nearly everyone uses 32bit WinPE images for deploying OSes. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of HELMS, DAVID C Sent: Wednesday, January 15, 2014 8:57 AM To: [email protected] <mailto:[email protected]> Subject: [MDT-OSD] WinPE NIC drivers I'm having issues where WinPE doesn't load on an older HP server using PXE. I haven't been able to determine if it's a DHCP issue or a NIC driver not in WinPE. I am still working through this, but wanted to ask a few questions. Here is the NIC driver that I need. 1. Is there a list of already supported drivers within WinPE? I'm running Config Manager 2012 R2 boot images ver 6.3.9600.16384. 2. When adding a NIC driver to WinPE, do I need to add the x86 driver to the x86 boot image or does it matter? I have both boot images, but the x86 seems to be the one used and the NIC driver that I downloaded was for Windows 2012 which is a 64 bit driver. I'd appreciate if anyone could clear up this confusion on my end. Thanks, David _____ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. _____
<<image002.png>>
<<image003.png>>
