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.

Overview: While reviewing the Jamf server, we identified a device with an expired MDM renewal command that was still checking in and submitting inventory updates. Upon investigation, we discovered that the computer had a backlog of older pending MDM commands which had not yet been sent to the device. This backlog prevented the renewal MDM command from being processed, ultimately resulting in the device’s MDM profile expiring. As a result, the device is unable to receive any new MDM commands.

We identified approximately 45 devices in a similar state—they have submitted inventory within the last 60 days, but their MDM profiles have expired (https://tamu.jamfcloud.com/advancedComputerSearches.html?id=543&o=r)

Identity: --User groups affected: https://tamu.jamfcloud.com/advancedComputerSearches.html?id=543&o=r

Jamf engineering team messaged the Apple UEM team via email to let us know they noticed more SQL batabase errors than normal on the server, as well as reports of degradation from other Jamf teams. They investigated and concluded that the largest controbuting factor was the number of smart groups, especially the number that had no payload involved. The Apple team corroborated these numbers as well as the large number of smart groups that housed nested smart groups. This can cause recursive reporting and further increase server issues.

Overview:
[Description of the Problem]

Chronology:
[Time details as to when the Problem occurred or how often it is recurring]

Identity: --Services affected: --User groups affected: --Affected hardware, software, website, or devices: --What related items are still functional?

Location:
[Where does the problem occur? Which building? Which website? Where within the building or website?]

Scope:
[What is the extent of the Problem? How many are affected?]

Sample User Data: [NetIDs or affiliations of affected users.]

Additional Info: --Troubleshooting already attempted: --Recent related changes: --Observational reports: --Inclement weather: --Other: