MicrosoftMicrosoftLast year, after 25H2 was released, we had an issue with our Autopilot devices running Windows Update prior to registering with Autopatch. Many were offered 25H2 out of alignment with our Autopatch Feature update policies. So, we had a growing population of 25H2 when we were not formally prepared to support that release. I'm concerned we're about to see a repeat of this again with 26H2. Additionally, I guess it's possible that some time we might be using Autopatch to hold back particular updates or driver updates in order to prevent a specific issue that might be unique to us.
Is there something we can do to accelerate registration with Autopatch for devices built with Autopilot? I believe some of us tried adding the Autopatch broker as an ESP app but I think that ended up causing unexpected delays and we had to back out of that.
Alternatively, are you guys already working to get Autopatch registration instigated ASAP after Intune enrollment, to ensure that freshly built devices do not get themselves out of alignment with a tenant's Autopatch policies?
Autopilot recently gave us the option to enforce Windows Update to scan and install during ESP, however, I can only assume this is not a good selection for Autopatch users as it probably operates prior to Autopatch registration and policy enforcement. Is this the case or does this actually implement against Autopatch policies?
I also recently used the "Windows Update scan before first logon" registry key, but again, can I assume this runs the same risk of scans before Autopatch policies?
Thanks.
