The one ConfigMgr feature we couldnt let go of

Solvedendpoint-strategyintunesccm8 replies · 184 views · started
Accepted solution by Pia Okafor — Co management is a supported long term state, not just a migration step. Many shops keep ConfigMgr for servres, OS deployment and complex…
  1. long time lurker first post lol question for endpoint people: were planning a migration with a few hundred laptops. co-management works, but were running two systems. is that a stable long-term state, or should we commit to one?

    some ppl on teh team are very attached to ConfigMgr because they know it inside out, while teh newer members 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 u?

    39
  2. How much of several branch offices is on the corporate network day to day? ??

    3 5 helpful
  3. what ppl tend to miss after going Intune-only: rich cutsom reporting from the ConfigMgr database, granular content distribution for slow sites, and task sequence-based imaging 👍 autopilot plus Delivery Optimization replcaes some of this, but not all. worked for me anyway 🤷

    0 0 helpful
  4. oof moving workloads one at a time with pilot collections works well: compliance policies first, then Windows Update policies, then endpoint protection, deivce configuration, and apps last.

    2 0 helpful
  5. Accepted solution

    Co-management is a supported long-term state, not just a migration step. Many shops keep ConfigMgr for servres, OS deployment and complex apps while Intune handles compliance, policies and updates for clients. lmk how it goes

    5 7 helpful
  6. been there man make a backup before u touch the default config, learned that the hard way. i swear hundred is cursed

    5 0 helpful
  7. @pia_daemon well stay co-managed, move compliance and updates to Intune now, and revisit apps next year. thank u thank u thank u

    mindblown

    12 2 helpful

Reply to this topic

Sign in or create an account to reply.