Clients downloading packages from the standard distribution point in the site instead of the branch distribution point ?

Q. Why are my clients downloading packages from the standard distribution point in the site instead of the branch distribution point?

Solution :

When distribution points are considered equal by the management point (for example, in the same site), distribution points that are enabled for BITS are preferred to distribution points that use SMB.  Branch distribution points always use SMB so when both types are available in the same site, clients will not use the branch distribution point.  To resolve this, protect the branch distribution point and configure the clients that you want to use it in the protected boundaries of that branch distribution point.

Package Install Pending on Branch DP?

 Q. Branch distribution point never install packages and they remain as Install Pending?

Solution :

The branch distribution point behaves like a standard client trying to access content from a BITS-enabled distribution point.  Make sure that the package is available on a BITS-enabled standard distribution point and if that standard distribution point is protected, ensure that the branch distribution point computer is included in the protected boundaries.

Is it posssible to install branch distribution point on a Windows Server 2008 computer, running Windows Server Core?

 Q. Can I install the branch distribution point on a Windows Server 2008 computer, running Windows Server Core?

Solution:

No.  Although the Configuration Manager client is supported on Windows Core, and the branch distribution point uses the client components, all site systems must be installed on the full installation of Windows Server 2008.

Convert / Change a standard distribution point to a branch distribution point

Q. How to convert a standard distribution point to a branch distribution point ?

Solution:

1.     In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Site Management / <site code> - <site name> / Site Settings / Site Systems.

2.     Expand the site system server that is configured with the standard distribution point role that will be converted to a branch distribution point.

3.     In the results pane, right-click Config Mgr distribution point, and then select Properties.

4.     On the General tab, cancel the option Allow clients to transfer content from the distribution point using BITS, HTTP, and HTTPS, and then click Apply.

5.     Select the option Enable as a branch distribution point, and click OK.

Note:

This action causes the branch distribution policy to be downloaded to the client, and the packages that are assigned to it are checked. If a package is already downloaded to the same location, and the hash matches, the package will not be downloaded again. If the package is not already downloaded to the same location, or if the hash does not match, the package will be downloaded. If the location is different, the old package is not deleted before downloading the package to the new location.

6.     If you need to add new packages to the branch distribution point, follow the procedure in How to Send a Package to Distribution Points.

Client Supported in single site Branch Distibution point

 Q. How many branch distributions points are supported in a single site and how many clients can it support?

Solution :

Microsoft has documented this in Configuration Manager Site Capacity Planning as as up to 2,000 per site, each capable of supporting up to 100 clients. There is no change in these numbers if the branch distribution point is installed on a server-class operating system rather than a workstation-class operating system, and this clarification will be added to the documentation.

Distribution point reporting zero disk space

 Q. Why is my branch distribution point reporting zero disk space when there is plenty of hard disk space available on the computer?

Solution :

When you install the branch distribution point, you configure a reserved amount of disk space that is effectively blocked from the branch distribution point so that users logging onto the computer can still save files locally and the operating system can create local files as needed.  It’s easy to forget about this option after installation and when the branch distribution point has been running for some time.  When the reserved disk space value is reached, the branch distribution point will report zero disk space even though the hard disk is not full.

Branch distribution point disabled

 Q. Why is the option to enable the branch distribution point disabled?

Solution :

If Configuration Manager detects non-supported states for a selected site system, the option to enable the branch distribution point will be disabled.  These include:

• The Configuration Manager client is not installed and/or not assigned to the site.  These states must be reported back to the site, so check that the Client column displays Yes and the Assigned column displays Yes for the computer in the Collections node of the console.
• The computer is a workgroup client.
• The computer is running Windows 2000.
• The computer registered as configured with an Internet-based management point (see  Native Mode )

I’ve also heard reported that a conflicting record (duplicate GUID) can also prevent this option from being available, and another case where the option was not available until the Configuration Manager console was closed and reloaded.  Also, make sure that the client and site system components are healthy – check status messages and log files for errors,  and if necessary try uninstalling/reinstalling the client and site system.

Note: Although the branch distribution point requires a standard distribution to function correctly, the absence of a standard distribution does not prevent the branch distribution point from installing.

Regards,

Amarpal Singh Sandhu