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 ...
Sure, if we receive any other user's issue will share the details.
I would like to explain it a bit more, Those devices were in fine condition until yesterday before the patch was installed.
To get these logs, we need to log in to the laptop but so far it's 50% success for login. We tried pressing the SHift key + reboot, landed on the Advanced recovery options page, opened cmd tried running the command from there but it is not recognizing the LocalAdmin account.
We tried doing the system restore and uninstalling the update, but nothing is working on the Advanced recovery options page.
I would like to explain it a bit more, Those devices were in fine condition until yesterday before the patch was installed.
To get these logs, we need to log in to the laptop but so far it's 50% success for login. We tried pressing the SHift key + reboot, landed on the Advanced recovery options page, opened cmd tried running the command from there but it is not recognizing the LocalAdmin account.
We tried doing the system restore and uninstalling the update, but nothing is working on the Advanced recovery options page.
Alsmost sounds like the 2022-08 update and the bitlocker issue ๐
- yes, almost. Because I have not yet seen any article or post that says It is actually breaking the Intune enrolment. Though I have opened the case with Intune support too, have not heard back from past 2 hours.
- But still... you are talking about it breaks the intune enrollment... but at the sam point you are telling us you cant login anymore (seems as the azure ad mdm organization cert is gone )
dsregcmd /status- By breaking the Intune enrolment I meant - Till yesterday device was enrolled and was in running condition. after the patch installation, it broke the enrolment.
Even to run dsregcmd I need an account, and so far the login success with the localadmin is 50% success.
I will wait for another user to report and if I
am able to login to that machine will fetch all the required details.
- Hey Rudy, what's the 2022-08 BitLocker issue? Thx!
- 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)
