Editing a driver

[timbo343]

We have a load of Hp 8000 machines which use the Intel Pro1000 driver. When we deploy an image or even set up one of these machines from scratch, we try to use the latest Intel Pro1000 drivers (the hardware is Intel 82567LM-3) however it seems like Intel forgot to add this hardware to the list of compatible hardware for this driver therefore once the image has been deployed we have to visit each machine and forcefully tell windows 10 to use the Intel 82679LM as the original driver doesn't have the WOL settings but the 82679LM does.

 

So, does anyone know how to add the82567LM-3 (PCI\VEN_8086&DEV_10DE&SUBSYS_3646103C&REV_02\3&21436425&0&C8) hardware to the Intel Pro1000 driver (NDIS65) so that these machines will automatically pickup this driver which is configured in our MDT server rather than having to visit each machine and forcefully make these machines accept this driver.

 

Thanks

[SHimmer45]

could you not use a selection profile in MDT to point at the specific driver for that machine rather than relying on PnP selection?

something i have been looking at to get over some annoying realtek sound driver issues...

[Arthur]

Have you tried the driver from the Windows Update Catalog...

 

https://www.catalog.update.microsoft.com/Search.aspx?q=VEN_8086%26DEV_10DE%26SUBSYS_3646103C

 

If @SHimmer45's suggestion doesn't work, you are going to have to edit the relevant .inf for your Intel NIC, buy a code signing certificate and re-sign the driver files...

 

http://deploymentresearch.com/Research/Post/454/Deploying-Windows-Server-2012-R2-to-Intel-NUC-devices-using-MDT-2013

[SHimmer45]

https://www.catalog.update.microsoft.com/Search.aspx?q=VEN_8086%26DEV_10DE

[timbo343]

could you not use a selection profile in MDT to point at the specific driver for that machine rather than relying on PnP selection?

something i have been looking at to get over some annoying realtek sound driver issues...

 

We do use selection profiles and have the latest intel Pro1000 drivers in there however the hardware keeps picking up the Windows 10 built in driver as the Intel Pro1000 driver doesn't have this specific driver listed. Only forcing the driver via Have Disk in device manager installs the driver and adds the WOL settings.

 

Have you tried the driver from the Windows Update Catalog...

 

https://www.catalog.update.microsoft.com/Search.aspx?q=VEN_8086%26DEV_10DE%26SUBSYS_3646103C

 

If @SHimmer45's suggestion doesn't work, you are going to have to edit the relevant .inf for your Intel NIC, buy a code signing certificate and re-sign the driver files...

 

Deployment Research > Research

 

The driver on the windows catelogue site is an old driver. I'm guessing windows 10 is already using this driver which doesn't have the WOL settings as default. These drivers worked perfectly when on windows 7.

[timbo343]

Looking at the .inf file, i dont even know where to start when editing the driver.

 

 

[ControlFlags]

ExcludeFromSelect = \

PCI\VEN_8086&DEV_1502,\

PCI\VEN_8086&DEV_1503

 

[intel]

 

[intel.NTamd64.10.0.1]

; DisplayName Section DeviceID

; ----------- ------- --------

%E1502NC.DeviceDesc% = E1502.10.0.1, PCI\VEN_8086&DEV_1502

%E1502NC.DeviceDesc% = E1502.10.0.1, PCI\VEN_8086&DEV_1502&SUBSYS_00008086

%E1502NC.DeviceDesc% = E1502.10.0.1, PCI\VEN_8086&DEV_1502&SUBSYS_00011179

%E1502NC.DeviceDesc% = E1502.10.0.1, PCI\VEN_8086&DEV_1502&SUBSYS_00021179

%E1503NC.DeviceDesc% = E1503.10.0.1, PCI\VEN_8086&DEV_1503

%E1503NC.DeviceDesc% = E1503.10.0.1, PCI\VEN_8086&DEV_1503&SUBSYS_00008086

%E1503NC.DeviceDesc% = E1503.10.0.1, PCI\VEN_8086&DEV_1503&SUBSYS_00011179

%E1503NC.DeviceDesc% = E1503.10.0.1, PCI\VEN_8086&DEV_1503&SUBSYS_00021179

 

[intel.NTamd64.10.0]

; DisplayName Section DeviceID

; ----------- ------- --------

%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502

%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_00008086

%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_00011179

%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_00021179

 

;===============================================================================

 

; WINDOWS 10 for 64-bit EXTENDED PLATFORMS

 

Im thinking the driver id goes in there somewhere.

[SHimmer45]

maybe remove the built in driver from the image so it has no choice but to use the driver you are selecting?

[3s-gtech]

Without the .inf file containing the HID it won't ever know to use the newer driver, even if the old one has gone. I think Arthur's post is the only possible route there.