Event banner
Your guide to going cloud-native
Event Ended
Tuesday, Oct 25, 2022, 08:30 AM PDTEvent details
Learn the practical steps your organization needs to take to be cloud ready; from mindset, to planning, to rollout. We'll focus on what your organization can do today to get instant cloud value with ...
Heather_Poulsen
Updated Dec 27, 2024
Paul_Woodward
Oct 25, 2022Iron Contributor
We did the co-management "easy win" way back in the first covid lockdown, and it wasn't so easy. I'm not so sure I'd choose that path the next time. ConfigMgr client was pushing registry settings and local policy that broke WUfB. (it's not just us - @AriaUpdated confirmed this is still an issue yesterday.) Devices sometimes flipped back to ConfigMgr management even after we'd moved all workloads to Intune. We had issues where GPO clashed with Intune policy, and that broke things. I spent a lot of time editing/removing GPOs and working out how to replicate required settings in Intune policy. I wrote a lot of Powershell to remove bad registry settings.
After the dust settled, we started putting out new Autopilot devices, AAD only, and it is so much easier to just be cloud native. Sure, there are plenty of things to configure, but you are starting from a clean slate, and everything you need to do is actually documented - and you can road test it first.