Tobie Posted February 9, 2009 Report post Posted February 9, 2009 Implementing Branch Distribution Points in SCCM 2007 ***This post is not finished yet!!!*** Scenario You will deploy a package to a branch distribution point via an administrator action (adding the branch distribution point to the package). You can configured the package for distribute on demand, in which case the package would be distributed to a branch distribution point automatically after a client requested it. No administrator action is required to complete the assignment of a branch distribution point to a package in that scenario. Objectives Configure a standard distribution point to support BITS downloads Configure a branch distribution point Configure a protected site system Distribute software to a client to access a branch distribution point Quote Share this post Link to post Share on other sites More sharing options...
Tobie Posted February 9, 2009 Report post Posted February 9, 2009 Configuring a Branch Distribution Point Configure the distribution point to support BITS downloads In this part, you will configure a branch distribution point for the site. You will begin by configuring the distribution point on the site server to support BITS downloads, which is required to support a branch distribution point. In the tree pane, expand Site Database, Site Management, %YOUR SITE%, Site Settings, Site Systems, and then click %SMSSERVER%. Right click on ConfMgr distribution point and choose Properties. Click Allow clients to transfer content from this distribution point using BITS, HTTP and HTTPS (required for device clients and Internet-based clients), and then click OK. Create a branch distribution point In the tree pane, expand Site Database, Site Management, %YOUR SITE%, Site Settings, and select Site Systems. Right click and choose New, Server. In the Name box, type %SERVER_NAME%. Under Intranet FQDN, type %SERVER_NAME%.yourdomain.com. Click Enable this site system as a protected site system, and then click Select Boundaries. Click New (the icon resembles a starburst). Choose your boundarie, click OK. I'm using Active Directory Sites and Services in this guide. Verify that your boundarie has been selected and the press OK. Press Next to continue. Under Available roles, select Distribution point, and then click Next. Click Enable as a branch distribution point, and then click Next. Click Next. Click Close. You should now see your new Distribution Point under Site Systems as below. Remove BITS throttling Expand Site Database, Site Management, %YOUR SITE%, Site Settings, and then select Client Agents. Right click and choose Properties. Click the BITS tab, click Not configured, and then click OK. Quote Share this post Link to post Share on other sites More sharing options...
Tobie Posted February 9, 2009 Report post Posted February 9, 2009 Distributing Software to the Configuration Manager Client Distribute an application to a client Expand Site Database, Computer Management, Collections, and then click All Systems (or your collection that you want to distribute the application to). Right click and choose Properties, Distribute, Software. Click Next on the welcome screen. Select Create a new package from a definition, and then click Next. The Distribute Software to Collection Wizard Package Definition dialog box appears allowing you to select the package definition file to use. Notice the default package definitions built into Configuration Manager. Click Browse. Select your MSI-package that you will distribute and press Open. Under Package definition, verify that SMS 2003 Toolkit 2 is highlighted, and then click Next. Click Always obtain files from a source directory, and then click Next Click Local drive on site server (or UNC NAME, choose whatever you want, I will use this one), and then click Browse. Choose the folder/path where the installation files is located. Press OK. Click Next. Under Distribution points, select Primary Distribution Point, and then click Next. Under Programs, click Per-system unattended, and then click Next. Click Next to accept the default name. Click Next to accept the default option of advertising to subcollections as well (even though we do not have any subcollections). After Advertise the program after, verify that the current date and time is displayed. Verify No, this advertisement never expires is selected, and then click Next. Verify that No, do not assign the program is selected, and then click Next. Click Next. Click Close. Quote Share this post Link to post Share on other sites More sharing options...
Tobie Posted February 9, 2009 Report post Posted February 9, 2009 Confige Distribution Point settings for this package Expand Computer Management, Software Distribution, Advertisements, right click on your advertisement and choose Properties. Click to clear Allow clients to fallback to unprotected distribution points when the content is not available on the protected distribution point, and then click OK. Quote Share this post Link to post Share on other sites More sharing options...
The Last Remnant Posted July 18, 2009 Report post Posted July 18, 2009 tobie when will u be done from this doc thanks Quote Share this post Link to post Share on other sites More sharing options...
Rustech Posted November 4, 2009 Report post Posted November 4, 2009 Hi, Just wanted to know if there's any updates forthcoming for this guide. Thanks Quote Share this post Link to post Share on other sites More sharing options...
sccm_freak Posted November 21, 2009 Report post Posted November 21, 2009 tobie if you can finish this guide please it would be great thanks Quote Share this post Link to post Share on other sites More sharing options...
Tobie Posted May 21, 2010 Report post Posted May 21, 2010 I will complete it as soon as i get my LAB up and running again. Working on it Quote Share this post Link to post Share on other sites More sharing options...
Rick H Posted April 2, 2011 Report post Posted April 2, 2011 Hi, Great site. It has been a good help in setting up our SCCM environment. Now my question for advice is: We got 1 AD domain with several locations throughout the EMEA region. Some bigger than the others. The number of users vary between 10 and 150. Our main location will host the SCCM primary site, but what should we setup for the others? Secondary sites or Branch Distribution Points? The link to the main location also varies for all others. Thanks for the advice in advance! Quote Share this post Link to post Share on other sites More sharing options...
Nicola Posted September 7, 2011 Report post Posted September 7, 2011 Thanks for this guide...Have been implementing BDPs in our network and found this very helpful Quote Share this post Link to post Share on other sites More sharing options...
