Regarding the method for recognizing NICs in Windows Server 2022 Standard

Question

Regarding the method for recognizing NICs in Windows Server 2022 Standard

佐々木駿 20

We are reviewing the operations required after the vendor’s onsite maintenance in the event of a server hardware failure.

Upon inquiry to the hardware vendor (HPE), we were informed that when a NIC is replaced, it is necessary to reconfigure the new NIC.

We would like to confirm the procedure for reconfiguring a NIC after replacement. However, because the NIC may be onboard and we are not able to actually replace it and verify the behavior, we would appreciate your guidance on the following points:

After a NIC is replaced, what happens to the pre-failure (existing) NIC configuration/state? (For example: Does the existing NIC remain as a lower-numbered device and the new NIC is added as a higher-numbered device? Is the existing NIC overwritten by the new NIC and its configuration inherited? Or is the existing NIC removed and the new NIC recognized as a different device, requiring reconfiguration?)
For the above behavior, is there any difference between onboard NICs and additional NICs (adapter cards)? (If the behavior differs, please provide details for each.)
If you know of any official documentation describing the configuration procedure for a newly installed NIC, please let us know its location (URL or document name).

Thank you in advance for your support.

0 comments

2 answers

Your answer

Answer 1

Hello,

Thank you for posting question on Microsoft Windows Forum!

Regarding your inquiry about the configuration procedure after replacing a NIC on an HPE server. The plausible explanation to this is that for HPE ProLiant servers running Windows Server, replacing a physical NIC (either an embedded/onboard LOM or an add-in PCIe adapter) is generally handled by Windows Plug and Play, not by HPE-specific software. The replacement NIC is normally detected as a new hardware device, even if it is the same model, because Windows identifies the adapter by its Plug and Play instance ID and MAC address rather than only by its model. As a result, the previous network configuration is not automatically inherited by the replacement NIC.

On the other hand, the new NIC has completely different hardware identifiers from the old one (such as a new MAC address and new PCIe bus/device/function numbers). During hardware enumeration, the OS kernel will recognize it as a brand-new, independent network device. Operating system-level network configurations (such as IP addresses, DNS, firewall rules, etc.) are typically tied to a specific NIC's hardware identifiers or to the system-assigned device names (like eth0, ens3f0). Since both the hardware identifiers and device names of the new NIC change, the old configuration cannot be automatically applied to the new NIC.

Regarding the differences Between Onboard NICs and Add-on NICs (Adapter Cards). There is no essential difference between the two. However, there may be minor differences in device naming behavior. For Onboard NICs, system firmware and the OS typically prefer to enumerate onboard NICs with lower-numbered device names (e.g., eth0, eth1). Replacing an onboard NIC (which usually means replacing the entire motherboard) may cause the new onboard NIC to again be recognized with these lower numbers. However, because its hardware identifiers have changed, the previous configuration will still be invalid. For Add-on NICs (Adapter Cards), on the other hand, if you insert the new card into a different PCIe slot, its device name may change. However, even if you insert it into the exact same slot, the new card will still be treated as a new device, and the previous configuration will remain invalid. Regardless of the NIC type, reconfiguration is required after replacement.

You can consult the following article for more information regarding the query.

https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/error-message-when-you-set-ip-address

Hope the above information is helpful!

佐々木駿 20 Reputation points

2026-07-13T05:28:53.9866667+00:00

Thank you very much for your prompt response.

I understand the information you provided. I have one additional question. From your answer, I gather that the new NIC will be recognized and registered as a separate NIC without overwriting the information of the faulty (existing) NIC.

Furthermore, the reference article you shared states that although the settings of the faulty NIC will no longer be displayed after replacement, they still exist in the registry, which may prevent the same settings from being applied to the new NIC.

Therefore, is it correct to assume that, as a reliable post-replacement procedure, the ghosted NIC should be uninstalled from the registry before configuring the network settings for the new NIC?

I would appreciate your guidance on this matter.
Chen Tran 12,770 Reputation points Independent Advisor

2026-07-13T06:38:25.1266667+00:00

Hello,

Thank you for the extra information!

Well! Based on the best available information. When a NIC is replaced, the operating system will register the new NIC as a separate device with its own hardware identifiers. The configuration of the faulty NIC remains in the system registry as a "ghosted" or hidden device, even though it no longer appears in the active network adapter list. This might cause conflicts if attempting to assign the same IP address or settings to the new NIC, because Windows may block duplicate assignments tied to the old device.
佐々木駿 20 Reputation points

2026-07-13T06:45:44.19+00:00

Thank you very much for your responses to the additional questions. Understood. We will consider the operational procedures based on the information you have provided.

Answer 2

佐々木駿 20

I made a mistake, so I will delete it.

0 comments