I have Boundary for Leduc (canada) set up ussing Active Directory site ,  and i just deploy a guy over there a big file software application (like 1gb).

The local Distribution Point have the application distributed just fine, but its taking long time for downloading it,  my question born because the computer from him its in a different OU (in an IT Test OU)  and not in LEDUC.

How the boundary work for him? where its he downloading the file from? its taking too much time i think like if he its downloading it from another place,  where its the log file to check that?

If you like you said the boundarie as been created using the active directory site and service the location of the computer inside active directory doesn't change anything.

Active directory site are base on subnet configure in site and services.

To see the location where he is getting the file look at that file on the client computer:DataTransferService.log

Also look at this log file on the client:LocationServices.log

this will tell you what AD site the computer is in

• Edited by Frederick Dicaire 15 hours 30 minutes ago

Which one is it? the DP over there its named LEDFP05,   the only name i see its IDCSCCM01 which its my Primary site.

DTSJob {D7F471C0-BAAE-42FC-97AA-2BED1C79CB17} in state 'DownloadingData'. DataTransferService 30/07/2015 10:07:33 a.m. 8552 (0x2168)
UpdateURLWithTransportSettings(): OLD URL - http://IDCSCCM01.rbi.local/SMS_MP DataTransferService 30/07/2015 10:07:41 a.m. 8548 (0x2164)
UpdateURLWithTransportSettings(): NEW URL - http://IDCSCCM01.rbi.local:80/SMS_MP DataTransferService 30/07/2015 10:07:41 a.m. 8548 (0x2164)
Added (source=.sms_dcm?Id&DocumentId=ScopeId_D87622B9-C4DF-4379-BECC-B4BCEEFFABBB/Application_c9b79980-1296-4ad6-afb9-b32889a65a45/2/MANIFEST&Hash=7C929231292974C7D758F6842FAA3B83EE64475BDAACCF1E1C6A3EEA0EFD7AEE&Compression=zlib,dest={2F453C93-9176-4157-8FED-1F7CABBC6C30}_1.zip) pair from manifest. DataTransferService 30/07/2015 10:07:41 a.m. 8548 (0x2164)
Added (source=.sms_dcm?Id&DocumentId=ScopeId_D87622B9-C4DF-4379-BECC-B4BCEEFFABBB/Application_c9b79980-1296-4ad6-afb9-b32889a65a45/2/PROPERTIES&Hash=0D28EB4BC224031A178BD96A3F9B54CB4D4AAA43A8EC32F0310BB37EF8421EA0&Compression=zlib,dest={2F453C93-9176-4157-8FED-1F7CABBC6C30}_2.zip) pair from manifest. DataTransferService 30/07/2015 10:07:41 a.m. 8548 (0x2164)
Added (source=.sms_dcm?Id&DocumentId=ScopeId_D87622B9-C4DF-4379-BECC-B4BCEEFFABBB/DeploymentType_efb5d4e1-5f1c-4406-abbc-8d8e40d5b133/2/MANIFEST&Hash=2510E3C502BCDDF9C464A6376223E93C5A1788476E4580B4F5DDD95A83C96678&Compression=zlib,dest={20A8968A-881B-46EB-9C07-DDD10009B8F7}_1.zip) pair from manifest. DataTransferService 30/07/2015 10:07:41 a.m. 8548 (0x2164)
Added (source=.sms_dcm?Id&DocumentId=ScopeId_D87622B9-C4DF-4379-BECC-B4BCEEFFABBB/DeploymentType_efb5d4e1-5f1c-4406-abbc-8d8e40d5b133/2/PROPERTIES&Hash=80F053CAD967A0B58BEF492FCAFCCB358ED4BDE5B0F5D162B1561C6D53438C8E&Compression=zlib,dest={20A8968A-881B-46EB-9C07-DDD10009B8F7}_2.zip) pair from manifest. DataTransferService 30/07/2015 10:07:41 a.m. 8548 (0x2164)
Added (source=.sms_dcm?Id&DocumentId=ScopeId_D87622B9-C4DF-4379-BECC-B4BCEEFFABBB/RequiredApplication_c9b79980-1296-4ad6-afb9-b32889a65a45/2/MANIFEST&Hash=D03D2597FDCBF476F144E1DF3803EFBE251B34033D01A15358B0D370E7334598&Compression=zlib,dest={71429BDE-5A69-48D8-BE38-57824BD60C26}_1.zip) pair from manifest. DataTransferService 30/07/2015 10:07:41 a.m. 8548 (0x2164)
Added (source=.sms_dcm?Id&DocumentId=ScopeId_D87622B9-C4DF-4379-BECC-B4BCEEFFABBB/RequiredApplication_c9b79980-1296-4ad6-afb9-b32889a65a45/2/PROPERTIES&Hash=CF84E58BE1453310323B591D2704E2B3A842041D9DCE9CF6F9EF7AA3FA768AF7&Compression=zlib,dest={71429BDE-5A69-48D8-BE38-57824BD60C26}_2.zip) pair from manifest. DataTransferService 30/07/2015 10:07:41 a.m. 8548 (0x2164)
DTSJob {802B0BDC-8736-4C3F-94FD-3074CA9D4DFB} created to download from 'http://IDCSCCM01.rbi.local:80/SMS_MP' to 'C:\WINDOWS\CCM\CIDownloader\Staging'. DataTransferService 30/07/2015 10:07:41 a.m. 8548 (0x2164)
DTSJob {802B0BDC-8736-4C3F-94FD-3074CA9D4DFB} in state 'PendingDownload'. DataTransferService 30/07/2015 10:07:41 a.m. 8552 (0x2168)
DTSFlag is 0x00009c8a DataTransferService 30/07/2015 10:07:41 a.m. 8552 (0x2168)
Exclude file list: DataTransferService 30/07/2015 10:07:41 a.m. 8552 (0x2168)
Using branch cache option DataTransferService 30/07/2015 10:07:41 a.m. 8552 (0x2168)
DTSJob {802B0BDC-8736-4C3F-94FD-3074CA9D4DFB} in state 'DownloadingData'. DataTransferService 30/07/2015 10:07:42 a.m. 8552 (0x2168)
DTSJob {D7F471C0-BAAE-42FC-97AA-2BED1C79CB17} in state 'RetrievedData'. DataTransferService 30/07/2015 10:12:31 a.m. 1976 (0x07B8)
DTSJob {D7F471C0-BAAE-42FC-97AA-2BED1C79CB17} successfully completed download. DataTransferService 30/07/2015 10:12:31 a.m. 1976 (0x07B8)
DTSJob {D7F471C0-BAAE-42FC-97AA-2BED1C79CB17} in state 'NotifiedComplete'. DataTransferService 30/07/2015 10:12:31 a.m. 5188 (0x1444)
DTS job {D7F471C0-BAAE-42FC-97AA-2BED1C79CB17} has completed:
Status : SUCCESS,
Start time : 07/30/2015 10:07:32,
Completion time : 07/30/2015 10:12:31,
Elapsed time : 298 seconds DataTransferService 30/07/2015 10:12:31 a.m. 5188 (0x1444)
UpdateURLWithTransportSettings(): OLD URL - http://IDCSCCM01.rbi.local/SMS_MP DataTransferService 30/07/2015 10:12:31 a.m. 6852 (0x1AC4)
UpdateURLWithTransportSettings(): NEW URL - http://IDCSCCM01.rbi.local:80/SMS_MP DataTransferService 30/07/2015 10:12:31 a.m. 6852 (0x1AC4)
Added (source=.sms_dcm?Id&DocumentId=ScopeId_D87622B9-C4DF-4379-BECC-B4BCEEFFABBB/Application_c9b79980-1296-4ad6-afb9-b32889a65a45/2/MANIFEST&Hash=7C929231292974C7D758F6842FAA3B83EE64475BDAACCF1E1C6A3EEA0EFD7AEE&Compression=zlib,dest={AF1C811F-8238-4F51-9575-6DA5B23A5E22}_1.zip) pair from manifest. DataTransferService 30/07/2015 10:12:31 a.m. 6852 (0x1AC4)
Added (source=.sms_dcm?Id&DocumentId=ScopeId_D87622B9-C4DF-4379-BECC-B4BCEEFFABBB/Application_c9b79980-1296-4ad6-afb9-b32889a65a45/2/PROPERTIES&Hash=0D28EB4BC224031A178BD96A3F9B54CB4D4AAA43A8EC32F0310BB37EF8421EA0&Compression=zlib,dest={AF1C811F-8238-4F51-9575-6DA5B23A5E22}_2.zip) pair from manifest. DataTransferService 30/07/2015 10:12:31 a.m. 6852 (0x1AC4)
Added (source=.sms_dcm?Id&DocumentId=urn:policy-platform:policy.microsoft.com:smlif:ms.dcm.ScopeId_D87622B9-C4DF-4379-BECC-B4BCEEFFABBB.RequiredApplication_c9b79980-1296-4ad6-afb9-b32889a65a45:2&Hash=B08A26796E33A32D6A3C9FB489F87F0D80C45FC7AEF00FDEF1D573537719853A&Compression=zlib,dest={21379E3D-4C26-4DF0-AA41-724B3E1314F7}_Model_VS.zip) pair from manifest. DataTransferService 30/07/2015 10:12:31 a.m. 6852 (0x1AC4)
DTSJob {79E2B771-FE7B-4A86-A72A-BFAF759F90BB} created to download from 'http://IDCSCCM01.rbi.local:80/SMS_MP' to 'C:\WINDOWS\CCM\CIDownloader\Staging'. DataTransferService 30/07/2015 10:12:31 a.m. 6852 (0x1AC4)
DTSJob {79E2B771-FE7B-4A86-A72A-BFAF759F90BB} in state 'PendingDownload'. DataTransferService 30/07/2015 10:12:31 a.m. 8936 (0x22E8)
DTSFlag is 0x00009c8a DataTransferService 30/07/2015 10:12:32 a.m. 8548 (0x2164)
Exclude file list: DataTransferService 30/07/2015 10:12:32 a.m. 8548 (0x2164)
Using branch cache option DataTransferService 30/07/2015 10:12:32 a.m. 8548 (0x2164)
DTSJob {79E2B771-FE7B-4A86-A72A-BFAF759F90BB} in state 'DownloadingData'. DataTransferService 30/07/2015 10:12:34 a.m. 8548 (0x2164)

Did you look at the second log file i posted to see what AD site the client hes being listed in.

You sure you also don't have overlapping boundary like 1 with the site that point to DP a and one with a IP range that point to DP B?

I have Boundary for Leduc (canada) set up ussing Active Directory site ,  and i just deploy a guy over there a big file software application (like 1gb).

The local Distribution Point have the application distributed just fine, but its taking long time for downloading it,  my question born because the computer from him its in a different OU (in an IT Test OU)  and not in LEDUC.

There's a difference between AD site and AD OU! OU does not come into play herer. 

Im maybe confused how the boundary its picking him up, I was first trying to explain you that The boundary its setup using Active Directory site. 

And i mention his computer its in an Active directory level not inside Leduc OU,  he its in united states (but he live in Leduc and work in Leduc network).  So if this information its irrelevant, please omit it.

The log I post up here, its the one you told me to look, let me see if there not Overlappin boundary, but in the log should LEDFP05 (the local DP IN leduc Canda) Should be mentioned?  I only see IDCSCCM01 whic its my primary site, also a DP

I also said to look at this log :LocationServices.log

This will list if the computer is in the active directory site leduc.

The way the active directory site work like i explain in my previous post is base on SUBNET (IP address) and not OU or location in the active directory.

SO if the guy is in a subnet that is not configure or part of the leduc active directory site than normal he would not fit in the boundary you configure.

• Edited by Frederick Dicaire 15 hours 20 minutes ago

Here its the log

Distribution Point='http://IDCSCCM01.rbi.local/SMS_DP_SMSPKG$/Content_f317751d-083d-42e6-a0b0-1326da7eb615.1', Locality='LOCAL', DPType='SERVER', Version='7958', Capabilities='<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>', Signature='http://IDCSCCM01.rbi.local/SMS_DP_SMSSIG$/Content_f317751d-083d-42e6-a0b0-1326da7eb615.1.tar', ForestTrust='TRUE', LocationServices 30/07/2015 09:08:34 a.m. 5072 (0x13D0)
Calling back with locations for location request {82A3942F-C01B-4F0C-8866-04D13B619DC0} LocationServices 30/07/2015 09:08:34 a.m. 5072 (0x13D0)
Executing Task LSRefreshLocationsTask LocationServices 30/07/2015 09:10:28 a.m. 8364 (0x20AC)
Current AD site of machine is Leduc LocationServices 30/07/2015 09:10:28 a.m. 8364 (0x20AC)
Current AD site of machine is Leduc LocationServices 30/07/2015 09:10:28 a.m. 8844 (0x228C)
Calling back with the following distribution points LocationServices 30/07/2015 09:10:28 a.m. 8844 (0x228C)
Distribution Point='http://IDCSCCM01.rbi.local/SMS_DP_SMSPKG$/Content_f317751d-083d-42e6-a0b0-1326da7eb615.1', Locality='LOCAL', DPType='SERVER', Version='7958', Capabilities='<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>', Signature='http://IDCSCCM01.rbi.local/SMS_DP_SMSSIG$/Content_f317751d-083d-42e6-a0b0-1326da7eb615.1.tar', ForestTrust='TRUE', LocationServices 30/07/2015 09:10:28 a.m. 8844 (0x228C)
Calling back with locations for location request {82A3942F-C01B-4F0C-8866-04D13B619DC0} LocationServices 30/07/2015 09:10:28 a.m. 8844 (0x228C)
Executing Task LSSiteRoleCycleTask LocationServices 30/07/2015 10:00:50 a.m. 8548 (0x2164)
1 assigned MP errors in the last 10 minutes, threshold is 5. LocationServices 30/07/2015 10:00:50 a.m. 8548 (0x2164)
Executing Task LSMPCommSuccessTask LocationServices 30/07/2015 10:07:28 a.m. 1600 (0x0640)
Reset assigned MP error count LocationServices 30/07/2015 10:07:28 a.m. 1600 (0x0640)
Executing Task LSRefreshLocationsTask LocationServices 30/07/2015 10:10:28 a.m. 7992 (0x1F38)
Current AD site of machine is Leduc LocationServices 30/07/2015 10:10:28 a.m. 7992 (0x1F38)
Current AD site of machine is Leduc LocationServices 30/07/2015 10:10:28 a.m. 3172 (0x0C64)
Calling back with the following distribution points LocationServices 30/07/2015 10:10:28 a.m. 3172 (0x0C64)
Distribution Point='http://IDCSCCM01.rbi.local/SMS_DP_SMSPKG$/Content_f317751d-083d-42e6-a0b0-1326da7eb615.1', Locality='LOCAL', DPType='SERVER', Version='7958', Capabilities='<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>', Signature='http://IDCSCCM01.rbi.local/SMS_DP_SMSSIG$/Content_f317751d-083d-42e6-a0b0-1326da7eb615.1.tar', ForestTrust='TRUE', LocationServices 30/07/2015 10:10:28 a.m. 3172 (0x0C64)
Calling back with locations for location request {82A3942F-C01B-4F0C-8866-04D13B619DC0} LocationServices 30/07/2015 10:10:28 a.m. 3172 (0x0C64)
Current AD site of machine is Leduc LocationServices 30/07/2015 10:25:44 a.m. 8776 (0x2248)
Created and Sent Location Request '{CFF396C9-EDF5-4DC1-BAA1-62ABC07BDB8B}' for package {D87622B9-C4DF-4379-BECC-B4BCEEFFABBB} LocationServices 30/07/2015 10:25:44 a.m. 8776 (0x2248)
Calling back with the following WSUS locations LocationServices 30/07/2015 10:25:44 a.m. 8776 (0x2248)
WSUS Path='http://IDCSCCM01.rbi.local:8530', Server='IDCSCCM01.RBI.LOCAL', Version='617' LocationServices 30/07/2015 10:25:44 a.m. 8776 (0x2248)
Calling back with locations for WSUS request {CFF396C9-EDF5-4DC1-BAA1-62ABC07BDB8B} LocationServices 30/07/2015 10:25:44 a.m. 8776 (0x2248)

You can cleary see that the DP configure for this user is:Distribution Point='http://IDCSCCM01.rbi.local/SMS_DP_SMSPKG$/Content_f317751d-083d-42e6-a0b0-1326da7eb615.1', Locality='LOCAL', DPType='SERVER', Version='7958', Capabilities='<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>', Signature='http://IDCSCCM01.rbi.local/SMS_DP_SMSSIG$/Content_f317751d-083d-42e6-a0b0-1326da7eb615.1.tar', ForestTrust='TRUE',

So i would look at the boundaries again.

I would open all the boundary group that IDCSCCM01 belongs to and look at the boundaries configure.

• Proposed as answer by Joyce LMicrosoft contingent staff, Moderator 2 hours 7 minutes ago

Just to reiterate, AD sites and AD OUs, even if they are named the same thing, have nothing to do with each other at all. The AD OU a computer object is in makes no difference whatsoever. The only thing that matters is what AD Site that the computer itself determines that it is in and this is completely based upon the subnets assigned to that site in AD.

In the Boundary Groups for LED, In general the boundary says LEDUC

Inside references i found 2 Site Systems

IDCSCCM01  connection FAST
LEDFP05      connectiong FAST

What i can also see , its that many of my boundary groups are setup like that, not just this one,  is this why? By the way, i didnt set up this, it was from previous guy.

Well this mean the all the client in the boundary LEDUC receive 2 distributions point. SO this is why the user is grabing the package from IDCSCCM01. If you want to make 100% sure they always grab the content from LEDFP05 juste remove IDCSCCM01  from the content server.

You could also go to Administration Distribution Points select the IDCSCCM01 and go to the boudary groups tab and remove the groups from there.

• Edited by Frederick Dicaire 14 hours 11 minutes ago

Is there an order for that?  if i put Leduc first it will grab it from there first? IDCSCCM its on the top.

(I will remove it i was just wondering).

For example what will happen for PXE deployments there? If the package its not local, it will go anyway to IDCSCCM01 to look it for? I guess this is why its setup like this.

No order they will pick one from the list.

If you want computer to always go yo LEDFp05 and if it doesn't have the content you need to look at things like Allow fallback source location for content:

Good article here:http://blogs.technet.com/b/neilp/archive/2013/01/03/on-demand-content-distribution-fallback-distribution-points-a-2012-configuration-manager-micro-depp-dive.aspx

But honestly if you do PXE from that location why not send all the package require for it and avoid people going to the main office (since you said the connection is slow).

This would be the best option make sure your DP are all set up properly with the content the users need.

• Edited by Frederick Dicaire 14 hours 5 minutes ago
• Proposed as answer by Joyce LMicrosoft contingent staff, Moderator 2 hours 7 minutes ago

Thank you very much Frederick for all the time spent here.

Thank you very much Frederick for all the time spent here.

Was my pleasure. Any chance you can mark the question as answer if the info provided was to your liking :)

PS: People from Quebec need to help each other:)

Of course! I already mark a couple.

If you like you said the boundarie as been created using the active directory site and service the location of the computer inside active directory doesn't change anything.

Active directory site are base on subnet configure in site and services.

To see the location where he is getting the file look at that file on the client computer:DataTransferService.log

Also look at this log file on the client:LocationServices.log

this will tell you what AD site the computer is in

• Edited by Frederick Dicaire Thursday, July 30, 2015 4:21 PM

I also said to look at this log :LocationServices.log

This will list if the computer is in the active directory site leduc.

The way the active directory site work like i explain in my previous post is base on SUBNET (IP address) and not OU or location in the active directory.

SO if the guy is in a subnet that is not configure or part of the leduc active directory site than normal he would not fit in the boundary you configure.

• Edited by Frederick Dicaire Thursday, July 30, 2015 4:31 PM

You can cleary see that the DP configure for this user is:Distribution Point='http://IDCSCCM01.rbi.local/SMS_DP_SMSPKG$/Content_f317751d-083d-42e6-a0b0-1326da7eb615.1', Locality='LOCAL', DPType='SERVER', Version='7958', Capabilities='<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>', Signature='http://IDCSCCM01.rbi.local/SMS_DP_SMSSIG$/Content_f317751d-083d-42e6-a0b0-1326da7eb615.1.tar', ForestTrust='TRUE',

So i would look at the boundaries again.

I would open all the boundary group that IDCSCCM01 belongs to and look at the boundaries configure.

• Proposed as answer by Joyce LMicrosoft contingent staff, Moderator Friday, July 31, 2015 5:44 AM

Well this mean the all the client in the boundary LEDUC receive 2 distributions point. SO this is why the user is grabing the package from IDCSCCM01. If you want to make 100% sure they always grab the content from LEDFP05 juste remove IDCSCCM01  from the content server.

You could also go to Administration Distribution Points select the IDCSCCM01 and go to the boudary groups tab and remove the groups from there.

• Edited by Frederick Dicaire Thursday, July 30, 2015 5:40 PM

No order they will pick one from the list.

If you want computer to always go yo LEDFp05 and if it doesn't have the content you need to look at things like Allow fallback source location for content:

Good article here:http://blogs.technet.com/b/neilp/archive/2013/01/03/on-demand-content-distribution-fallback-distribution-points-a-2012-configuration-manager-micro-depp-dive.aspx

But honestly if you do PXE from that location why not send all the package require for it and avoid people going to the main office (since you said the connection is slow).

This would be the best option make sure your DP are all set up properly with the content the users need.

• Edited by Frederick Dicaire Thursday, July 30, 2015 5:46 PM
• Proposed as answer by Joyce LMicrosoft contingent staff, Moderator Friday, July 31, 2015 5:44 AM