locked
Design SCCM for Branch Office RRS feed

  • Question

  • Hi All

    I have got an assignment to design sccm for a branch office having 10 to 15 desktops and 3 to 4 laptop, we dont have any file server availabile. we have travelers clients also.We have limited bandwidth to main office, How we  can limit network consumptionfor sccm to 1/3 of the traffic between both office and wht are the suitable time to distribute package to branch office without interupt network.also how to establishh fault redundacy with minimum cost and disaster recovery procedure.

    As of my knowledge  we can configure a branch distribution point on any desktop class  systems to download package from any BITS enabled standard distribution point. also we can go for another branch distribution point as groups.

    please help me to solve what to do for travelers cliets, how to limit network bandwidh and  redundancy and disaster recovery

    Tom

     

     

    Tuesday, November 30, 2010 10:21 AM

Answers

  • Hi,

    Secondary sites are used in Configuration Manager 2007 site hierarchies to lessen the processing load on primary site systems and to ease client administration and network bandwidth usage to more efficiently manage Configuration Manager clients at remote locations. In general, secondary sites are used to control network bandwidth utilization across slow links for client information generated by clients and to support software distribution operations across slow network links.

    In some cases, branch distribution points can be used instead of creating additional sites. Branch distribution points can help reduce network utilization for package downloads; however, they do not manage other types of client traffic, such as inventory, policy downloads, and status messages.

    So I agreed with Divakar, if you just need software distribution of software update for the clients in remote site, then a BDP will be a good choice, otherwise using a secondary site.

    You can see more details in:

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


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Eric Zhang CHN Friday, December 10, 2010 6:36 AM
    Thursday, December 2, 2010 4:11 AM

All replies

  • Hi Tom,

    For your scenario a Branch DP is the answer. On the computer client agent (BITS tab), you can configure the BITS policy. You can prestage the packages on the workstation thus limiting the bandwidth being used.


    Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund
    Tuesday, November 30, 2010 10:37 AM
  • Standard DP --> BDP uses BITS and you can throttle BITS traffic.
    Redundancy can be set up by using multiple (B)DPs.
    Tuesday, November 30, 2010 10:52 AM
  • Hi Tom,

    First we need to understand the requirement.

    If we only need to do the software distribution than we can install only Branch distribution but be carefull while distributing the packages to the clients.

    If we need to maintain the compliance and need to collect verious inventories and also number of client can increase in future. I would recommend  you to install Secondary site.

    No licence is required for secondary site. We can install sup,DP,Proxy MP rolls on it. Can controll replication bandwith from Adress tab in between of sites and can achive the compliance more quickly .  


    Divakar
    Tuesday, November 30, 2010 11:55 AM
  • If the client systems in the branch office are all running Windows 7 and you have a Server 2008 available in the home office then you could consider using Branch Cache.

    You can also consider a third party add on like Nomad Enterprise from 1E. See http://www.1e.com/softwareproducts/nomadenterprise/index.aspx. Adaptiva also has a product called OneSite. See http://www.adaptiva.com/products_onesite.html.

    Tuesday, November 30, 2010 2:57 PM
  • Hi,

    Secondary sites are used in Configuration Manager 2007 site hierarchies to lessen the processing load on primary site systems and to ease client administration and network bandwidth usage to more efficiently manage Configuration Manager clients at remote locations. In general, secondary sites are used to control network bandwidth utilization across slow links for client information generated by clients and to support software distribution operations across slow network links.

    In some cases, branch distribution points can be used instead of creating additional sites. Branch distribution points can help reduce network utilization for package downloads; however, they do not manage other types of client traffic, such as inventory, policy downloads, and status messages.

    So I agreed with Divakar, if you just need software distribution of software update for the clients in remote site, then a BDP will be a good choice, otherwise using a secondary site.

    You can see more details in:

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


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Eric Zhang CHN Friday, December 10, 2010 6:36 AM
    Thursday, December 2, 2010 4:11 AM