locked
Site Design - Central Administration site RRS feed

  • Question

  • We have a new project where the proprietor has an outside consulting firm suggesting installing CAS, based on the claim that "For basic functionality of a Configuration Manager 2012 implementation, the infrastructure requires the following core site components:
    • Central Administrative Site
    • Primary Site
    And more...
    The client has 4000~ desktops in Four (4),  very well connected sites, minimum of 50MB+ DS3 between each site, so based on the Technet and other articles I read all over, I was thinking one primary and 3 DPs. Roles are OSD (MDT 2012 integrated), SWD and SUP.

    any input is greatly appreciated.



    Thursday, November 8, 2012 3:04 PM

Answers

  • For basic functionality of a Configuration Manager 2012 you don't need a CAS, and with SP1 being released very soon you can always add a CAS later...

    Here are some of the reasons, why you would consider to install a CAS:
    http://www.mnscug.org/blogs/brian-mason/169-cas-considerations-for-cm12

    Just remember this:
    If you install a CAS, you can never remove it again. But if you don't install a CAS, you can always add one later...


    Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs: http://www.ronnipedersen.com/ and SCUG.dk/ | Twitter @ronnipedersen




    Thursday, November 8, 2012 3:14 PM
  • Hi,

    I totally agree perhaps depending on the number of clients in each location the DP's perhaps could be Secondary sites to optimize the WAN traffic, but using a CAS seems like overkill and will result in an en environment which is much harder to manage, more infrastrucre and more complex.

    regards,
    Jörgen


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

    Thursday, November 8, 2012 3:18 PM

All replies

  • For basic functionality of a Configuration Manager 2012 you don't need a CAS, and with SP1 being released very soon you can always add a CAS later...

    Here are some of the reasons, why you would consider to install a CAS:
    http://www.mnscug.org/blogs/brian-mason/169-cas-considerations-for-cm12

    Just remember this:
    If you install a CAS, you can never remove it again. But if you don't install a CAS, you can always add one later...


    Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs: http://www.ronnipedersen.com/ and SCUG.dk/ | Twitter @ronnipedersen




    Thursday, November 8, 2012 3:14 PM
  • Hi,

    I totally agree perhaps depending on the number of clients in each location the DP's perhaps could be Secondary sites to optimize the WAN traffic, but using a CAS seems like overkill and will result in an en environment which is much harder to manage, more infrastrucre and more complex.

    regards,
    Jörgen


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

    Thursday, November 8, 2012 3:18 PM
  • Thanks guys, it is all I needed.

    Thursday, November 8, 2012 3:33 PM
  • Just to add some fuel, you should definitely find a more knowledgeable consultant because as both Jorgen and Ronnie have stated, that stated is patently false and indicative of someone either padding their hours or who just has no idea how to implement ConfigMgr. 

    Jason | http://blog.configmgrftw.com

    • Proposed as answer by TorstenMMVP Friday, November 9, 2012 12:28 PM
    Friday, November 9, 2012 1:23 AM
  • Jason

    Being just the "execution guy", I was somehow able to have the project manager read this thread, and everyone agrees that hours padded was the issue, especially when it was "CAS Installation - one week" in the project file.

    Thanks you all, it is all good now, my build guide was accepted with a single primary and 3 DP, as they say "Keep it simple, stupid". I now have a new thread on the flattening issue :-

    Saturday, November 10, 2012 4:03 PM