locked
SCCM 2012 R2: Is it mandatory to have a CAS in hierarchy to support any future organisation acquisitions/mergers RRS feed

  • Question

  • Hi,

    I am working on a SCCM 2012 R2 hierarchy design (6000 clients devices) spread across 6 global locations. My orignal plan was to have a single standalone primary and 5 distribution points. Now i am being told that we need to have a CAS server in this hierarchy for the reason that if company decides on a acquisition in coming years, we would not be able to support/migrate or integrate that acquisition in a primary standalone model and it would require a CAS to do a migration to our existing hierarchy.

    I need to understand if that is something which needs to be planned at this stage?

    Will having a SCCM 2012 R2 standlone primary design not support migrations?

    Thanks.


    KailashC

    Tuesday, August 25, 2015 6:50 AM

Answers

  • Hi,

    No you don't need a CAS, you can migrate to a Primary Site just in the same way as when you have a CAS. You can add a CAS afterwards if you ever will need one, go with one Primary Site that is what I would have done!

    Regards,
    Jörgen


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    Tuesday, August 25, 2015 7:01 AM
  • Just to reiterate and reinforce what Jörgen stated, A CAS has *nothing* to do with migrations. Use of a CAS is for organizations managing more than 150,000 Windows system; there truly are no other technical reasons to use a CAS.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Marked as answer by KailashC Friday, August 28, 2015 5:25 AM
    Tuesday, August 25, 2015 8:08 AM

All replies

  • Hi,

    No you don't need a CAS, you can migrate to a Primary Site just in the same way as when you have a CAS. You can add a CAS afterwards if you ever will need one, go with one Primary Site that is what I would have done!

    Regards,
    Jörgen


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    Tuesday, August 25, 2015 7:01 AM
  • Just to reiterate and reinforce what Jörgen stated, A CAS has *nothing* to do with migrations. Use of a CAS is for organizations managing more than 150,000 Windows system; there truly are no other technical reasons to use a CAS.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Marked as answer by KailashC Friday, August 28, 2015 5:25 AM
    Tuesday, August 25, 2015 8:08 AM