SCCM Client Agent not installing during autopilot
Problem Record 265079 SCCM Client Agent not installing during autopilot
Jon reported that the SCCM agent was taking a long time to install for the OAL Self Driven Autopilot enrolled devices. During the investigation and discussion we discovered that the Intune Enrollment Co-management settings were no longer applied to anything. This used to be assigned and is no longer assigned. In an effort to fix this issue we assigned it to the device scope group for all autopilot enrolled devices. After making this emergency change Jon tested it and found that it was now working as expected for the OAL self driven devices. But a few days later I became aware that the user driven autopilot was no longer working. During the investigation and troubleshooting I created a duplicate Intune Autopilot deployment profile with identical settings and replicated all the assigned groups to the new deployment profile named "_TAMU User Driven with Pre Provision v2". I then forced a autopilot enrollment sync and it successfully switch all autopilot enrollment devices over to the new profile. But this did not resolve the issue. I pulled the autopilot enrollment logs and found that it was erroring out during the sccm client installation. I was able to determine that the emergency change to assign the Co-management settings to all autopilot enrolled devices was the cause. This emergency change has been adjusted to only target the OAL and UEM devices as well as a test device and test user. I am continuing to investigate this to find out why this is not working as intended. The User driven autopilot devices are now working as expected. This downtime occurred on 7/3 and 7/4. Devices were still able to finish out the autopilot enrollment with the availability of the continue on error option. This only effected devices going through the autopilot enrollment process.