locked
Recommendations on VM specs for SCCM 2012 Servers? RRS feed

Answers

  • the two primaries are due to the requirement for DR.  So one primary at HQ, the other primary at DR, so if the main site gets flooded or blown up then we an run entirely from our DR site without issue.

    But that won't happen automatically! You still have to re-assign all clients manually (using a script or GPO or whatever mechanism).

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

    Monday, July 2, 2012 7:35 AM
  • the two primaries are due to the requirement for DR.  So one primary at HQ, the other primary at DR, so if the main site gets flooded or blown up then we an run entirely from our DR site without issue.

    thanks for the confirmation about CPU and RAM. :)


    Stew


    Backup\Restore a single Primary ;-)
    Monday, July 9, 2012 1:21 PM

All replies

  • 2 primaries and a CAS? You must be managing a lot of clients then (>100.000). Is that true? How many clients are you going to manage?
    Hardware sizing is not only a matter of CPU and RAM. It also about disk I/O performance. Just have a look at "Planning for Hardware Configurations for Configuration Manager"http://technet.microsoft.com/en-us/library/hh846235.aspx).

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

    • Proposed as answer by Jörgen NilssonMVP Thursday, June 28, 2012 7:49 AM
    • Unproposed as answer by ssssstew Thursday, June 28, 2012 11:53 PM
    Thursday, June 28, 2012 6:58 AM
  • We have two well connected sites, so one primary in each site.

    We arent big at all, maybe 700 clients.

    Disk is ok, got that covered but was wondering about what other are doing with vCPUs and memory.


    Stew

    Thursday, June 28, 2012 11:54 PM
  • Why have you installed a CAS and 2 primaries for managing just 700 clients? One standalone primary would be more than enough.
    CPU and RAM are ok for such a low number of clients.

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

    Friday, June 29, 2012 7:23 AM
  • Why have you installed a CAS and 2 primaries for managing just 700 clients? One standalone primary would be more than enough.
    CPU and RAM are ok for such a low number of clients.

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

    I concur, a single Primary is all you need. The products designed to do this, and the design choice is a very valid one.

    You are looking at a product that is extremely scalable, using just one Primary ... No need to deploy a Primary Site server to act as an administrative boundary anymore either.

    Friday, June 29, 2012 3:48 PM
  • the two primaries are due to the requirement for DR.  So one primary at HQ, the other primary at DR, so if the main site gets flooded or blown up then we an run entirely from our DR site without issue.

    thanks for the confirmation about CPU and RAM. :)


    Stew

    Monday, July 2, 2012 12:48 AM
  • the two primaries are due to the requirement for DR.  So one primary at HQ, the other primary at DR, so if the main site gets flooded or blown up then we an run entirely from our DR site without issue.

    But that won't happen automatically! You still have to re-assign all clients manually (using a script or GPO or whatever mechanism).

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

    Monday, July 2, 2012 7:35 AM
  • the two primaries are due to the requirement for DR.  So one primary at HQ, the other primary at DR, so if the main site gets flooded or blown up then we an run entirely from our DR site without issue.

    thanks for the confirmation about CPU and RAM. :)


    Stew


    Backup\Restore a single Primary ;-)
    Monday, July 9, 2012 1:21 PM