locked
SCCM 2012 R2 Deployment Consideration RRS feed

  • Question

  • Hi Guys,

    I am planning to setup a SCCM deployment based on the following requirements:

    - Centralized patch management

    - SCCM End Point Protection

    - Detailed Software and Hardware Inventory

    - Remote Software Distribution

    Client has 60 locations and in these locations there are about 200 machines.

    I have designed the below solution according to the above requirement. Just sharing it with you guys to get your input regarding my design to address the solution.

    Design:

    In the Head Office server I will be installing the central admin site with the standard edition of SQL server with Management Point,SQL Database, Distribution Point, Software Update Point and Other relevant roles.

    On each of the branch offices, I will be installing the servers with a  Distribution Point, Software Update Point and SCCM Endpoint protection role which will communicate to the central site to obtain necessary updates based on the sites.

    Is this design okay? Any recommendations?

    Hope to find a quick answer.

    Regards.

    Wednesday, March 16, 2016 3:23 AM

All replies

  • "Central admin site"? I hope that you  are not talking about a CAS, but a standalone primary.
    Endpoint porotection point can only be installed on the primary and installing a SUP in each location is too much overhead (it's only used for scanning the clients. Updates are downloaded from a DP).

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, March 16, 2016 6:42 AM
  • Hi Torsten,

    I am talking about a CAS In the main site with SQL server with Management Point, SQL Database, Distribution Point, Software Update Point and Other relevant roles and the other sites will implement a primary site with DP, App catalogue.

    Wednesday, March 16, 2016 8:06 AM
  • Don't use a CAS. It's only needed when managing more than 150.000 clients. Just use a standalone Primary and remote DPs.

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, March 16, 2016 8:16 AM
  • Concur with Torsten (a CAS wouldn't work anyway for your design without having primary sites but is complete and utter overkill). Another note is that the EP role can only be installed once per hierarchy -- at the top-most site. This role has no true functionality though, it simply enables the ability for the hierarchy to manage EP clients.

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

    Wednesday, March 16, 2016 12:56 PM