SCCM - Distribution point - 2 x Distribution servers coming up on locationservices.log

Question

Hey,

I have this site (subnet and site) assigned to a local DP - no fallback, no references.

When I check the locationservices.log I see a few references to 2 x DP's: the local one (DP01) and the site server one (CM01).

Distribution Point='http://SRV-DP01.contoso.com/SMS_DP_SMSPKG$/c3xxxxxa09d', Locality='BOUNDARYGROUP', Version='9040', Capabilities='<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>', Signature='http://SRV-DP01.contoso.com/SMS_DP_SMSSIG$/cc3xxxxxa09d09d.1.tar', ForestTrust='TRUE', BlockInfo='0' LocationServices
Distribution Point='https://SRV-DP01.contoso.com/CCMTOKENAUTH_SMS_DP_SMSPKG$/c32xxxxx9d', Locality='BOUNDARYGROUP', Version='9040', Capabilities='<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/><Property Name="AuthMethod" Value="1024"/></Capabilities>', Signature='https://SRV-DP01.contoso.com/CCMTOKENAUTH_SMS_DP_SMSSIG$/ccc3xxxxxa09d09d1.tar', ForestTrust='TRUE', BlockInfo='0' LocationServices
Distribution Point='http://SRV-CM01.contoso.com/SMS_DP_SMSPKG$/c3xxxxxa09d', Locality='SITE', Version='9040', Capabilities='<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>', Signature='http://SRV-CM01-
CM01.contoso.com/SMS_DP_SMSSIG$/ccc3xxxxxa09d09d1.tar', ForestTrust='TRUE', BlockInfo='0' LocationServices 35012 (0x88C4)
Distribution Point='https://SRV-CM01.contoso.com/CCMTOKENAUTH_SMS_DP_SMSPKG$/c3xxxxxa09d', Locality='SITE', Version='9040', Capabilities='<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/><Property Name="AuthMethod" Value="1024"/></Capabilities>', Signature='https://SRV-CM01.contoso.com/CCMTOKENAUTH_SMS_DP_SMSSIG$/c3cc3xxxxxa09d09d.1.tar', ForestTrust='TRUE', BlockInfo='0' LocationServices

I cannot understand why the site server is showing up here?

Thanks Everyone :)

Answer 1

Without seeing all of your configuration, I can't say the exact configuration causing this, but content location is always a result of the client being mapped to a DP with the content via boundaries and boundary groups. Thus, in addition to being mapped to DP-01 based on the existing boundaries and boundary groups, it (based on the above log snippet) must also fall within the scope of a boundary and boundary group referencing the CM-01 as well.