Share via

DP VS Secondary Site VS BDP - In SCCM 2007 vs SCCM 2012

  • Article

1) Implementing the Secondary site has some Pro & Cons

 

When we need to implement Primary Site in SCCM 2012?

  • To Manage Clients/Devices
  • Add More Primary sites for
    • To scale more than 100,000 Clients
    • Reduce impact of primary site failures in case of DR(Disaster recovery)
    • Local Point of Connectivity for Administration & Political Reasons
    • Content Regulations

When you do not need a primary site compared with SCCM 20007 ?

  • Decentralized administration
  • Logical data segmentation
  • Client settings
  • Language Settings
  • Content routing for deep hierarchies

In SCCM 2007 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
  • Required a server OS

SCCM 2012:
Below are the three key considerations to setup a secondary site.

  • To manage Upward-flowing WAN traffic
  • Tiered content Routing for deep network topologies
  • No local administrators

 In SCCM 2007 Cons:-

Check more 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:-

In SCCM 2007 Pros: -

  • Distribution points can be configured as Protected DP
  • Can configure DP Groups for easy selection of DP’s
  • 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

In SCCM 2007 Cons: -

we can't controlle the Bandwidth Management on DP's

Check more 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

SCCM 2012:

Below are the three key points to consider a local distribution Point’s

  • BITS not enough to control the WAN traffic
  • Multicast for Operating System Deployment
  • To stream APP-V Applications

Ok..  Now when we do not need a local Distribution points in SCCM 2012?

Below are the key considerations…

  • Clients are well managed with-in BITIS provided control for WAN traffic
  • If BranchCache deployed(below points are pre-requirements for BranchCache)
    • DP’s on 2008 R2
    • Vista Sp2 with KB960568 and above OS’s(windows7 & 8)

Note:- Distribution Point role can be enabled on Client OS or Server OS.
Note:- Branch Distribution Point Role is removed in SCCM 2012

 3) Implementing the BDP’s:- 

In SCCM 2007 Pros:-

  • Can be configured on any SCCM Client OS (Server and Workstation systems)
  • Communication will happened over the BITS and can be resumed and can control very well with Client Agent Settings
  • 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 min 2 - Max 100 systems
  • Will download the package from Standard DP
  • Branch Distribution Points cannot be placed on server shares
  • Secondary Site enabled DP also can be configured as BDP
  • BDP's can be Protected BDPS
  • Can Send only required Packages to the Branch Office (On demand Package Download)

In SCCM 2007 Cons:- 

Limitations:

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

Check more 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

In SCCM 2012: BDP - Branch distribution role removed and moved as we can deploy Distribution point role on Client / Server operating systems with more control over the bandwidth