Intel Ethernet Connection I2xx-LM NIC Drivers From K2000 Driver Feed Not Working on new Dell Models (Optiplex 9020-AIO, Latitude E7240, Latitude E7440)
After our image is successfully deployed via the K2000 for the Dell Optiplex 9020-AIO, Latitude E7240, and Latitude E7440, Windows is booted up, however it appears the NIC ethernet jack is deactivated (NIC icon is missing from the taskbar). I would have to physically disconnect the RJ-45 cable and reconnect, and then the icon would appear in the taskbar. If I reboot the system, the NIC would not function again. I would have to repeat the process of replugging the physical RJ-45 cable into the PC. It appears to do something with the new NIC cards that Dell is using: the Intel Ethernet Connection I2xx-LM (i.e. I217-LM, I218-LM, etc.). The drivers from the K2000 Driver Feed are all dated approximately 2/26/2013 for all respective models tested.
Has anyone encountered the same issue, and if so, how did you resolve it?
Some More Tidbits:
I was able to uninstall the driver and install the 7/12/13 drivers which were extracted from a factory image of one of the workstations using Double Driver. This would appear to fix the problem If I were to perform this after the image is deployed. However, if I replace them into the appropriate folders for the \\kbox\drivers_postinstall\ (For example, for the Optiplex 9020-AIO, I removed \\pamu1pua\drivers_postinstall\dell\windows_7_x86\9020-aio\network\72fnc_a00-00 and added the 7/12/13 drivers), the same issue would occur if I tried to reimage the machine again. I would like to fix the root of the problem because I do not want to have to deploy an image, uninstall NIC drivers, reinstall NIC drivers, manually perform postinstall tasks. It makes a simple automated process, now very manual and tedious.
We do have Dell Optiplex 760, 780, 990, 7010 and Latitude models which have all been deployed with the same image successfully, and all post install tasks completing as well.
Answers (2)
If this is a sysprep'd image you may want to use this method of staging the drivers instead of the drivers feed. When a box come out of sysprep it uses this structure to look for drivers in and has always worked for me on all models.
http://www.itninja.com/blog/view/creating-a-windows-7-sysprep-image-without-having-to-install-any-drivers-at-post-install-tasks
Comments:
-
We do have a sysprep'ed image of Windows 7 Enterprise.
It sounds like a possible solution but I would like to try and figure out the root cause of the NIC driver problem. I'd prefer to utilize the K2000's methodology of DISM'ing the drivers from the KBOX's Driver Feed. We would like to use the K2000 as it was designed for.
When speaking with a Dell technician, he mentioned that the manufacturer had used some sort of network syntax/protocol/code that is not the standard. Such commands as mounting the KBOX during the KBE loadup also had issues. We had to copy custom drivers to the \\kbox\drivers\kbe_windows_x86\ folder in order for the KBE to load and to be able to mount the KBOX for the image deployment process. I just thought to add that piece of information, if anyone may be able to comment on if and how they deviated from the norm. - Nu-Nu 10 years ago
Have you tried installing the Kernel Mode Driver Framework 1.11? I was having major driver issues on some newer Dells (7440 and 6540) and they would not image properly until I added this driver. This only applies to Windows 7, I guess it's built into 8.
http://support.microsoft.com/kb/2685811
http://en.community.dell.com/techcenter/b/techcenter/archive/2013/10/07/kernel-mode-driver-framework-1-11-update-what-it-is-and-why-you-need-it.aspx
Comments:
-
Rebuilt a whole new image from scratch, installed the Kernel-Mode Driver Framework v1.11 (KB2685811) as well as the User-Mode Driver Framework v1.11 (KB2685813), sysprepp'ed, deployed the image but still no luck unfortunately. I was really hoping this KB package would fix the issue.
Thanks anyhow for the suggestion! - Nu-Nu 10 years ago-
Have you tried renaming the 7/12/13 version to a different folder name and leave it in the Network folder? Name is so it gets processed after the 2/13 driver. It should install the 2/13 driver then the 7/13 one I believe. - SDNBTP 10 years ago
-
To factor out the possibility of the KBOX DISM'ing (installing) the older drivers, I actually deleted the Feb. 2013 drivers from \kbox\drivers_postinstall\, and then copied the new July 2013 drivers into it. After booting into the O/S, I did check Device Manager and confirmed the July 2013 drivers were installed.
I did not actually try leaving BOTH NIC drivers in the KBOX postinstall folder. - Nu-Nu 10 years ago -
You said you also had WinPE driver issues... What version of WinPE drivers are you using? If you are on 3.0 you can try 4.0 or the new 5.0 driver package and that may help with that. http://www.kace.com/support/resources/kb/solutiondetail?sol=SOL111717
Maybe check if your BIOS is up to date as well. Does 64 bit windows 7 exhibit the same behavior? What about the driver directly from Intel and not from Dell? Not sure what else you could try unfortunately. - SDNBTP 10 years ago -
It appears I am on version A08, which I believe is WinPE 3.0. We originally had a System 1232 issue, and I was told that by the Dell tech that these new Dell models contain a new Intel chipset. We did copy the Intel drivers (which were extract via Double Driver and drivers confirmed to be manufactured by Intel) into the \\kbox\drivers\kbe_windows_x86 folder, and recreated the KBE.
These drivers were extracted from a working Dell Optiplex 9020-AIO factory image that was pulled out of the shipping box and booted up.
I can try WinPE 4.0 and WinPE 5.0, but would that help when I am trying to deploy Windows 7? I see the article mentioning those two versions are for Windows 8 and Windows 8.1 respectively.
I'm all out of ideas and am curious if anyone else has these very specific models and had any issues deploying a Windows O/S with the default drivers from the Driver Feed? - Nu-Nu 10 years ago -
Yes A08 is WinPE 3.0. Win 7 works with 4.0 and 5.0, although I'm not sure if you will see benefits. But it will help for future models, you won't need to add the drivers. Here's comparison: http://technet.microsoft.com/en-us/library/dn293271.aspx
My last suggestion would be to try the newest driver directly from Intel, looks like a new one just came out this month.
I did have issues with E5430 non v-pro model in K2 versions 3.4 and 3.5, the feed would not find any drivers even though the feed was enabled and driver_feed_tool.vbs was showing them in the right folder. I contacted support and they told me it was bug and to submit a feature request on the user voice forums. Instead I just created a mid level task to inject those drivers via DISM commands. This task completely broke in 3.6 due to the new task engine, but it looks like they finally addressed the issue so I don't need to worry about it anymore. - SDNBTP 10 years ago -
I took your advice and checked out the Intel site and noticed a new package was release on 1/13/2014. I downloaded it and extracted the files, and did a driver search for the Ethernet Controller. It was able to find the Intel Ethernet Connection I217-LM drivers dated 8/29/2013, v12.10.30.0 in there and install successfully. I replaced these drivers in my \\kbox\drivers_postinstall\dell\windows_7_x86\9020-aio\network and redeployed the image and it appears to work!!!! I will run these drivers for a couple days early next week to see that the NIC icon doesn't disappear again. Thanks for that last bit of advice as it seems to solve the problem. Even the Dell KACE L3 tech representatives didn't know and were at a loss of words.
NOTE: It appears that both NIC drivers dated Jan. 2013 and July 2013 DO NOT WORK. You will need the 8/29/2013 drivers!!!
For those that run into the same scenario, this is what you want to do:
1) If working from a factory image or newly deployed image, uninstall any NIC drivers for the your Intel Ethernet Connection I217-LM (make sure to check the box that says 'Delete the driver software for this device'.)
2) Download the drivers from the Intel site (https://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Ethernet+Components&ProductLine=Ethernet+Controllers&ProductProduct=Intel%C2%AE+Ethernet+Connection+I217-LM). I would recommend either clicking on the link "Network Adapter Driver for Windows 7" or "Intel® Ethernet Connections CD" and extract to a USB.
3) Copy those drivers to a USB and plug into the problematic workstation.
4) Go to Device Manager and search the USB device and all subfolders for the Ethernet Controller. It will find the Intel Ethernet Connection I217-LM drivers dated 8/29/2013, v12.10.30.0.
5) Open Double Driver to backup all non-Intel drivers from that system.
6) You then want to copy the folder \\net\Intel(R) Ethernet Connection I217-LM, and paste that into \\kbox\drivers_postinstall\dell\windows_7_x86\9020-aio\network
7) Reboot the malfunctioning machine into the Dell KBE and deploy your image. When all is said and done, the NIC icon will be there, NIC drivers installed. I've been running for an hour and no problems yet!!!
I believe the same exact scenario would occur for all the new Dell models such as the Latitude E7240 and Latitude E7440. Good luck to all!!! - Nu-Nu 10 years ago -
Awesome, glad you finally found something that worked. - SDNBTP 10 years ago
One other thing I noticed is that the OP says the date of their drivers is from 2013. I checked my feed and my drivers (At least for 7240) are 2/17/14 - JordanNolan 9 years ago