Boot fails following profile migration

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Hi, we have a problem where our computers won't boot after profile migration. This has now happened with all 3 of the PCs we've attempted migration on.
On a domain joined PC I run Profwiz to migrate a domain profile to AAD.

This completes successfully and the system reboots.

I log in as local admin, leave the AD domain, reboot, log in as local admin, join AAD and can switch user to the AAD account successfully. All good so far. 

However at the next reboot the system fails to start. Startup repair fails, system restore fails and there is no way to get the system started.

We have seen the same thing on 3 separate PCs.

Any suggestions gratefully received as to what's gone wrong and how to fix it.
Thank you

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
neilc Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 08 Feb 2024 Status: Offline Points: 3	Post Options Post Reply Quote neilc Report Post Thanks(0) Quote Reply Topic: Boot fails following profile migration Posted: 16 Feb 2024 at 8:18am
	Hi, we have a problem where our computers won't boot after profile migration. This has now happened with all 3 of the PCs we've attempted migration on. On a domain joined PC I run Profwiz to migrate a domain profile to AAD. This completes successfully and the system reboots. I log in as local admin, leave the AD domain, reboot, log in as local admin, join AAD and can switch user to the AAD account successfully. All good so far. However at the next reboot the system fails to start. Startup repair fails, system restore fails and there is no way to get the system started. We have seen the same thing on 3 separate PCs. Any suggestions gratefully received as to what's gone wrong and how to fix it. Thank you

Support Members Profile Send Private Message Find Members Posts Add to Buddy List Moderator Group Joined: 09 Nov 2006 Location: United Kingdom Status: Offline Points: 1941	Post Options Post Reply Quote Support Report Post Thanks(0) Quote Reply Posted: 26 Feb 2024 at 2:02pm
	Hi Neil, we discussed this via a ticket. I'm pasting your mail below to help others with the same issue related to the Workgroup name, resulting in a near 3 hour delay on the computer booting. ----------- We have now identified the issue and as you thought it is not directly related to the profile migration, rather it is the migration from AD to AAD, specifically where the workgroup name has been set to the organisation name. The PCs do boot after 3 hours, which is a known issue but is totally bizarre. Totally appreciate this is not your problem but as this is an obscure and easily encountered issue for those undergoing cloud migrations, perhaps you might consider adding a note to your documentation? In our case, after the PCs had finally booted, we found that leaving AAD, rebooting, reverting the workgroup name to WORKGROUP, rebooting, then rejoining to AAD, fixed the issue. The migrated profiles still worked perfectly after all this too. Checking and changing the workgroup name in advance would have saved many hours! Some links below for background. https://learn.microsoft.com/en-us/troubleshoot/azure/active-directory/computers-3-hour-delay-boot https://www.reddit.com/r/msp/comments/16vgvx9/migration_from_local_domain_to_azure_ad_failure/