I'm maintaining an inherited SCCM 2007 SP2 system running on Server 2008 x86 consisting of one primary site, two standard DPs, and several more branch DPs. I followed http://technet.microsoft.com/en-us/library/bb632651.aspx to run through Branch DP creation for a new server and while the system shows up as healthy in SCCM's Site Status something is not right. I added the primary site server computer object to the local admin group of the new branch DP (which has the SCCM SP2 client) before starting, and have even tried using a domain admin account for installation purposes. Both times I have rebooted the primary site server a few hours after completion and the server shows up with over 100GB of free space but the built-in SCCM shares are not created and the IIS components are missing too. I've searched the logs on the primary site and while I find references to the new server, there are no associated errors listed. The event logs on the new DP server aren't helping either, any suggestions before calling MS? Thanks, D

Let's clarify here. You are having issues with install the BDP's? BDP's do not require the primary site server to be local admin, nor do they use IIS or the shares that a standard DP uses. They simply require a functioning client and an unprotected DP from which to get content. (I over simplied that a bit because unprotected is the easiest way) John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

Yes, I'm having the problem while attempting to setup a new Branch DP. The other branch DPs are working as expected, a test deployment just went to all BDPs except the new one. The standard DPs are protected but I have added the IP of the BDP as a boundary to both of the SDPs.

What do the logs say on the Branch DP? Branch DPs acquire content just like a normal client because they are a normal client. LocationServices.log, ContentTransferManager.log, and PeerDPAgent.log are good places to start. Here's a very good blog post from Steve (Rachui) also: http://blogs.msdn.com/b/steverac/archive/2007/10/26/branch-dp-internals-sccm-2007.aspx.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

The standard DPs are protected but I have added the IP of the BDP as a boundary to both of the SDPs. In this case I'll have to go deeper into my simple explanation above. You can use a protected DP as the source location for the BDP but this generally creates a unique problem. The BDP, as you already know, must be in the boundaries of the SDP. Seemigly the simple answer is to create a 1 IP address boundary which is the IP of the BDP. The problem with that is that 1 IP address is most often also in the boundaries of the subnet which the BDP will try to service. This means you end up with overlapping boundaries. (bad joo joo) The only way to avoid this and keep all SDP's protected is to make sure that 1 IP of the BDP is not in any other boundary. This often creates excessive administrative overhead. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

Hi, · Also, as you stated “I followedhttp://technet.microsoft.com/en-us/library/bb632651.aspx to run through Branch DP creation for a new server and while the system shows up as healthy in SCCM's Site Status something is not right.”, what is the detailed message or error? Regards, Sabrina This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |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.

Thanks for the replies John and Jason. I wasn't able to track down the root issue from last week but the branch DP is now working. The only thing that happened was powering down the virtual BDP server to move to a different storage array, when it came back up the test packages started transferring almost immediately. I'm not sure how that helped as I was rebooting the BDP before the site server last Wednesday and Thursday, but thankfully it kicked into gear.