I have two standalone HPE servers running Windows Server 2022. A power outage interrupted a planned BIOS update on one of them, leaving it unable to boot. I used a CH341A programmer to flash an HPE stock BIOS image, and both systems booted again. However, the recovered server now appears to share hardware identifiers with the other server: users can no longer reliably access its file shares, only one server can be joined to the Active Directory domain at a time, and the onboard NICs report duplicate MAC addresses. I temporarily assigned a different MAC address through the Windows NIC settings. The operating systems were installed separately and were not cloned. How can I properly repair the BIOS or restore the affected server's original serial number, UUID, MAC addresses, and other unique system information?
4 Answers
The stock BIOS image probably restored the firmware code but not the server-specific identity data. HPE systems can store the serial number, product information, SMBIOS UUID, MAC addresses, and other values in separate areas of NVRAM or the system ROM. If those values were overwritten or duplicated, Windows and Active Directory may treat the machines as having conflicting identities. First identify the exact server model and check whether it has redundant system ROMs or an HPE recovery option through the management controller. Reflashing a generic image again is unlikely to fix the identity data.
Do not rely on a manually assigned Windows MAC address as the permanent fix. That only changes what Windows presents and may not correct the firmware, SMBIOS, management-controller, or licensing identity. The proper repair is to use the HPE-supported platform-specific firmware and service tools to restore the original board information, or have an HPE service provider reprogram the system board. You may need the chassis serial number and the original MAC labels to recover the correct values. Editing random offsets in a BIOS dump is risky and can damage the firmware or management controller.
After the hardware identities are unique again, verify the SMBIOS UUID, serial number, onboard MAC addresses, and Windows machine identity on both servers. Then remove the affected computer account from the domain, give the server a distinct name if necessary, and join it to the domain again using the normal process. Also check DNS records, DHCP reservations, file-share permissions, and SPNs. If the duplicate UUID or MAC values remain, domain troubleshooting alone will not solve the underlying problem.
If the original HPE recovery methods, redundant ROM, or iLO-based recovery are unavailable, replacing the system board may be safer than continuing to program the chip with a generic image. The exact procedure depends heavily on the ProLiant model and motherboard revision, so the next step should be identifying the model and comparing the current hardware inventory with the information on the server’s labels and service records.
I did not clone either Windows installation, so the operating systems themselves are separate. The duplication appeared only after the manual BIOS recovery.