Client did not get package from its protedcted BDP
Our new SCCM system has three servers: SCCM1, site code: SC1, Roles: Root site, Site DB, MP, RP, SLP, SUP. No site boundaries specified. SCCM2, Site code: SC2, Role: Primary site, Site DB, MP, SUP, FSP, DP Three testing site boundaries: One for corp fast LAN, Other two for slow WAN. BITS policy on Computer Client Agent of SCCM2: Apply to BDP only, 256Kbps (for testing) DP for Corp fast LAN. BDP1 and BDP2 are protected BDPs for their remote stores over slow WAN. SCCM3, Site system and Standard DP in Site SC2 for remote stores in slow WAN. BITS allowed on on Intranet only. Protected boundaries defined for each store. My testing store has two Winodws XPs with SP3 on 100MB Ethernet in a testing OU without any BITS AD policy. Client1 is defined as a protected BDP. Client2 is in the same boundary as the client1. I am expending Client1 will download package from DP on SCCM3. Client2 should download package from its protected BDP client1. I created three testing packages and deploied as the following: Test#1: During create a package, I selected the DP on SCCM3 only. Both clients, one is BDP, got the package from SCCM3 based on CAS.log The package is saved in BDP folder on Client1. Why client2 did not download the package from BDP on Client1? Test#2: Selected DP and all three BDPs. result is same as above. DP on SCCM3 is the first available source. Why client2 did not download the package from BDP on Client1? Test#3: Select three BDPs only. Package status is "Pending Install", Why? Thanks, Steven
March 18th, 2011 4:23pm

Hello - See, for more details Flowchart on selection of DPs http://technet.microsoft.com/en-us/library/bb932154.aspx http://technet.microsoft.com/en-us/library/bb632435.aspxAnoop 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.
Free Windows Admin Tool Kit Click here and download it now
March 18th, 2011 10:24pm

That issue is most likely caused by boundaries. How are the boundaries set up on each site? Which IP address and subnet masks have to clients got (if IP subnets are used for boundaries)? Please list all of them.Torsten Meringer | http://www.mssccmfaq.de
March 20th, 2011 5:51am

That issue is most likely caused by boundaries. How are the boundaries set up on each site? Which IP address and subnet masks have to clients got (if IP subnets are used for boundaries)? Please list all of them.Torsten Meringer | http://www.mssccmfaq.de
Free Windows Admin Tool Kit Click here and download it now
March 20th, 2011 5:51am

Boundaries: SC1 no boundary defined Bounday Site Conn Protected Desc 172.20.150.26-172.20.150.26 SC2 Fast MONSCCM3 172.20.150.138-172.20.150.139 SC2 Fast "MONSCCM3", "MONSCCMXP1" Test1 Store 10.99.12.0 SC2 Slow "MGRPC9912A", "MONSCCM3" Test2 Store BDP: MONSCCMXP1 (150.138), The three packages are created in local drive Client: MONSCCMXP2 (150.139), downloaded package from MONSCCM3.
March 21st, 2011 3:04pm

Boundaries: SC1 no boundary defined Bounday Site Conn Protected Desc 172.20.150.26-172.20.150.26 SC2 Fast MONSCCM3 172.20.150.138-172.20.150.139 SC2 Fast "MONSCCM3", "MONSCCMXP1" Test1 Store 10.99.12.0 SC2 Slow "MGRPC9912A", "MONSCCM3" Test2 Store BDP: MONSCCMXP1 (150.138), The three packages are created in local drive Client: MONSCCMXP2 (150.139), downloaded package from MONSCCM3. why?
Free Windows Admin Tool Kit Click here and download it now
March 21st, 2011 3:10pm

Boundaries: SC1 no boundary defined Bounday Site Conn Protected Desc 172.20.150.26-172.20.150.26 SC2 Fast MONSCCM3 172.20.150.138-172.20.150.139 SC2 Fast "MONSCCM3", "MONSCCMXP1" Test1 Store 10.99.12.0 SC2 Slow "MGRPC9912A", "MONSCCM3" Test2 Store BDP: MONSCCMXP1 (150.138), The three packages are created in local drive D:\SMSPKGD$ Client: MONSCCMXP2 (150.139), downloaded package from MONSCCM3. why?
March 21st, 2011 10:02pm

We finally figured out: 1) Define BDP (IP) and its local subnet (IP range or subnet) for each remote office in Site boundary. 2) Add only BDP in protected DB (BITS enabled). This will make sure DP send package to BDPs only. 3) Add the local subnet in Protected BDP boundary. This will make sure that clients get package from it BDP only.
Free Windows Admin Tool Kit Click here and download it now
May 2nd, 2011 1:27pm

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

Other recent topics Other recent topics