Precision Fixed Workstations

Last reply by 09-25-2021 Unsolved
Start a Discussion
2 Bronze
2 Bronze
6284

Precision 3630 MDT WinPE NIC card problem

Hello,

We received a batch of the new Precision 3630 workstation and were curious if anyone else is having issues with the integrated NIC I219-LM drivers failing load while starting Microsoft Deployment Toolkit (MDT) WinPE environment.

At the this time, none of our other Dell workstations (T3620, Opti 5040, 5050, etc) and laptops (Latitude E64xx, E65xx, etc) are exhibiting this behavior.

We are using MDT Build 8443 and have imported the latest WinPE 10 cab drivers found here (link) and updated the deployment share via "completely regenerate the boot images" and replaced the newly created wim on WDS.

The 3630 will PXE boot, receive an IP address from DHCP, and load the WinPE wim from WDS. However the result of the failure is that MDT cannot reach the deployment share as it does not load the integrated NIC card driver thus has no network access to mount the share.

We have also tried to inject factory Intel drivers, Dell 3630 specific drivers found (here), drivers extracted from the OOBE 3630 itself and some older variants of the Intel driver to no avail.

One red flag item we've noticed from the X:\Windows\INF\setupapi.dev.log is the 3630 does not appear to present the plug-n-play enumeration of the integrated NIC to the WinPE environment.

For example, here's what a working OptiPlex 5040 setupapi.dev.log looks like (note the bold blue line):

[Device Install Log]
OS Version = 10.0.14393
Service Pack = 0.0
Suite = 0x0100
ProductType = 1
Architecture = amd64

[BeginLog]

[Boot Session: 2018/11/19 14:35:57.488]

>>> [Device Install (DiInstallDevice) - PCI\VEN_8086&DEV_15B8&SUBSYS_06BA1028&REV_31\3&11583659&0&FE]
>>> Section start 2018/11/19 14:36:04.058
cmd: wpeinit.exe
ndv: Flags: 0x00000002
dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
sto: {Setup Import Driver Package: X:\WINDOWS\INF\oem47.inf} 14:36:04.058
sto: Driver package already imported as 'oem47.inf'.
sto: {Setup Import Driver Package - exit (0x00000000)} 14:36:04.074
dvi: Searching for hardware ID(s):
dvi: pci\ven_8086&dev_15b8&subsys_06ba1028&rev_31
dvi: pci\ven_8086&dev_15b8&subsys_06ba1028
dvi: pci\ven_8086&dev_15b8&cc_020000
dvi: pci\ven_8086&dev_15b8&cc_0200
dvi: Searching for compatible ID(s):
dvi: pci\ven_8086&dev_15b8&rev_31
dvi: pci\ven_8086&dev_15b8
dvi: pci\ven_8086&cc_020000
dvi: pci\ven_8086&cc_0200
dvi: pci\ven_8086
dvi: pci\cc_020000
dvi: pci\cc_0200
dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
dvi: {Plug and Play Service: Device Install for PCI\VEN_8086&DEV_15B8&SUBSYS_06BA1028&REV_31\3&11583659&0&FE}
ndv: Driver INF Path: X:\WINDOWS\INF\oem47.inf
ndv: Driver Node Name: e1d65x64.inf:5f63e53495efc9df:E15B8.10.0.1:12.17.8.9:pci\ven_8086&dev_15b8&subsys_06ba1028
ndv: Driver Store Path: X:\WINDOWS\System32\DriverStore\FileRepository\e1d65x64.inf_amd64_89a7b3d5b7825ea1\e1d65x64.inf

Here is what the 3630's setupapi.dev.log looks like (full log). Notice the integrated Intel NIC never presents itself to the WinPE environment. The battery does strangely..haha.

[Device Install Log]
OS Version = 10.0.14393
Service Pack = 0.0
Suite = 0x0100
ProductType = 1
Architecture = amd64

[BeginLog]

[Boot Session: 2018/11/14 15:11:04.486]

>>> [Device Install (DiInstallDevice) - ROOT\KDNIC\0000]
>>> Section start 2018/11/14 15:11:10.030
cmd: wpeinit.exe
ndv: Flags: 0x00000002
dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
sto: {Setup Import Driver Package: X:\WINDOWS\INF\kdnic.inf} 15:11:10.030
sto: Driver package already imported as 'kdnic.inf'.
sto: {Setup Import Driver Package - exit (0x00000000)} 15:11:10.030
dvi: Searching for hardware ID(s):
dvi: root\kdnic
dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
dvi: {Plug and Play Service: Device Install for ROOT\KDNIC\0000}
ndv: Driver INF Path: X:\WINDOWS\INF\kdnic.inf
ndv: Driver Node Name: kdnic.inf:db04a16c725e6ffa:KdNic.ndi:10.0.14393.0:root\kdnic
ndv: Driver Store Path: X:\WINDOWS\System32\DriverStore\FileRepository\kdnic.inf_amd64_e1703005cc16edf6\kdnic.inf
dvi: Searching for hardware ID(s):
dvi: root\kdnic
dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
ndv: {Core Device Install} 15:11:10.042
ndv: {Install Device - ROOT\KDNIC\0000} 15:11:10.042
ndv: Parent device: HTREE\ROOT\0
ndv: {Configure Device - ROOT\KDNIC\0000} 15:11:10.042
ndv: Parent device: HTREE\ROOT\0
sto: {Configure Driver Package: X:\WINDOWS\System32\DriverStore\FileRepository\kdnic.inf_amd64_e1703005cc16edf6\kdnic.inf}
sto: Source Filter = root\kdnic
inf: Class GUID = {4d36e972-e325-11ce-bfc1-08002be10318}
inf: Class Options = Configurable
dvi: {Configure Device: ROOT\KDNIC\0000}
dvi: Device Instance Id = ROOT\KDNIC\0000
dvi: Updating existing device instance.
dvi: {Configure Device: exit(0x00000000)}
inf: {Configure Driver: Microsoft Kernel Debug Network Adapter}
inf: Section Name = KdNic.ndi
inf: {Add Service: kdnic}
inf: Start Type = 3
inf: Service Type = 1
inf: Error Control = 1
inf: Image Path = \SystemRoot\System32\drivers\kdnic.sys
inf: Display Name = Microsoft Kernel Debug Network Miniport (NDIS 6.20)
inf: Group = NDIS
inf: Created new service 'kdnic'.
inf: {Add Service: exit(0x00000000)}
inf: Hardware Id = root\kdnic
inf: {Configure Driver Configuration: KdNic.ndi}
inf: Service Name = kdnic
inf: Config Flags = 0x00000000
inf: {Configure Driver Configuration: exit(0x00000000)}
inf: {Configure Driver: exit(0x00000000)}
flq: Hardlinking 'X:\WINDOWS\System32\DriverStore\FileRepository\kdnic.inf_amd64_e1703005cc16edf6\kdnic.sys' to 'X:\WINDOWS\System32\drivers\kdnic.sys'.
! flq: HardLink: 'X:\WINDOWS\System32\DriverStore\FileRepository\kdnic.inf_amd64_e1703005cc16edf6\kdnic.sys' to 'X:\WINDOWS\System32\drivers\kdnic.sys' FAILED!
! flq: Error 1: Incorrect function.
dvi: Existing files modified, may need to restart related services.
sto: {Configure Driver Package: exit(0x00000bc3)}
ndv: Restart required for any devices using this driver.
dvi: Install Device: Configuring device (kdnic.inf:root\kdnic,KdNic.ndi). 15:11:10.241
dvi: Install Device: Configuring device completed. 15:11:10.241
dvi: {Restarting Devices} 15:11:10.241
dvi: Restart: ROOT\KDNIC\0000
dvi: {Restarting Devices exit} 15:11:10.241
ndv: {Configure Device - exit(0x00000000)} 15:11:10.241
ndv: {Install Device - exit(0x00000000)} 15:11:10.241
ndv: {Core Device Install - exit(0x00000000)} 15:11:10.241
ump: {Plug and Play Service: Device Install exit(00000000)}
<<< Section end 2018/11/14 15:11:10.250
<<< [Exit status: SUCCESS]


>>> [Device Install (DiInstallDriver) - X:\Windows\Inf\Battery.inf]
>>> Section start 2018/11/14 15:11:16.327
cmd: "X:\windows\system32\drvload.exe" X:\Windows\Inf\Battery.inf
ndv: Flags: 0x00000000
ndv: INF path: X:\Windows\Inf\Battery.inf
inf: {SetupCopyOEMInf: X:\Windows\Inf\Battery.inf} 15:11:16.327
inf: Copy style: 0x00000000
inf: Driver Store Path: X:\WINDOWS\System32\DriverStore\FileRepository\battery.inf_amd64_8e3050ad7a27ade1\battery.inf
inf: Published Inf Path: X:\WINDOWS\INF\battery.inf
inf: {SetupCopyOEMInf exit (0x00000000)} 15:11:16.327
<<< Section end 2018/11/14 15:11:16.343
<<< [Exit status: SUCCESS]

 

Since this issue is fairly complex, I'm hoping some other enterprise orgs may have experienced this issue and have a resolution. Possibly some Dell Tier 2/3 engineers are able to test the 3630 on their own MDT/WDS environment and see if they can replicate the issue.

Will open a support ticket soon.

-DMI123

Labels (3)
Replies (8)
Moderator
Moderator
6214

@dmi123,

We have a deployment bench here at my site so I'll ask around and see what I can find.

I will follow-up with you as soon as I know.

Justin C Dell Technical Support | Project Sputnik


Dell Support is also on Twitter! https://twitter.com/DellCaresPRO


Moderator
Moderator
6199

@dmi123,

We're using MDT 8450 and Windows 10 ADK 1803 with no issues on xx30 series Precision. Can you give those a shot?

Justin C Dell Technical Support | Project Sputnik


Dell Support is also on Twitter! https://twitter.com/DellCaresPRO


6161

Is there any word on this working? I have a batch of Precison 3630's. I infuse the Intel L2xx drivers into a 1809 boot.wim and I get cannot obtain DHCP address using WDS.

6061

Hi,

I tried to inject the drivers to x86 and x64 WinPE and cannot make it work either ... in x86 USB does not work either = no keyboard and mouse ... very frustrated ...

Update:
network drivers from Intel work when injected to x64 boot wim 

https://downloadcenter.intel.com/download/22283

5937

Please let me know if someone will solve this problem ... thank you

5236

NOTE: I performed the following steps below on a Windows 10 computer due to the fact I needed the DISM version 10.0.17134.1. The download link for the new ADK is at this link.

 

Download and install the latest Deployment Image Servicing and Management tool kit (Version: 10.0.17134.1). You will need to inject the CAB drivers from Dell into the WinPE boot image, and the Windows Setup boot image for Windows 10. They will error out/fail if you try to add the driver packages to boot image from the Windows Deployment Services Server. The required drivers to boot your I219-LM nic are not installed. Make sure to download both the WinPE, and Win 10 CAB driver files from the Dell website, I'll explain how they are applied later. The boot image would be the boot.wim file from the installation media, or from downloading the installer from Microsoft (example: Win101809.iso). Make sure to install PowerShell ver 3.0, it is required. Follow the directions below.

 

PREP STEPS:

* Create a root folder name 'Mount' on your c:, or d: drives.

* In the Mount folder, create three folders: BootWIM, PEDriver, and OSDriver.

* Copy the boot.wim file from the Windows 10 media to the Mount folder.

* Extract the WinPE driver CAB file from Dell to the PEDriver folder.

* Extract the Win 10 driver CAB file from Dell to the OSDriver folder.

 

DOS Commands:

* Execute the following command without quotes: 'Dism /Get-ImageInfo /ImageFile:d:\mount\boot.wim'. You should have two indexes, WinPE and Windows Setup. We will start with the drivers for the WinPE (Index 1).

* Now we want to extract the WinPE boot portion. Execute the command: Dism /Mount-Image /ImageFile:"d:\mount\boot.wim" /index:1 /MountDir:d:\mount\BootWIM

* Now we want to inject the WinPE drivers into the WinPE boot portion. Execute the command without quotes: 'Dism /Image:d:\mount\BootWIM /Add-Driver /Driver:d:\Mount\PEDriver\ /recurse'. You should receive the message: The Driver package was successfully installed for each driver. You can validate the drivers were installed by executing the command without quotes: 'Dism /Image:d:\Mount\BootWIM /Get-Drivers'.

* Now we want to commit the changes back to the boot.wim file for the WinPE portion. Execute the command: Dism /Unmount-Image /MountDir:d:\mount\bootWIM /Commit

* Now we will proceed with the Win 10 OS drivers. We need to extract the Windows Setup boot portion from the boot.wim file. Execute the command: Dism /Mount-Image /ImageFile:"d:\mount\boot.wim" /index:2 /MountDir:d:\mount\BootWIM

* Now we want to inject the Windows driver into the Windows Setup boot portion. Execute the command without quotes: 'Dism /Image:d:\mount\BootWIM /Add-Driver /Driver:d:\Mount\OSDriver\ /recurse'. You should receive the message: The Driver package was successfully installed for each driver. You can validate the drivers were installed by executing the command without quotes: 'Dism /Image:d:\Mount\BootWIM /Get-Drivers'.

* Now we want to commit the changes back to the boot.wim file for the Windows Setup portion. Execute the command: Dism /Unmount-Image /MountDir:d:\mount\bootWIM /Commit

NOTE: You have successfully injected the Windows OS and Windows PE drivers into the boot.wim file. If you notice the new size of the boot.wim file, it should have grown to be around 500MB from about 350MB.


Windows Deployment Services Server:

* Copy the updated boot.wim file to your WDS Server and add the boot image for Windows 10. You can boot from the boot.wim image on the WDS server. If you have your WDS Server setup correctly, you can either perform a legacy or UEFI boot to proceed with deploying your image onto your computer.

NOTE: With this fix, you no longer need to press the shift and F10 buttons, and load a driver from your USB device during the setup screen (Windows 10) from the WDS Server.

2463

I am having the same problem with Keyboard and Mouse. Did you get that fixed? 

2 Bronze
2 Bronze
1595

Hello dmi123,

Have you fixes the problem? I have the same problem.

Thanks,

Dominique.

Latest Solutions
Top Contributor