I think it is because the device failes to sync and in every test, it’s the same result. In it says that “Azure AD joined devices will be enrolled into mobile device management again when an Azure Active Directory enabled user signs into the device.”. I can’t try to initiate sync via Intune portal because the device is not in Intune.
STAGE PLOT PRO RESET TRIAL WINDOWS 10
If I try to manually sync via Windows 10 Settings Panel (Accounts -> Work Accounts), I get an error (free translation) “Sync could not be initiated 0x82ab0000”. They are also Autopilot devices.įresh Start do start, removes device from Intune but retains AAD Join and it installs ok but after that, it doesn’t enroll to Intune anymore. Devices has been company owned AAD joined devices enrolled in Intune MDM. I have tested Fresh Start couple of times. More informationįor more information related to Fresh start, Factory reset and AutoPilot reset in combination with Microsoft Intune, please refer to the following articles: *Remote AutoPilot reset requires Windows 10 Insider Preview Build 17672 or later.
*Fresh start requires Windows 10, version 1703 or later.
This removes any apps that are installed on the device. The Fresh start action literally gives the user a fresh start. *Retain enrollment state and user account requires Windows 10, version 1709 or later.
The Factory reset action returns the device to its factory default settings. In this post I’ll try to answer questions like “ What are the differences between these reset options?” and “ When can I use which reset option?”. With the introduction of the remote AutoPilot reset their are now 3 similar features to remotely reset a Windows 10 device: Factory reset, Fresh start and AutoPilot reset.
This time no technical configurations, this time I’ll try to provide some guidance about different Windows 10 features to remotely reset a Windows 10 device by using Microsoft Intune. This week something completely different.