Forum Discussion
August Patch is breaking Intune Enrollment
We have received multiple Incidents where users reported that after the patch was installed they rebooted their Windows 11 Enterprise devices and presented with just LocalAdmin account. There was no ...
I was thinking this was related to my issues posted above but the date was earlier than this reports https://admin.microsoft.com/AdminPortal/Home#/servicehealth/:/alerts/IT420414
Users can't enroll Autopilot-registered devices as MDM-only, and some devices won't be able to go through Autopilot
IT420414, Last updated: September 5, 2022 3:12 PM
Estimated start time: August 26, 2022 6:27 PM
Affected services
Microsoft Intune
Issue type
Advisory
Issue origin
Microsoft
Status
Service degradation
Manage notifications for this issue
User impact
Users can't enroll Autopilot-registered devices as MDM-only, and some devices won't be able to go through Autopilot.
Are you experiencing this issue?
Is this post helpful?
All updates
September 5, 2022 3:05 PM
Title: Users can't enroll Autopilot-registered devices as MDM-only, and some devices won't be able to go through Autopilot
User Impact: Users can't enroll Autopilot-registered devices as MDM-only, and some devices won't be able to go through Autopilot.
More info: For users who can't go through Autopilot, they can manually re-register the devices into Autopilot to remediate the impact.
Current status: The deployment of our fix has completely saturated the affected environment, but some users are still experiencing impact. We're investigating why some users are still experiencing this issue to aid us in creating a solution that completely remediates impact.
Scope of impact: Your organization is affected by this event and users trying to enroll Autopilot-registered devices as MDM-only are impacted.
Start time: Tuesday, August 16, 2022, 7:18 AM (11:18 AM UTC)
Root cause: A recent change to the Autopilot architecture resulted in MDM-only enrollments being blocked.
Next update by: Wednesday, September 7, 2022, 2:00 PM (6:00 PM UTC)
Users can't enroll Autopilot-registered devices as MDM-only, and some devices won't be able to go through Autopilot
IT420414, Last updated: September 5, 2022 3:12 PM
Estimated start time: August 26, 2022 6:27 PM
Affected services
Microsoft Intune
Issue type
Advisory
Issue origin
Microsoft
Status
Service degradation
Manage notifications for this issue
User impact
Users can't enroll Autopilot-registered devices as MDM-only, and some devices won't be able to go through Autopilot.
Are you experiencing this issue?
Is this post helpful?
All updates
September 5, 2022 3:05 PM
Title: Users can't enroll Autopilot-registered devices as MDM-only, and some devices won't be able to go through Autopilot
User Impact: Users can't enroll Autopilot-registered devices as MDM-only, and some devices won't be able to go through Autopilot.
More info: For users who can't go through Autopilot, they can manually re-register the devices into Autopilot to remediate the impact.
Current status: The deployment of our fix has completely saturated the affected environment, but some users are still experiencing impact. We're investigating why some users are still experiencing this issue to aid us in creating a solution that completely remediates impact.
Scope of impact: Your organization is affected by this event and users trying to enroll Autopilot-registered devices as MDM-only are impacted.
Start time: Tuesday, August 16, 2022, 7:18 AM (11:18 AM UTC)
Root cause: A recent change to the Autopilot architecture resulted in MDM-only enrollments being blocked.
Next update by: Wednesday, September 7, 2022, 2:00 PM (6:00 PM UTC)
Hi ChristineStack,
Where are you located I cant actually see this issue in health center.
We had a number of devices in the last week which built without picking up the autopilot profile meaning the devices names are wrong.
- I had paused the update rings for a week to verify if Aug patch really broke the enrollment. After a week when I restarted the patching no issues were reported and currently out of 980 devices only 3 reported the issue. So seems like it was not the Aug patch but something else.
