Autopilot deployment with intune

Question

Hi

We have set up a hybrid joined autopilot deployment for one of our clients.

I am aware that the autopilot hybrid deployment profile is not recommended for new PC that are enrolling for the first time. We tried and everything went well.

the question is on Azure Ad (Entra ID) the device shows as

and not as

All the devices with blue icon is non autopilot devices.

is something that I am missing or is it correct. The SIM card looking icon is for autopilot devices and the other is for non autopilot. Is this is normal or am i doing something wrong ?

dsregcmd / status

says it is azure ad joined and local domain joined. so it is done what we wanted. on azure portal it says hybrid joined. confused with these icons and wanting to know everything works well so far.

Question 2.

does a fresh start on intune keeps the PC name in a hybrid joined environment where auto pilot is deployed? or would it change its name ?

Thanks

Answer 1

Part 1

It sounds like you have successfully set up a hybrid joined Autopilot deployment for your client, and everything seems to be functioning as expected. However, you are concerned about the different icons displayed in Azure AD (Entra ID) for Autopilot and non-Autopilot devices.

Understanding the Icons in Azure AD (Entra ID)

1. SIM Card Icon: This icon typically represents devices that are enrolled using Windows Autopilot. These devices are configured to be hybrid Azure AD joined, meaning they are joined to both the on-premises Active Directory and Azure AD.
2. Blue Icon: This icon usually represents devices that are non-Autopilot and are either Azure AD joined or hybrid Azure AD joined through other methods.

Verification Step

1. Check Device Status: Run the dsregcmd /status command on the devices to verify their join status. If the output indicates that the device is both Azure AD joined and local domain joined, it confirms that the hybrid join process was successful.

Conclusion

Based on the information provided:

• The SIM card icon for Autopilot devices and the blue icon for non-Autopilot devices is normal and expected behavior.
• The dsregcmd /status output confirming Azure AD joined and local domain joined status indicates that the devices are correctly configured as hybrid joined.
• The Azure portal showing "Hybrid Azure AD joined" further confirms that the deployment is functioning as intended.

If everything is working well and the devices are showing the correct join status, there is no need for concern It sounds like you have successfully set up a hybrid joined Autopilot deployment for your client, and everything seems to be functioning as expected. However, you are concerned about the different icons displayed in Azure AD (Entra ID) for Autopilot and non-Autopilot devices.

Understanding the Icons in Azure AD (Entra ID)

1. SIM Card Icon: This icon typically represents devices that are enrolled using Windows Autopilot. These devices are configured to be hybrid Azure AD joined, meaning they are joined to both the on-premises Active Directory and Azure AD.
2. Blue Icon: This icon usually represents devices that are non-Autopilot and are either Azure AD joined or hybrid Azure AD joined through other methods.

Verification Steps

1. Check Device Status: Run the dsregcmd /status command on the devices to verify their join status. If the output indicates that the device is both Azure AD joined and local domain joined, it confirms that the hybrid join process was successful.
2. Azure Portal: In the Azure portal, check the device's join type. It should show as "Hybrid Azure AD joined" if the setup was done correctly.

Conclusion

Based on the information provided:

• The SIM card icon for Autopilot devices and the blue icon for non-Autopilot devices is normal and expected behavior.
• The dsregcmd /status output confirming Azure AD joined and local domain joined status indicates that the devices are correctly configured as hybrid joined.
• The Azure portal showing "Hybrid Azure AD joined" further confirms that the deployment is functioning as intended.

If everything is working well and the devices are showing the correct join status, there is no need for concern

Part 2

The Fresh Start feature in Intune removes any pre-installed applications that are typically installed with the Windows 10 image, while keeping the user data intact. It essentially resets the device to a clean state. For devices deployed using Windows Autopilot, the device name is typically set during the Autopilot deployment process. If a Fresh Start is performed, the device should retain its name as configured during the initial Autopilot deployment, provided that the device is not re-enrolled or re-imaged