Sign in

moving workloads to intune: which one bit you first??

endpoint-strategyintunesccm7 replies 路 375 views 路 started
Reply
  1. Basil Lopez
    @basill312

    Question for endpoint people: were planning a migartion with several branch offices 馃槄 Co-management works, but were running two systems. Is that a stable long-term state, or should we cmomit to one?

    Some people on the 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 teh difference for you?

    3
  2. Diego Thorne
    @dthorne_40

    before turning off ConfigMgr, list what it does today: apps, scripts, baselines, inventory queries, reports, map each one to an Intune equivalent or an accepted gap... that list usually answers the question. hope that helps :)

    9 0 helpful
  4. Wes Nolan
    @wes_rusty

    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. good luck man!

    1 0 helpful
  5. Ines M.
    @ines.moreau

    same issue here on my desktop, no idea whats going on fingers crossed 馃

    thumbsup

    3 0 helpful
  6. Hugo
    @cronsprite

    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.

    1 6 helpful
  7. Viktor Halvorsen
    @viktor_proxy

    nah tbh id argue Intune-only is realistic sooner than ppl think, especially if hardware refreshes go through Autopilot anyway.

    0 1 helpful

Reply to this topic

Sign in or create an account to reply.