Why are some clients being assigned wrong DP?

Overview

SCCM 2012 SP1, One Site, One MP, ~80 DP's
GLCM001  - Site Server, MP, DP in data centre
UKASHI001 - DP in branch office
UKGLAS001 - DP in branch office
One to one mapping between AD Site (or IP Range), Boundary group and DP. No Fallback DP's. No distributing content to preferred DP's.

I've been experiencing some issues with content being pulled by the end client from GLCM001 instead of the DP within the defined Boundary.

We run our domain from two data centres with ~80 branch offices.  In one of the data centres I have my SCCM Server (GLCM001  - Site Server, MP, DP etc), in each of the branch offices I have a DP.
I'm aware that boundary overlapping is the most common cause for this issue, I looked at the defined boundaries but couldn't see an overlap, and I haven't come across any log to prove otherwise. Normally I just use AD sites to map boundaries but for troubleshooting purposes I changed the boundaries of the sites I was using for testing to be IP address ranges, which made no difference.

My problem is appearing in some branch offices, but not all, and all clients within a branch office react the same.

I ran two tests
The first was to check that if the content was only on GLCM001, clients not within it's boundary didn't download content from it.  This worked as expected, the two test clients didn't download content.

On the second test, when the content is not on GLCM001, but on the DP's near the client, UKGLAS065 gets it content from the GLCM001 DP

Any ideas why?

Test 2 - Content only on DP's UKASHI001 and UKGLAS001

Client:
UKASHI013

Client LocationServices.log: 
Current AD site of machine is Ashington LocationServices 04/02/2014 11:32:51 884 (0x0374)
Calling back with the following distribution points LocationServices 04/02/2014 11:32:51 884 (0x0374)
Distribution Point='http://UKASHI001.domain.local/SMS_DP_SMSPKG$/PR100087', Locality='LOCAL', DPType='SERVER', Version='7804', Capabilities='<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>', Signature='http://UKASHI001.domain.local/SMS_DP_SMSSIG$/PR100087', ForestTrust='TRUE', LocationServices 04/02/2014 11:32:51 884 (0x0374)
Calling back with locations for location request {99F6E76F-4D7D-4946-9A88-33B7503789BD} LocationServices 04/02/2014 11:32:52 884 (0x0374)

Server MP_location.log:
MP_GetContentDPInfoProtected (PR100087,1,PR1,<ServerNameList><ServerName>UKASHI001.domain.local</ServerName></ServerNameList>,SMSPackage,00000000,domain.local,domain.local,<ClientLocationInfo LocationType="SMSPackage" DistributeOnDemand="0" UseAzure="0" AllowWUMU="0" UseProtected="1" AllowCaching="0" BranchDPFlags="0" UseInternetDP="0" AllowHTTP="1" AllowSMB="1" AllowMulticast="1"><ADSite Name="ASHINGTON"/><Forest Name="domain.local"/><Domain Name="domain.local"/><IPAddresses><IPAddress SubnetAddress="192.168.240.0" Address="192.168.240.69"/></IPAddresses></ClientLocationInfo>)

Client:
UKGLAS065

Client LocationServices.log: 
Current AD site of machine is Glasgow LocationServices 04/02/2014 11:51:54 4588 (0x11EC)
Calling back with the following distribution points LocationServices 04/02/2014 11:51:54 4588 (0x11EC)
Distribution Point='http://GLCM001.domain.local/SMS_DP_SMSPKG$/PR100087', Locality='LOCAL', DPType='SERVER', Version='7804', Capabilities='<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>', Signature='http://GLCM001.domain.local/SMS_DP_SMSSIG$/PR100087', ForestTrust='TRUE', LocationServices 04/02/2014 11:51:54 4588 (0x11EC)
Calling back with locations for location request {04144A8E-D780-42DE-8FEE-80EFACA4943F} LocationServices 04/02/2014 11:51:54 4588 (0x11EC)

Server MP_location.log:
MP_GetContentDPInfoProtected (PR100087,1,PR1,<ServerNameList><ServerName>UKGLAS001.domain.local</ServerName></ServerNameList>,SMSPackage,00000000,domain.local,domain.local,<ClientLocationInfo LocationType="SMSPackage" DistributeOnDemand="0" UseAzure="0" AllowWUMU="0" UseProtected="1" AllowCaching="0" BranchDPFlags="0" UseInternetDP="0" AllowHTTP="1" AllowSMB="1" AllowMulticast="1"><ADSite Name="GLASGOW"/><Forest Name="domain.local"/><Domain Name="domain.local"/><IPAddresses><IPAddress SubnetAddress="192.168.146.0" Address="192.168.146.81"/></IPAddresses></ClientLocationInfo>)



  • Edited by idarryl Tuesday, February 04, 2014 4:01 PM typo
February 4th, 2014 6:45pm

Hi,

So the content didn't show up under GLCM001 DP before or after UKGLAS065 download the content?

Best Regards,

Joyce Li

Free Windows Admin Tool Kit Click here and download it now
February 5th, 2014 1:26pm

The content had been removed from GLCM001 for the second test, and was only available on UKASHI001 and UKGLAS001 before UKGLAS056 downloaded the content 
February 5th, 2014 1:45pm

How is you site assignment boundary group configured? have you added GLCM001 under site servers in site assignment boundary group?

If the answer is yes to the second question this is expected.

Free Windows Admin Tool Kit Click here and download it now
February 5th, 2014 6:33pm

Hi Delphin.  Not entirely sure where/what you mean, but if I understand you correctly.  I have each office assigned to it's own AD site boundary assigned to it's own DP in the office.


Ashington office - Ashington Site - UKASHI001
Glasgow Office - Glasgow Site - 
UKGLAS001
Data Centre - Data Center AD Site - 
GLCM001

February 5th, 2014 7:29pm

idarryl, there two type of boundary group you must configure.

1. ConfigMgr site assignment boundary group

2. ConfigMgr content location boundary group

http://technet.microsoft.com/en-us/library/gg712679.aspx#BKMK_BoundarySiteAssignment

Now, How are your boundary groups configured?

Create a single boundary groups for site assignment, Do not add any site server under content location (or mark it as slow) in site assignment boundary group properties.

Configure separate boundary group for each branch office and add your local dp as content server on the boundary group properties.

Free Windows Admin Tool Kit Click here and download it now
February 5th, 2014 9:36pm

Hi Delphin,

thank you for your clarification.  

In my previous post I was referring to content location boundary groups.  

I do not currently have a site assignment boundary group.  As I only one run site, I thought if was enough to 'manually' assign the site code using the Client Push Installation Properties using the 'SMSSITECODE=PR1' property.  All my clients also have the Agent Site value as PR1.  Is this not enough?

February 6th, 2014 12:29pm

That should be fine for now. But in the future you may run across a scenario where the clients failing to reports to your site for various reasons.

But still you've not answered my question about how the boundaries and boundary group for branch Glasgow are configured? Ad site, Ip subnet etc..

Does the client mentioned in this post have multiple ip address registered ?

How is the collection membership rule configured? Ad site, Ip subnet, OU etc

Free Windows Admin Tool Kit Click here and download it now
February 7th, 2014 7:16am

Hi, sorry for the delayed reply.

I thought I would give you a quick update. I involved Microsoft as the problem was getting urgent.  They've been through SCCM and the setup is fine.  They noted that the client receives an empty DP list from the MP when there is no content on the DP within it's boundary group, and a DP list containing only the DP that is also the MP when there is content on the DP within it's boundary group.

To answer your questions:
Content boundaries were AD sites, but were moved to IP ranges for testing.

The client(s) don't have multiple IP addresses

Collection membership is direct (for testing)

February 17th, 2014 4:23am

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

Other recent topics Other recent topics