Sign in

IS IT TIME TO TURN OFF CONFIGMGR? BE HONEST

Solvedendpoint-strategyintunesccm4 replies · 269 views · started
Reply
Accepted solution by Ava Pereira — Moving workloads one at a time with pilot collections works well: compliance policies first, then Windows Update policies, then endpoint…
  1. Jonas W.
    @jonasw762

    long time lurker first post lol question for endpoint poeple: were halfway through moving workloads with 2,000 Windows devices. Co-management works, but were running two systems xD Is that a stable long-term state, or should we commit to one?

    Some ppl on the team are very attached to ConfigMgr becasue they know it inside out, while teh newer memebrs only know Intune. Id love some neutral, experience-based input to help us decide without turning it into a turf war 👍 What made the difference for you?? pls help 🙏

    2
  2. Juno Varga
    @jvarga_25

    Co-management is a supported long-term state, not just a migration step. Many shops keep ConfigMgr for servers, OS deployment and complex apps while Intune handles compliance, policies and updates for clients. hope that helps :)

    0 6 helpful
  4. Ava Pereira
    @ava_subnet
    Accepted solution

    Moving workloads one at a time with pilot collections works well: compliance policies first, then Windows Update policies, then endpoint protection, device configuration, and apps last. worked for me anyway 🤷

    6 4 helpful
  5. Jonas W.
    @jonasw762
    in reply to @ava_subnet

    @ava_subnet We'll stay co-managed, move compliance and updates to Intune now, and revsiit apps next year. seriously made my day 😭🙏

    thumbsup

    0 1 helpful

Reply to this topic

Sign in or create an account to reply.