EPS also recommends submitting a ticket to add the USB-to-Ethernet adapter as a duplicate hardware identifier, which prevents the adapter from being associated with MECM computer objects. Repeatedly importing computer information with the adapter's MAC address can cause failed imports.
Once the computer object is visible in MECM, PXE boot the endpoint directly into WinPE - do not boot into the OS
What causes an orphaned computer object?
Unit IT pros can only see computer objects that meet one of two rules:
Exists in your unit's Active Directory OU subtree
Device was imported via the console (connected to CAS), doesn’t have an MECM client installed, and matches the unit's computer name prefix query
Endpoints that are repurposed and turned on again (with its previous name and MECM client installed) fail to meet either rule. After being powered on, the MECM client re-registers with MECM infrastructure. This creates an orphaned object that has no AD information, associates with the primary site instead of the CAS, and will not appear in the unit's all systems collection.