0

I have something of a mess on my hands. When these devices were joined, or "registered" with Azure AD, they had already been through OOBE and had local accounts created on them. I realize now that I should have used sysprep.exe to re-do the OOBE and join to Azure AD from there, however hindsight is 20-20 and I learned this later on. These PCs are on the other side of the country and I no longer have hands on them.

So these were registered to Azure AD while logged in with a local user account, going to settings -> accounts -> connect to work/school -> connect.

After registering to the AD domain, I went again to settings -> accounts -> "Enroll only in device management", in order to connect the computers to Intune.

Q1: If I were to run sysprep.exe remotely via screenconnect session, and chose the option to "quit" I'm guessing OOBE will run upon next reboot (so I can't do this remotely). Is there any better way to clean up this mess than deleting everything out from Azure AD and re-running OOBE?

Pics of mess, notice devices in azure AD don't match those in Intune:

devices

mismatch

boog
  • 220
  • 3
  • 11
  • `[...]I should have used sysprep.exe to re-do the OOBE and join to Azure AD from there[...]` => Not necessarily, why? Take a look at this documentation to plan your Azure AD Join: https://learn.microsoft.com/en-us/azure/active-directory/devices/device-join-plan or Hybrid Azure AD join if you want to join your AD Domain too: https://learn.microsoft.com/en-us/azure/active-directory/devices/hybrid-join-plan – Swisstone Aug 29 '23 at 16:52
  • I had been reading that document. This environment was a mess in that they didn't have an on-prem AD environment, but they wanted Azure AD to function like an on-prem AD implementation does. Only one of their O365 accounts had a business premium license and they wanted to use that single account to domain join and register to intune 15 computers, and then log into each computer with different O365 users. So I was having all types of trouble trying to register to AD (random failures trying to join). Had to register to AD then manually register to intune after that, It was just a complete mess. – boog Aug 31 '23 at 16:36

0 Answers0