Smells like hardware to me. We had similar issues with the 'E' series(M58e, M70e, M71e, etc) Lenovo models and the Marvel Yukon driver. Lenovo released a new driver on July 15th that fixed it but we had dealt with the issues for over 6 months.
Daniel Ratliff From: [email protected] [mailto:[email protected]] On Behalf Of Peter Johansson Sent: Thursday, January 09, 2014 8:17 AM To: [email protected] Subject: [MDT-OSD] Problem with NIC on HP EliteOne 800. Hi, I have a problem with a new model (HP EliteOne 800 AIO). The nic works in WinPE but it doesn't work after the image is applied. In WinPE I can ping the siteserver and other machines on the network but as soon the image is applied and the machine is rebooted to the applied OS (windows 7 x64) and Task Sequence is started again the nic doesn't work. I get an IP-address from dhcp but I can't connect or ping anything on the network. When I do ipconfig /release and ipconfig /renew the nic works until next reboot then I have to do a new ipconfig release and renew. In the TS I've put continue on error on every step and when the TS is finished and I log on to the computer the network still doesn't work and everything is ok in device manager. The nic is an Intel i217-LM and we have that nic in another model (Z230) and that machine works without any problem. The difference between the machines is the hardware id for the nic. We are using SCCM 2012 CU1 and MDT 2012 Update 1. The things I tried: 4 different versions of the driver Created a driver package with only the nic driver in it. 4 different images with different patches 2 years back. Manually installed Windows 7 (will install Windows 8.1 manually tonight to see if that works) Regards //Peter 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.
