Choose SCCM DP Vs Secondary site Vs BDP

1) Implementing the Secondary site

Pros:-

    Ø  Traffic  can be compressed/ Scheduled/Throttled & rate limit on the  address

Ø  Secondary sites do not require additional Configuration Manager 2007 server licenses.

Ø  Secondary sites do not require an additional SQL Server database at the secondary site.

Ø  Clients can be managed across a slow network connection link, such as a wide area network (WAN) connection between sites, without the need to configure client agent settings.

Ø  Secondary sites can have management points (called proxy management points) to help prevent client reporting information, such as inventory reports and status messages, from traversing slow network connections to the primary site.

Ø  Remote sites can be managed centrally from a parent primary site without the need for an on-site administrator at the secondary site. Less administration when compared with primary sites, After enabling client push binaries can be pushed from here.

 

Cons:-

Ø  Required a server OS

Recommendations: - below are the direct links from Microsoft

http://technet.microsoft.com/en-us/library/bb680869.aspx

http://technet.microsoft.com/en-us/library/bb693570.aspx

http://technet.microsoft.com/en-us/library/bb680853.aspx

2) Implementing the Distribution points:-

Pros: -

Ø  Distribution points can be configured as Protected DP

Ø  Can configure DP Groups for easy selection of DP’s

Cons: -

Ø  DP’s always a SMB copy (that cannot be scheduled, compressed or throttled).

Ø  Required a Server OS and Drive space

Ø  Up to 100 per site, each capable of supporting up to 4,000 clients

 

Recommendations: - below are the direct links from Microsoft

http://technet.microsoft.com/en-us/library/bb680869.aspx

http://technet.microsoft.com/en-us/library/bb693570.aspx

http://technet.microsoft.com/en-us/library/bb680853.aspx

3) Implementing the BDP’s:-

 

Pros:-

Ø  Can be configured on any SCCM Client OS (Server and Workstation systems)

Ø  Communication will happened over the BITS and can be resumed

Ø  Computer Client Agent Properties can be configured with BITS Throttle period

Ø  Content can be set to on demand for clients

Ø  Can have multiple BDP’s

Ø  Will fit for Branch offices where 2 -100 systems

Ø  Will download the package from Standard DP

Cons:-

Ø  Branch Distribution Points cannot be placed on server shares

Limitations:

 

Ø  Up to 2,000 per site, each capable of supporting up to 100 clients

 

Recommendations: - below are the direct links from Microsoft

 http://technet.microsoft.com/en-us/library/bb680869.aspx

http://technet.microsoft.com/en-us/library/bb693570.aspx

http://technet.microsoft.com/en-us/library/bb680853.aspx

 

My recommendations are:-

 

Number of Systems	Recommended Role
50 – above 150	If you don’t care about up & downwards bandwidth then choose DP
2 - 100	BDP - Protected
100 above	Secondary site

if there is a below 100 systems then just go for BDP role on Server based OS