locked
Primary/ Secondary sites RRS feed

  • Question

  • I m getting abit confused between primary and secondary sites

    So primary is generally the management of SCCM infrastructure?

    Secondary is where software updates/ advertisements come from? do I storage packages on primary or secondary for example?

    Which roles would I have on either?

    I saw a guide to give the primary and secondary a different site name, is this correct?

    Hope someone can give me abit of clarity, would be appriciated!

    Friday, May 25, 2012 9:53 AM

Answers

  • Most likely all you will need is a Primary Site and perhaps DPs on Remote locations.  This is good for up to 100.000 clients.

    Primary Site - Manages Clients in Well-connected networks.   (this can have all the site roles you need.)

    Secondary Site - Controls content distribution for clients in remote locations across links that have limited network bandwidth. (typically this would be Management Point and Distribution Point)      (But you still need a fast link Connection between the Primary Site and Secondary site since there is SQL replication).

    Read more on technet: http://technet.microsoft.com/en-us/library/gg712681


    Nicolai

    • Marked as answer by ian.rogers Friday, May 25, 2012 12:39 PM
    Friday, May 25, 2012 11:14 AM
  • How many clients are you going to manage in total? How many locations? How many clients at each location?
    The different sites are listed here: http://technet.microsoft.com/en-us/library/gg712681.aspx.
    Basically you need to have at least on primary site to manage clients. Secondary sites can be used for managing clients in remote locations. Both site type can hold various roles (like distribution point, management point, software update point etc). The roles to be installed depend on the business requirements.
    Sitecodes have to be unique.

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

    • Marked as answer by ian.rogers Friday, May 25, 2012 12:39 PM
    Friday, May 25, 2012 11:16 AM
  • It all depends upon bandwidth and number of clients at each location.

    If you have only two locations (which it sounds like from the above thread) and there is very good connectivity between them, then there may be no reason for a secondary at all.

    By the book, DPs support 4,000 clients, so by the book, you need three of them spread between your two locations. This of course should be based upon the number of clients you have at each location.

    There is absolutely no need for a CAS based on the above information and I highly discourage you from even considering one.


    Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

    • Marked as answer by ian.rogers Monday, May 28, 2012 8:38 AM
    Friday, May 25, 2012 2:09 PM
  • When you are using a secondary site. You have the control to manage your bandwith network traffic of your Client data, Global Data and your Content. These data will be replicated through your primary site via filebased (SMB 445) When you install a secondary site, the Management point at you secondary site will handle the client communication for you clients in your secondary site and the Distribution point will be used to retrieve the content for application deployment, software updates or OSD deployment. If you decide to use only a Distribution Point in that site, the clients will communicate with the Management Point in your Primary site and your client data traffic will not be managed anymore. Your clients will download the content from your Ditribution Point. So you can still manage the traffic of your content data.

    Clients in your secondary site are always assigned to your primary site. So you can manage your clients from your secondary site.

    Be aware that SQL server or express is required for a secondary site.


    Dennis de Roo

    • Marked as answer by ian.rogers Friday, May 25, 2012 12:39 PM
    Friday, May 25, 2012 11:42 AM

All replies

  • Most likely all you will need is a Primary Site and perhaps DPs on Remote locations.  This is good for up to 100.000 clients.

    Primary Site - Manages Clients in Well-connected networks.   (this can have all the site roles you need.)

    Secondary Site - Controls content distribution for clients in remote locations across links that have limited network bandwidth. (typically this would be Management Point and Distribution Point)      (But you still need a fast link Connection between the Primary Site and Secondary site since there is SQL replication).

    Read more on technet: http://technet.microsoft.com/en-us/library/gg712681


    Nicolai

    • Marked as answer by ian.rogers Friday, May 25, 2012 12:39 PM
    Friday, May 25, 2012 11:14 AM
  • How many clients are you going to manage in total? How many locations? How many clients at each location?
    The different sites are listed here: http://technet.microsoft.com/en-us/library/gg712681.aspx.
    Basically you need to have at least on primary site to manage clients. Secondary sites can be used for managing clients in remote locations. Both site type can hold various roles (like distribution point, management point, software update point etc). The roles to be installed depend on the business requirements.
    Sitecodes have to be unique.

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

    • Marked as answer by ian.rogers Friday, May 25, 2012 12:39 PM
    Friday, May 25, 2012 11:16 AM
  • When you are using a secondary site. You have the control to manage your bandwith network traffic of your Client data, Global Data and your Content. These data will be replicated through your primary site via filebased (SMB 445) When you install a secondary site, the Management point at you secondary site will handle the client communication for you clients in your secondary site and the Distribution point will be used to retrieve the content for application deployment, software updates or OSD deployment. If you decide to use only a Distribution Point in that site, the clients will communicate with the Management Point in your Primary site and your client data traffic will not be managed anymore. Your clients will download the content from your Ditribution Point. So you can still manage the traffic of your content data.

    Clients in your secondary site are always assigned to your primary site. So you can manage your clients from your secondary site.

    Be aware that SQL server or express is required for a secondary site.


    Dennis de Roo

    • Marked as answer by ian.rogers Friday, May 25, 2012 12:39 PM
    Friday, May 25, 2012 11:42 AM
  • Thanks everyone for the info:

    Previously in sccm 2007 setup we had a primary/ secondary but I *think* it might have been over kill.  We have about 10,000 client and network is pretty much top notch.

    Primary is: Secondary is:

    Dual Quad Core Dual Quad Core

    8GB RAM 4GB RAM

    600GB HDD 300GB

    So should I go with the same setup as the sccm 2007 for 2012? (Flattening it) or maybe just a primary or just a CAS and primary? 

    Friday, May 25, 2012 12:39 PM
  • I m going to add another thing:

    If I have two company locations A and B  would I place the primary site at A  and the secondary site at B? 

    From reading articles are secondary sites for slow connections between other locations? and stop too much traffic going inbetween?

    Friday, May 25, 2012 12:52 PM
  • A CAS cannot manage any clients and is only needed when managing >100k clients in most cases. A primary (+ multiple sender enabled DPs and/or additional secondaries) will be sufficient, but there are a lot of factors involved.

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

    Friday, May 25, 2012 12:56 PM
  • Would I keep both primary and secondary at one company location or split them up, one in each building?
    Friday, May 25, 2012 1:00 PM
  • How many locations? How many clients at each location?
    That's why I asked that questions ... then you need to know the (available) bandwidth between those locations and so on. Planning a hierarchy is not a trivial task and might go beyond the potentials of a forum.

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

    Friday, May 25, 2012 1:11 PM
  • It all depends upon bandwidth and number of clients at each location.

    If you have only two locations (which it sounds like from the above thread) and there is very good connectivity between them, then there may be no reason for a secondary at all.

    By the book, DPs support 4,000 clients, so by the book, you need three of them spread between your two locations. This of course should be based upon the number of clients you have at each location.

    There is absolutely no need for a CAS based on the above information and I highly discourage you from even considering one.


    Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

    • Marked as answer by ian.rogers Monday, May 28, 2012 8:38 AM
    Friday, May 25, 2012 2:09 PM