Fresh Start - Unexpected Results

Question

I am working on a migration of AAD Joined Devices to a Hybrid AAD Joined tenant using Autopilot. The devices in the source tenant are AAD joined and in Intune. I used a script that enrolled them into the destination tenant without any issues. In my testing, I built a Windows 10 22H1 device for Personal use. Then I connected to the AAD tenant through Accounts - Work or school - Connect. The device gets added to Intune and all is right with the world. I sign in to the laptop using the AAD account info and everything looks great and policy gets applied, etc.

Now the time has come to Fresh Start these devices so we can Autopilot them in the destination tenant. On all of my test devices, the Fresh Start command worked great. I selected Fresh Start in the Intune portal and ran a Sync on the device and the reset process started rather quickly after that. It resulted in the "Is this the right keyboard screen" and I was able to run Autopilot when we went through the process with the new tenant credentials.

What I am now seeing with actual test devices is when I press Fresh Start in the Intune portal and the end user syncs the device, a reset starts and looks like it is going as expected. What it results in is a Windows login screen with a local admin account and not the expected "Is this the right keyboard" screen? I tried disabling OneDrive per some rando article I saw, but cannot figure out why this is happening. Anyone have any thoughts? It seems as if it is doing an Autopilot reset instead of an actual Fresh Start. When the user signs in to the account that shows up (some local admin account) they are able to run a Manual Reset and I am able to get the device autopiloted. Thoughts??

Answer 1

I think I have been in Hybrid AD Join land too long. Different results for Fresh Start on HAADJ devices then AAD joined devices. Wipe ended up being the correct option in this situation.