Deploy new site system as 'branch distribution point' option greyed out.
I am trying to deploy a new distribution point from the site systems folder in the configuration manager console and set it up as a branch distribution point, but the option is always greyed out. The pc has the client installed and can be seen by config mgr. I can deploy software packages to it. Can anyone help me find the missing piece of the puzzel?
July 26th, 2008 12:57am

How to Deploy a Branch Distribution Point
Free Windows Admin Tool Kit Click here and download it now
July 26th, 2008 1:03am

I followed that, but the option is greyed out. The only option I have is to create a standard distribution point.Iseem to have missed something but cannot see it. According to the instructions all there are no special preq's other than the system has the 2007 client installed. On the Distribution Point page, select the Enable as a branch distribution point option. If you want to limit the branch distribution point installation and package files to a specific partition on the client computer or if you want to reserve a specific amount of disk space for the operating system or workstation files, you can set those preferences on this page.
July 26th, 2008 2:19am

What operating system is the client? Branch Distribution Points are not supported on Windows 2000 computers (or workgroup computers)
Free Windows Admin Tool Kit Click here and download it now
July 26th, 2008 9:15pm

One is a 2003 Server and the rest of the test are xp sp2 pc's and they are all part of the domain.
July 27th, 2008 6:00am

Is there at least one standard dp that is BITS enabledin the site already? This is a quote from another question here: "For a BDP to be fully functional, you must have a standard DP and that DP must be BITS-enabled. Remember, technically speaking, a BDP is a client that downloads packages via BTIS from a BITS-enabled standard DP, before it can serve other clients within the network-challenged location. Also please note, if your standard DP is protected, please be sure that your BDP is inside of that protected boundary. If your environment meets above BDP requirements and the package is still in pending state, check client logs for errors."
Free Windows Admin Tool Kit Click here and download it now
July 27th, 2008 1:09pm

You can install a branch distribution point without a standard distribution point being available it just wont work until you do. So it cant be this. I assume that the client is also assigned to the site, but is it displaying Yes in the Client column, and Yes in the Assigned column? Although a computer might be a client and might be successfully assigned, this information needs to be sent back to Configuration Manager so it could be a timing issue if youre using a test setup with newly installed clients. If the branch distribution point option is still not available, try uninstalling and reinstalling the client verifying that the client status in the console updates for both steps. Two other reasons Ive heard of that resolved this issue: Conflicting record (duplicate GUID). Make sure this client isnt displayed as a conflicting record in the Conflicting Records node (although the default is to automatically resolve). Exit and reload the Configuration Manager console. Im not sure what was going on here, whether a timing issue or something else, but a customer reported that this resolved his issue so Im passing it along. - Carol This posting is provided AS IS with no warranties and confers no rights.
July 27th, 2008 6:35pm

When you say bits enable, do you mean in the site system folder under configmgr distribution point properties. I have checked 'enable as a standard distribution point" and under comm setting both ';allow clients to transfer from this DP using bits, http, and https' allow clients to connect anonymously'
Free Windows Admin Tool Kit Click here and download it now
July 29th, 2008 7:19pm

Is there a way that I can check this in configuration manager? I currently only have the one site installed. I can deliver packages to the clients. There are no record in the conflictin records.
July 29th, 2008 7:24pm

Make sure that you advance client is installed on the machine that you are trying to make a BDP. This should fix it.
Free Windows Admin Tool Kit Click here and download it now
November 12th, 2008 4:10pm

I had the same issue with one of my installs. The problem for me was entered the FQDN in properly but I entered the Server name wrong. After I went back and corrected this error I was given the BDP option.
February 4th, 2010 8:00pm

I, too, am having the same issue. Site server is bits-enabled distribution point. The target XP machine has the CM client installed, the Client is seen in All Systems collection as having the client installed and being a member of the site, the client is joined to the domain (single forest, single domain). No matter how long I wait, or how many time I reboot all systems, the BDP option is never available in the Distribution Point configuration page.I have checked and re-checked the FQDNs I am using, all show up in nslookup and ping.The CM GUID is unique, I have no conflicting records.Anyone have any other suggestions than those listed above?
Free Windows Admin Tool Kit Click here and download it now
February 19th, 2010 6:57pm

One other possible scenario I know is if the client is configured for Internet-based client management by using the CCMHOSTNAME client installation property. Let me know if this is applicable, and I'll provide more information.
February 22nd, 2010 5:20pm

The client is *not* configured for Internet-based client management.Hope this clarifies things.
Free Windows Admin Tool Kit Click here and download it now
February 24th, 2010 10:05pm

I have corrected the problem. I misunderstood what values could reside in the Name field (example Server1). I now understand that it must be the computername of the machine being added, not just any name. Once this was understood, everything else fell into place.
February 27th, 2010 2:02am

To help other customers, I'm marking your update as Propose As Answer - please confirm it. One of the earlier responses (Jeff's) was that a branch distribution point can't be a workgroup computer. I suspect Configuration Manager uses the value in the Name field to check this requirement, so if it doesn't get a positive response (which it won't if the site system name isn't correct) then it thinks that the site system isn't joined to the domain (ie a workgroup computer) - and disables the branch distribution point option. I'll add this condition to the troubleshooting documentation, to help other customers.I've seen this feedback before, that the "Name" field in the UI doesn't make it obvious that it must be the actual computer name rather than a display name - and I agree. It is in the documentation (, but if you think that it's a display name then there's no reason to check the documentation. Unfortunately, we can't change the UI for this version of Configuration Manager, but I will recommend to the product group that it's made more obvious in new versions.
Free Windows Admin Tool Kit Click here and download it now
March 7th, 2010 6:22pm

I am facing the problem in making Branch Distribution point. Enable Branch Distribution poin is grayed out. 1) Client is domain joined. 2) windows 7 OS 3) Agent is installed 4) Client is not internet based client need urgent answer
November 26th, 2010 8:35am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics