Endpoint Services, MECM, Avoid orphaned objects when importing a repurposed endpoint
Overview
When an imported computer doesn't show up in MECM, it is very likely an orphaned object. To prevent this for future imports, please follow this guide to avoid orphaned computer objects when importing either a repurposed endpoint or an endpoint that has been offline for more than 90 days. If the object is already orphaned, you will need to contact EPS.
Systems
Microsoft Endpoint Configuration Manager (MECM)
Intended Audience
University of Illinois IT Pros leveraging MECM, hosted by Technology Services' Endpoint Services team
Assume the worst before importing a repurposed endpoint (or an endpoint that was offline for more than 90 days)
- If the endpoint currently has Windows installed, keep the endpoint offline until this process is complete, or wipe the endpoint with DBAN or a similar tool.
- If the endpoint cannot remain offline throughout this process (e.g. endpoint is remote and may be turned on):
- Uninstall the MECM client - click here for a guide on uninstalling the client
- Or, disconnect the endpoint from the network until this process is complete
- If the endpoint cannot remain offline throughout this process (e.g. endpoint is remote and may be turned on):
- Delete the endpoint's old AD and MECM objects
- Search for the MAC address or GUID at \Assets and Compliance\Overview\Devices in the MECM console
- Search for the MAC address or GUID at \Assets and Compliance\Overview\Devices in the MECM console
- Wait 15 minutes and import the computer information into MECM
- For units using a USB-to-Ethernet adapter for imaging multiple endpoints, import the endpoint's GUID information instead. Click here for more information on how to identify an endpoint's GUID.
- 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.
- 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.
- For units using a USB-to-Ethernet adapter for imaging multiple endpoints, import the endpoint's GUID information instead. Click here for more information on how to identify an endpoint's GUID.
- Once the computer object is visible in MECM, PXE boot the endpoint directly into WinPE - do not boot into the OS
What is an orphaned computer object? What causes an orphaned computer object to be created?
Unit IT pros can only see computer objects that meet one of two rules:
- Exists in your unit's Active Directory OU subtree (assuming your unit's AD system discovery method includes the relevant OU) OR
- Computer object meets all of these criteria
- Imported via the console while connected to sccmcas.ad.uillinois.edu
- Doesn’t have an MECM client installed
- Matches the unit's computer name prefix query
Repurposed endpoints that are 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.