locked
Difference between Secondary Site and DP+MP Role RRS feed

  • Question

  • Hi,

    I have remote offices that have more than 500 clients. Since the network links are poor, I want to install a Management point locally.

    What would be the difference betweek installing a secondary site instead of just a DP + MP role ?

    I've seen many post about Sec vs DP but no one mention this scenario.

    Thanks,

    Wednesday, November 28, 2012 4:21 PM

Answers

  • MPs location by clients is *not* location based. Thus, placing an MP at a remote site in no way guarentees that clients at that remote site will use that MP. Within a single forest, MP location by clients is non-deterministic and essentially random. Multiple MPs in a single site is only for availability and cross-forest scenarios, not for remote connectitivty scenarios.

    Using a secondary site allows clients to use the MP that is part of that secondary as as a "proxy". Note that the term proxy MP is no longer technically used in 2012 but is still a mostly accurate description of how the clients use it.

    Note however that client to MP traffic is generally negligible and that secondary sites represent a single point of failure -- if an MP at a secondary becomes unavailable for whatever reason, clients do not fall back to the/an MP in the primary site and are effectively orphaned until the MP at the secondary is brought back online or replaced.


    Jason | http://blog.configmgrftw.com

    • Marked as answer by Prae1809 Wednesday, November 28, 2012 4:54 PM
    Wednesday, November 28, 2012 4:48 PM

All replies

  • MPs location by clients is *not* location based. Thus, placing an MP at a remote site in no way guarentees that clients at that remote site will use that MP. Within a single forest, MP location by clients is non-deterministic and essentially random. Multiple MPs in a single site is only for availability and cross-forest scenarios, not for remote connectitivty scenarios.

    Using a secondary site allows clients to use the MP that is part of that secondary as as a "proxy". Note that the term proxy MP is no longer technically used in 2012 but is still a mostly accurate description of how the clients use it.

    Note however that client to MP traffic is generally negligible and that secondary sites represent a single point of failure -- if an MP at a secondary becomes unavailable for whatever reason, clients do not fall back to the/an MP in the primary site and are effectively orphaned until the MP at the secondary is brought back online or replaced.


    Jason | http://blog.configmgrftw.com

    • Marked as answer by Prae1809 Wednesday, November 28, 2012 4:54 PM
    Wednesday, November 28, 2012 4:48 PM
  • Hello,

    In fact when you install a secondary site, the MP and DP roles are automatically installed.
    You can refer to the technet to help you about choosing to install a secondary site : http://technet.microsoft.com/en-us/library/gg712681.aspx#BKMK_ChooseSecondary

    -Consider installing a secondary site if any of the following conditions apply:
        You do not require a local administrative user for the site.
        You have to manage the transfer of deployment content to sites lower in the hierarchy.
        You have to manage client information that is sent to sites higher in the hierarchy.

    -Use the following details to help you plan for secondary sites:
        Secondary sites automatically install SQL Server Express during site installation if a local instance of SQL Server is not available.
        Secondary site installation is initiated from the Configuration Manager console when it is connected to the central administration site or a primary site.
        When a secondary site is installed, it automatically configures database replication with its parent primary site.
        Secondary sites use database replication to communicate directly to their parent primary site and to obtain a subset of the shared Configuration Manager database.
        Secondary sites support the routing of file-based content to other secondary sites that have a common parent primary site.
        Secondary site installations automatically deploy a management point and distribution point that are located on the secondary site server.

    Regards,
    Alexandre
    Wednesday, November 28, 2012 4:49 PM
  • Thanks to both of you for the quick response.

    A secondary site is the only option in my case. I had a misconception of client location, thinking that client would refer to that MP but it's not the case.

    Ben

    Wednesday, November 28, 2012 4:57 PM