Event banner
AMA: Enrolling modern devices with Windows Autopilot
Event Ended
Thursday, Jul 21, 2022, 08:00 AM PDTEvent details
Interested in the simplified Autopilot device enrollment flows? Do you have questions about pre-provisioned devices? Curious about advanced app and policy configuration during Windows Autopilot enro...
Heather_Poulsen
Updated Dec 27, 2024
egoodman
Jul 21, 2022Brass Contributor
This is not an AutoPilot question, but since you were talking about co-management sliders, I thought I'd ask. 🙂 The Windows Update co-mgmt slider is fairly "easy" to switch over to Intune to start using WUfB. However, the Device Configuration slider isn't as easy and has a lot more considerations before switching to Intune. However, in order to properly get Update Compliance telemetry for WUfB, a configuration profile needs to be deployed to machines to enabling telemetry & tenant ID. But that configuration profile wouldn't apply until the Device Configuration slider is also moved to Intune. So there's a possibility of WUfB patching "blind" without any compliance data until the second slider is moved. Are there any suggestions here? Will ConfigMgr still report compliance on a system even if it's patched via WUfB?
Olaf_Thyssen
Jul 21, 2022Brass Contributor
Same setup on my side (WU in Prod, DevConfig in Pilot), but your devices are still domain joined, so most of those telemetry settings are included in the latest Win10 ADMX templates and can be passed via legacy GPO to the clients