Share via

Nic's are sometimes identified as "e1dexpress" or "e1dnexpress" instead of something like "Intel (R) Ethernet Connection..." - Why?

Anonymous
2025-06-06T15:51:31+00:00

I'm the new IT tech at a cancer center and find that a number of the Nic's in my CI (configuration Item) report of host name and all NIC's are listed as "e1dexpress", with a few as "e1ednexpress". This is sometimes seen on micro desktops mounted on mobile carts. The majority are set in place at nurses stations or offices. A very few are laptops that are docked and undocked.

I'm curious about why I see this. I'd like to know so I can better understand the Nics and what this means when I look at my reports.

Windows for home | Windows 11 | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

  1. Anonymous
    2025-06-06T18:33:42+00:00

    I'm glad my explanation helped.

    Since your reports come from ServiceNow with SCCM Discovery, make sure that SCCM's hardware inventory is set up to collect the right WMI properties. This will help you get the friendly NIC names (like "Intel(R) Ethernet Connection") instead of the driver names (like "e1dexpress").

    By default, SCCM sometimes gathers information about the driver instead of the NIC's friendly name.

    Things you can do:

    • Make sure that the Win32_NetworkAdapter class is included in your SCCM hardware inventory settings by checking or changing the Name or Description property. The friendly NIC name is usually in this.
    • Make sure that those helpful fields from SCCM data are pulled in by ServiceNow's Discovery or CMDB mappings.
    • If you can, use Get-NetAdapter | PowerShell to run a test query on a sample machine. To make sure the friendly names are available on the endpoint, select Name, InterfaceDescription.

    That's all for now.

    Appreciate your time. Have a nice day!

    Thanks,

    Pau

    1 person found this answer helpful.
    0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-06-06T17:31:22+00:00

    Hi Mike,

    Good day! I'm Pau, and I'm an Independent Advisor. Thanks for asking about the NIC names showing up in your Configuration Item reports as "e1dexpress" or "e1dnexpress" instead of the expected "Intel (R) Ethernet Connection..."

    If the system's NIC driver uses Intel's e1dexpress or e1dnexpress driver packages, which are usually Intel Ethernet drivers, this naming pattern will show up. Instead of the descriptive hardware name you might expect, the system gives you the name of the driver.

    How to fix this problem and why it happens:

    1. Names for these drivers (e1dexpress, e1dnexpress) refer to Intel's network interface card drivers, which are common in newer or built-in Intel NICs, especially on small or portable devices like micro desktops on carts or laptops with docking stations.
    2. While Windows may recognize the device with a friendly name, it may not be fully recognized because:
    • Installation of generic or specific Intel drivers without the manufacturer's unique device description.
    • Systems that are using a minimal or customized OS image that doesn't have full device name metadata downloaded.
    • Generic or older tools for reporting not reading the device description but the driver name.
    1. Ensure that the most recent versions of the Intel Network and chipset drivers are installed in order to see the friendly NIC name in Windows:

    Reinstall drivers:

    • Launch Device Manager.
    • Expand network adapters
    • Click "Update driver" on the NIC and then "Automatically search for updated driver software."
    1. It's not a problem if the device name still shows up as the driver name. The NIC is working normally; the issue is with how the system or your reporting tool is recognizing the device.
    2. For improved clarity in your Configuration Item reports:
    • It's important that the software used for management or inventory gets the NIC's friendly name (like "Intel(R) Ethernet Connection") instead of the driver name using WMI or PowerShell queries.
    • Access the friendly NIC descriptions with PowerShell commands like Get-NetAdapter | Select-Object Name, InterfaceDescription.

    I'm happy to help you modify your reporting methods or keep your drivers up to date.

    Tell me if you want me to walk you through the process of updating drivers or suggest settings for the reporting tool.

    Sincerely,

    Pau

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2025-06-06T18:26:39+00:00

    Thanks! This answered my questions. (My reports come from ServiceNow; I'll try to find a way to get the friendly name. It uses SCCM as the Discovery Source.)

    0 comments