The ‘.1’ at the end means “Workstation only” for INF Manufacturer sections:
https://msdn.microsoft.com/en-us/library/windows/hardware/ff547454(v=vs.85).aspx NTx86.6.3 vs ntx86.6.3.1 ? Technically there is no difference, they mean the same thing. There are NO Windows Server 2012 R2 x86 machines. NTamd64.6.3 vs NTamd64.6.3.1 ? That is slightly more interesting. Intel uses the workstation modifier to cripple some consumer networking chipsets from running on Server OS’es. My rant on the subject: https://keithga.wordpress.com/2014/11/08/running-windows-server-on-consumer-intel-chipsets-z87/ AS for the problem at hand… If your driver works, but it is not getting loaded correctly in WinPE, check the wpeinit.log file, and see what it says when trying to load the networking driver. From: [email protected] [mailto:[email protected]] On Behalf Of Miller, Todd Sent: Thursday, February 19, 2015 11:12 AM To: [email protected] Subject: RE: [MDT-OSD] NIC not loading in WinPE 5.1 And, so what is the difference between NTx86.6.3 and NTx86.6.3.1? And what is Windows Blue? I tried modifying the driver’s sections to say 6.3 instead of 6.2, but that didn’t trick WinPE 5.0 into loading them. From: <mailto:[email protected]> [email protected] [ <mailto:[email protected]> mailto:[email protected]] On Behalf Of Aaron Czechowski Sent: Thursday, February 19, 2015 10:35 AM To: <mailto:[email protected]> [email protected] Subject: RE: [MDT-OSD] NIC not loading in WinPE 5.1 Daniel, you’re close but not quite right. :) WinPE 3 = Win7 = 6.1 WinPE 4 = Win8 = 6.2 WinPE 5 = Win8.1 = 6.3.9600.16384 WinPE 5.1 = Win8.1 Update (Spring 2014) = 6.3.9600.(I don’t remember, something greater than 16384) (I won’t share my personal opinions on this topic…perhaps we can discuss over drinks at Ignite…) As for “conflicting advice” on whether to update, here’s mine: http://blogs.technet.com/b/msdeployment/archive/2014/04/03/understanding-the-adk-for-windows-8-1-update-and-mdt-2013.aspx (with the associated similar post for ConfigMgr <http://blogs.technet.com/b/configmgrteam/archive/2014/04/03/understanding-the-adk-for-windows-8-1-update-and-configmgr-osd.aspx> ). If someone else is telling you to use WinPE 5.1, I’d be very interested to hear their reasons why. Sorry I can’t help with the driver issue, but wanted to clear things up with this. Aaron From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Thursday, February 19, 2015 6:25 AM To: [email protected] <mailto:[email protected]> Subject: RE: [MDT-OSD] NIC not loading in WinPE 5.1 WinPE 5.0 = 6.2 = Win8 WinPE 5.1 = 6.3 = Win8.1 The only catch is there is an update to WinPE 5.1, that keeps at it 5.1 and it’s called the Win8.1 Update. I found little to nothing online about the 980 and WinPE 5.1. I would say the label on the site may not match as a lot of vendors assume if it works for 8.0 it works for 8.1. I know that is not always the case with Lenovo and it sounds like it with Dell too. Daniel Ratliff From: <mailto:[email protected]> [email protected] [ <mailto:[email protected]> mailto:[email protected]] On Behalf Of Miller, Todd Sent: Thursday, February 19, 2015 9:15 AM To: <mailto:[email protected]> [email protected] Subject: RE: [MDT-OSD] NIC not loading in WinPE 5.1 I think I was mistaken when I said WinPE 5.1. I am pretty sure I am using WinPE 5.0. The version numbers are pretty confusing with 8.0 and 8.1 with are really 6.2 and 6.2.1 or 6.3 or 6.3.1 and then with WinPE being 5.0 or 5.1… Anyway, the OS version of the boot image is reported as 6.3.9600.16384 (How would I tell the difference between WinPE 5.0 and 5.1? and I have heard conflicting advice on whether to update WinPE 5.0 to 5.1 or not) Intel doesn’t list 8.1 drivers for the 82578DM NIC, but Windows Update Catalog from Microsoft does. That driver I downloaded from Microsoft looks like this… So No 6.3 or 6.3.1 section. But Windows Update Catalog says this driver is for 8 and 8.1. Is this not a valid driver for Win PE 5.0? I can force it to load after booting into WinPE and it works, but it wont load automatically. After forcing it to load I DO get a NIC listed correctly and an IP address as shown in ipconfig. This is on a Dell Optiplex 980. I can verify that this driver ends up being baked into the WIM because it is present in the X:\Windows\INF folder in the RAM/Boot disk and I can load it by force using the drvload command. [Manufacturer] %Intel% = Intel, NTx86.6.2.1 [ControlFlags] ExcludeFromSelect = \ PCI\VEN_8086&DEV_10DE&SUBSYS_10DE8086,\ PCI\VEN_8086&DEV_10DF&SUBSYS_10DF8086 [Intel] ;=============================================================================== ; WINDOWS 8 PLATFORMS ;=============================================================================== [Intel.NTx86.6.2.1] ; DisplayName Section DeviceID ; ----------- ------- -------- %E10DENC.DeviceDesc% = E10DE, PCI\VEN_8086&DEV_10DE %E10DENC.DeviceDesc% = E10DE, PCI\VEN_8086&DEV_10DE&SUBSYS_10DE8086 %E10DFNC.DeviceDesc% From: <mailto:[email protected]> [email protected] [ <mailto:[email protected]> mailto:[email protected]] On Behalf Of Keith Garner (Hotmail) Sent: Tuesday, February 17, 2015 7:30 PM To: <mailto:[email protected]> [email protected] Subject: RE: [MDT-OSD] NIC not loading in WinPE 5.1 Here are my debugging steps from my technet FAQ Posting: https://social.technet.microsoft.com/Forums/en-US/3e083173-f5db-48e9-b744-f71b9ca6541c/how-to-debug-missing-drivers-in-mdt?forum=mdt Installing Network Drivers in WinPE * Step 6 - Try the network connection again (See above * Step 7 - Verify Connectivity from within WinPE Verifying network connectivity will be a bit more difficult in WinPE, since we have a limited User Interface, so all investigation must be done in the debugging mode (Press F8) cmd.exe ○ Try connecting to the Deployment Share: c:\> net use * \\MDT\DeploymentShare$ <file:///\\MDT\DeploymentShare$> /u:UserDomain\UserName * ○ Try pinging the Deployment Server: c:\> Ping.exe MDT.Corp.contoso.com ○ Verify that you have an IP address ( ipconfig /all ) If you have an AutoConfiguration address - Driver OK - WinPE can't reach the DHCP server. If you have "Media Disconnected" - Driver OK - Physical adapter not plugged to network. If no devices are listed - Driver bad - Driver not installed. ○ Check the x:\windows\system32\WpeInit.log - This log will show the network driver (if found) being installed. From: [email protected] <mailto:[email protected]> [mailto:[email protected]] On Behalf Of Chris Catlett Sent: Tuesday, February 17, 2015 4:10 PM To: [email protected] <mailto:[email protected]> Subject: Re: [MDT-OSD] NIC not loading in WinPE 5.1 which version number of the driver are you injecting? To be sure, you are loading the windows 8.1 driver into the boot image, that is what pe 5.1 requires. _____ On a Dell Optiplex 980, when booting from a USB stick with a WinPE 5.1 image created by SCCM 2012/MDT 2013 I am not getting an IP address. I am pretty sure I have the correct driver loaded in the WIM, but for some reason it is not loading correctly and then I do not get an IP address. I am able to find the correct driver in the X:\Windows\INF folder in the Boot Wim when booted from the stick as “OEM28.inf” – so the driver is injected properly as far as I can tell. I am able to load the driver using “drvload oem28.inf” from a command prompt. When I load the driver in this way and do “wpeutil initializeNetwork” then I get an IP address. So I think I have the right driver in there, but it is just not being detected correctly. Does anyone have any tips? I am pretty sure the ven/dev code for the Ethernet device in the Optiplex 980 is 8086/10EF- and that code is listed as supported in the driver that gets loaded by adding the drivers to the WIM (as evidenced by OEM28.inf _____ 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. _____ _____ 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. _____ 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. _____ 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. _____
