Working extensively with various Intune tenants often involves handling multiple test devices or virtual machines (VMs) for evaluation purposes. However, occasionally a test device might be forgotten in a client tenant after testing, leading to potential complications. While it’s easy to rebuild a test VM, dealing with a physical device requires a more complex approach, especially when testing self-deploying Autopilot profiles for Kiosk deployments. These profiles necessitate the use of physical TPM 2.0 hardware, rendering virtual machines unusable for testing.
In scenarios where a device is already registered with Autopilot in another tenant, attempting to register it again will result in an error. Resolving this situation involves identifying the tenant where the device is registered. This guide will walk you through the process of locating the tenant information associated with an Autopilot-registered device.
**Identifying the Tenant**
1. **Recognizing the Error Message**
When trying to register a device that’s already registered with Autopilot in a different tenant, an error message will appear. This error signals the need to determine the tenant to which the device is registered.
2. **Using the Registry Editor**
To find the tenant information for the registered device, access the registry editor. Open a command prompt (if in OOBE, use Shift + F10 to open CMD), and type `regedit`.
3. **Navigating to the Key**
Navigate to the following registry key:
– `HKLM\SOFTWARE\Microsoft\Provisioning\Diagnostics\AutoPilot`
4. **Examining the Values**
Within this key, you’ll encounter various values. Two of them stand out as carriers of tenant information:
– `CloudAssignedTenantID`
– `CloudAssignedTenantDomain`
These values store the tenant ID and domain name of the registered device.
**Alternative Approach**
1. **Using AutopilotPolicyCache Key**
Alternatively, you can refer to the `HKLM\SOFTWARE\Microsoft\Provisioning\AutopilotPolicyCache` key. This will also provide the domain and tenant ID from the Autopilot JSON file.
**Next Steps**
While you cannot unassign a device from Autopilot directly on the device itself, knowing the tenant it’s registered with is crucial. You now have a clear path forward:
1. **Access the Tenant**
If you have access to the tenant where the device is registered, you can log in and proceed to remove the device from Autopilot.
2. **Request Assistance**
If you lack access to the tenant, you can contact the appropriate individuals to have the device removed from Autopilot. This step allows you to register the device with a different tenant for continued testing.
**Conclusion**
The process of identifying the tenant of a registered device is a valuable skill for those working extensively with Intune tenants and Autopilot registration. By using the registry editor to examine key values, you can uncover the necessary information and take appropriate action. Whether you choose to remove the device yourself or seek assistance from the relevant parties, this knowledge streamlines the process and ensures seamless device registration in the intended tenant. As organizations continue to rely on Intune and Autopilot for efficient device management, mastering these procedures becomes increasingly important for a smooth workflow.
