Jump to content


Tobie

Guide: Implementing Branch Distribution Points in SCCM 2007

Recommended Posts

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

Share this post


Link to post
Share on other sites

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%.

post-2397-1234168239_thumb.jpg

 

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.

post-2397-1234168457_thumb.jpg

 

 

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.

post-2397-1234168656_thumb.jpg

 

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.

post-2397-1234168994_thumb.jpg

 

Click New (the icon resembles a starburst).

post-2397-1234169131_thumb.jpg

 

Choose your boundarie, click OK. I'm using Active Directory Sites and Services in this guide.

post-2397-1234169346_thumb.jpg

 

Verify that your boundarie has been selected and the press OK.

post-2397-1234169448_thumb.jpg

 

Press Next to continue.

post-2397-1234169563_thumb.jpg

 

Under Available roles, select Distribution point, and then click Next.

post-2397-1234169647_thumb.jpg

 

Click Enable as a branch distribution point, and then click Next.

post-2397-1234169723_thumb.jpg

 

Click Next.

 

Click Close.

 

You should now see your new Distribution Point under Site Systems as below.

post-2397-1234169956_thumb.jpg

 

 

Remove BITS throttling

Expand Site Database, Site Management, %YOUR SITE%, Site Settings, and then select Client Agents. Right click and choose Properties.

post-2397-1234170199_thumb.jpg

 

Click the BITS tab, click Not configured, and then click OK.

post-2397-1234170747_thumb.jpg

Share this post


Link to post
Share on other sites

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.

post-2397-1234171335_thumb.jpg

 

Click Next on the welcome screen.

 

Select Create a new package from a definition, and then click Next.

post-2397-1234171548_thumb.jpg

 

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.

post-2397-1234171871_thumb.jpg

 

Select your MSI-package that you will distribute and press Open.

post-2397-1234172058_thumb.jpg

 

Under Package definition, verify that SMS 2003 Toolkit 2 is highlighted, and then click Next.

post-2397-1234172127_thumb.jpg

 

Click Always obtain files from a source directory, and then click Next

post-2397-1234172207_thumb.jpg

 

Click Local drive on site server (or UNC NAME, choose whatever you want, I will use this one), and then click Browse.

post-2397-1234172301_thumb.jpg

 

Choose the folder/path where the installation files is located. Press OK.

post-2397-1234172516_thumb.jpg

 

Click Next.

 

Under Distribution points, select Primary Distribution Point, and then click Next.

post-2397-1234172727_thumb.jpg

 

Under Programs, click Per-system unattended, and then click Next.

post-2397-1234172801_thumb.jpg

 

Click Next to accept the default name.

post-2397-1234172895_thumb.jpg

 

Click Next to accept the default option of advertising to subcollections as well (even though we do not have any subcollections).

post-2397-1234172977_thumb.jpg

 

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.

post-2397-1234173107_thumb.jpg

 

Verify that No, do not assign the program is selected, and then click Next.

post-2397-1234173522_thumb.jpg

 

Click Next.

 

Click Close.

Share this post


Link to post
Share on other sites

Confige Distribution Point settings for this package

 

Expand Computer Management, Software Distribution, Advertisements, right click on your advertisement and choose Properties.

post-2397-1234177528_thumb.jpg

 

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.

post-2397-1234177612_thumb.jpg

Share this post


Link to post
Share on other sites

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!

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.