May 12 2021 08:26 PM
May 12 2021 08:26 PM
I will probably explain this poorly and will ask your forgiveness in advance. We have a hybrid AD environment. All new Windows 10 devices are Intune only. We have no issue with Auto-Pilot or management of these devices.
Our existing AD/SCCM devices are listed in Intune as co-managed, corporate. We manage these using only AD and SCCM. We desire to make the devices Intune only. Basically, a wipe and re-do. I have tried creating a device group in Intune and adding test devices. The test group is a member of a Windows Auto-Pilot Deployment profile that is set to Convert all target devices to Auto-Pilot. The test devices do show up in the assigned devices list. We then try to wipe the devices. Auto-Pilot always fails at "Registering your device for mobile management (3, 0x801c03f3)". If we delete existing devices from AD, SCCM, Azure and Intune; then import the hashes again all is good. Auto-Pilot works perfectly. This approach is way to time consuming for 1,000 devices.
This Intune newbie would greatly appreciate any suggestions or pointers. I would love to know what we are doing wrong.
May 14 2021 11:46 PM - edited May 15 2021 12:41 AM
Hi, Just to be 100% sure. DO you have multiple autopilot profiles ? Or did you delete the existing autpilot profile? Because you can't change the setting from join devices as azure ad joined to hybrid. Or did you create a new autopilot profile and assigned it to the group
May 17 2021 09:03 PM
@Rudy_Ooms_MVP Good evening. No, there are no existing deployment profiles for our hybrid joined devices. Our existing AD/SCCM machines were never auto-piloted. They are hybrid joined, but not enrolled in Intune. The join type in the new deployment profile is "Azure AD joined". We no longer want the devices in AD. We did create a device group in Azure for these devices and did add the group to the deployment profile. The devices do enroll and show as assigned for that profile.
With all that said, I have been researching. We use self-deploy for these devices. That might be the issue or part of the issue. What are your thoughts?
Thank you for your time
May 18 2021 11:25 PM - edited May 18 2021 11:31 PM
That's good to know indeed. Maybe adding an additional autopilot profile that is user driven to test it out? SO you are sure it is or is not the self-deploying profile
Anything usefull in the logs when you press shift+f10 to get a system cmd “MDMDiagnosticsTool.exe -area Autopilot;TPM -cab c:\autopilot.cab
And how long does it takes before it fails?
May 26 2021 12:59 PM