Thank you An00p for your help. If the Site DP has no boundary protection, the package will download fron site DP to BDP share D\SMSPKGD$, then SCCM Client on the BDP workstation will get the package from this BDP share at D:\SMSPKGD$. But our site DP is boundary protected, if BDP's IP is not defined in the DP's protected boundary, where the package, under D:\SMSPKGD$, came from at the first place? BITS control policy, such as scheduled bandwidth configuration, can only be defined on primary site server, so we need to use protected boundaries on the site DP. Steven

Thank you An00p for your help. If the Site DP has no boundary protection, the package will download fron site DP to BDP share D\SMSPKGD$, then SCCM Client on the BDP workstation will get the package from this BDP share at D:\SMSPKGD$. But our site DP is boundary protected, if BDP's IP is not defined in the DP's protected boundary, where the package, under D:\SMSPKGD$, came from at the first place? BITS control policy, such as scheduled bandwidth configuration, can only be defined on primary site server, so we need to use protected boundaries on the site DP. Steven Hello - Don't make DP unprotected, just remove the BDP's IP from protected DP's boundary because BDP's IP is already part of protected boundary of BDP. Regarding the download of packages to SMSPKGD$ folder in BDP, I suppose there shouldn't be any problem. I think, you can test it for one of the BDP. If successfull then apply the same for others. Anoop C Nair - Twitter @anoopmannur MY BLOG: http://anoopmannur.wordpress.com SCCM Professionals This posting is provided AS-IS with no warranties/guarantees and confers no rights.

Primary Site server: SCCM2, IP is 172.20.x.x, It has a DP role. The DP protected boundary contains BDP's IP of each store only. We have to add BDP's IP 10.99.69.100 in DP's protected boundary. Each Store has PCs from 10.x.x.100 to 10.x.x.126. We want the package deliver once from DP to BDP for each store. Then all PCs in the store, including BDP workstation itself, should get the package from this BDP folder. So we assign a BDP role to one windows workstation for each store, such as 10.99.69.100. Then Add ip range 10.x.x.100 to 126 in BDP's protected boundary. So each PC in the store will only get packages from its BDP, not from site DP, nor from other BDPs. This is the reason the BDP IP is in both DP protected boundary and also in its BDP protected boundary. When BDP download the package into BDP folder D:\SMSPKGD$, the Client on BDP workstation should get the package from the BDP folder, not download again site DP. How to change Boundary to make the package deliver to BDP workstation only once? Steven

Am not sure, we need to add BDP's ip to standard DP's protected boundary. Becuase in your case, your BDP is part two protected boundary and it will always select standard DP rather than BDP if both protected DPs are available (Standard DP is BITs enabled). I would suggest you that try removing BDP's IP from procted Boundary of Standard DP and give a try?Anoop C Nair - 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.

If I remove BDP's IP from site DP's protected boundary, where the BDP can get packages from? Our DP has protected boundaries defined, All store PCs must get packages from their BDP, and never from site DP. Steven

Primary site server: SCCM2, site code:SC2 Site boundary: 10.99.69.100-10.99.69.100 and 10.99.69.100-10.99.69.126 for each store DP has protected boundaries: one for each BDP workstation. such as 10.99.69.100-10.99.69.100 BDP has its own protected boundary: 10.99.69.100-10.99.69.126 A testing package is targeted to all PCs in the store. The advertise is configured to not allow download package from fallback DP and unprotected DBs. The testing result from ContentTransferService.log shows: a) BDP workstation 10.99.69.100 download the package from its protected DP SCCM2 to BDPTmpWrkFldr folder, and then to BDP folder share D:\SMSPKGD$\SC100039. b) All PCs, other than BDP PC in the store, download the package from its protected BDP workstation. c) After one hour, the BDP workstation SCCM client downloads the same package from its protected DP SCCM2 again to C:\Windows\system32\CCM\cache\SC100039. Problem / Question: Is there any way to make BDP workstation download package once? Any help will be appreciate, Steven

Hi Steven, Is the application advertisment assigned to the BDP workstation? the D:\SMSPKGD$\ is the location the BDP uses to store its packages (The same as a standard DP) however the c:\windows\system32 location is where CCM clients (non DP's / Workstations etc.) store their packages after they have received the appropriate advertisment and provisioned the package from a DP source. I imagine this is why you would have the double up? Let us know how you go! :D

BDP should get the package from D:\SMSPKGD$ on the BDP. Yes I understand.Anoop C Nair - 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.

Primary site server: SCCM2, site code:SC2 Site boundary: 10.99.69.100-10.99.69.100 and 10.99.69.100-10.99.69.126 for each store DP has protected boundaries: one for each BDP workstation. such as 10.99.69.100-10.99.69.100 BDP has its own protected boundary: 10.99.69.100-10.99.69.126 Hello - What is the IP of SCCM2 server? and what is the IP of BDP machine? What I can see is 10.99.69.100 is in both the boundaries. if 10.99.69.100 is ur BDP workstation IP then that is causing you the issue. Please correct the boundaries so that you will get expected results. Anoop C Nair - 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.

An00p: your solution does not work. After remove BDP's IP from protected DP boundary, BDP can not download from site DP SC2. It start looking for unprotected DPs. Quan: You explained the problem but did not provide any solution. Your link to http://technet.microsoft.com/en-us/library/bb632366.aspx is an excellent article. When a client has two package source, it will pick BITS enabled DP (SCCM2) over SMB (BDP). But we did set 100.99.69.100 as a SLOW network, and 100.99.69.100-100.99.69.126 as a FAST network. So the FAST network should leading client download package from BDP. Today I found that there are no NTFS permissions assigned on problem folder inside all BDP folder share. Our package is a reoccurring package everyday. For some reason, BDPs delete old package folder, download contents to the new folder with the same name, but could not assign NTFS permissions. So no one can access the package in BDP folder share. The packaging status shows "Install Pending". It is the second time happened. When it was happened at the first time, I went to package, delete all DPs, then add site DP first, wait a hour, then add all other BDPs. What caused this problem? anyway to prevent it happen again? any hot fix for this? After fix this NTFS permission, we might see my original problem get resolve becaused I defined SLOW and FAST network boundaries.

An00p: your solution does not work. After remove BDP's IP from protected DP boundary, BDP can not download from site DP SC2. It start looking for unprotected DPs. Quan: You explained the problem but did not provide any solution. Your link to http://technet.microsoft.com/en-us/library/bb632366.aspx is an excellent article. When a client has two package source, it will pick BITS enabled DP (SCCM2) over SMB (BDP). But we did set 100.99.69.100 as a SLOW network, and 100.99.69.100-100.99.69.126 as a FAST network. So the FAST network should leading client download package from BDP. Today I found that there are no NTFS permissions assigned on problem folder inside all BDP folder share. Our package is a reoccurring package everyday. For some reason, BDPs delete old package folder, download contents to the new folder with the same name, but could not assign NTFS permissions. So no one can access the package in BDP folder share. The packaging status shows "Install Pending". It is the second time happened. When it was happened at the first time, I went to package, delete all DPs, then add site DP first, wait a hour, then add all other BDPs. What caused this problem? anyway to prevent it happen again? any hot fix for this? After fix this NTFS permission, we might see my original problem get resolve becaused I defined SLOW and FAST network boundaries.

Hi, I think we should not remove the BDP boundary away from the protected standard DP's boundaries. Because branch distribution point does not function entirely on its own and depends on a standard distribution point from which it receives its content. If the standard distribution point is configured as a protected site system, ensure that the protected boundaries of the standard site system include the branch distribution point. If the computer running the branch distribution point is excluded from the protected boundaries of the standard distribution point, it cannot install the packages that it needs. Have a look at the example in this technet document, it may helps: http://technet.microsoft.com/en-us/library/bb892788.aspx c) After one hour, the BDP workstation SCCM client downloads the same package from its protected DP SCCM2 again to C:\Windows\system32\CCM\cache\SC100039. When your BDP workstation SCCM client want to download the package, it will get the content locations from both standard and Branch DP because it's IP in the both DPs' protected boundaries. Then client will download package from standard DP, because BITS is the preferred choice but the SMB from BDP. I think this is not really a problem will block your job. Take the following documents as references: http://technet.microsoft.com/en-us/library/bb680853.aspx http://technet.microsoft.com/en-us/library/bb632366.aspx Thanks

Hi, I think we should not remove the BDP boundary away from the protected standard DP's boundaries. Because branch distribution point does not function entirely on its own and depends on a standard distribution point from which it receives its content. If the standard distribution point is configured as a protected site system, ensure that the protected boundaries of the standard site system include the branch distribution point. If the computer running the branch distribution point is excluded from the protected boundaries of the standard distribution point, it cannot install the packages that it needs. Have a look at the example in this technet document, it may helps: http://technet.microsoft.com/en-us/library/bb892788.aspx c) After one hour, the BDP workstation SCCM client downloads the same package from its protected DP SCCM2 again to C:\Windows\system32\CCM\cache\SC100039. When your BDP workstation SCCM client want to download the package, it will get the content locations from both standard and Branch DP because it's IP in the both DPs' protected boundaries. Then client will download package from standard DP, because BITS is the preferred choice but the SMB from BDP. I think this is not really a problem will block your job. Take the following documents as references: http://technet.microsoft.com/en-us/library/bb680853.aspx http://technet.microsoft.com/en-us/library/bb632366.aspx Thanks