none
SCCM Client push using remote DPs

    Question

  • I have one Primary site/MP server with 38 DPs at remote locations.  The default config manager package has been successfully distributed to all the DPs.  All DPs have configured successfully at 100%.  I have all my boundaries (using IP subnets), and boundary groups setup.  But, when I use the client push wizard to push to an individual computer (still in testing phase) it is not using the local DP to download  and install the client. It uses the primary site server.  The client will install successfully without error.  But, I would like the client to download and install from the local DP. I've verified the device I'm trying to push to is within the proper boundary, and the local DP has been added as a content location on the corresponding boundary group.  According to the log it finds the remote location, but can't find any local DPs. 

    The following is an excerpt from ccmsetup.log:

    ====================================================

    026EC8ECD36EAD6EAF3B5D35663F8201BDE175413C" MinimumClientVersion="5.00.7804.1000" RandomizeMaxDays="7" ProgramEnabled="false" LastModifiedTime="30302483;1187404032" SiteVersionMatch="true"

    SiteVersion="5.00.7804.1000" EnablePeerCache="true"/></ContentLocationReply>' ccmsetup 7/17/2013 12:42:27 PM 1068 (0x042C)
    Found remote location 'http://SUS.acme.dom/SMS_DP_SMSPKG$/PDO00002' ccmsetup 7/17/2013 12:42:27 PM 1068 (0x042C)
    Could not find local DP locations from all MPs. Will fallback to MP download. ccmsetup 7/17/2013 12:42:27 PM 1068 (0x042C)
    GET 'HTTP://SCCMServer.acme.dom/CCM_Client/ccmsetup.cab' ccmsetup 7/17/2013 12:42:27 PM 1068 (0x042C)
    C:\Windows\ccmsetup\ccmsetup.cab is Microsoft trusted. ccmsetup 7/17/2013 12:42:47 PM 1068 (0x042C)
    Successfully extracted manifest file C:\Windows\ccmsetup\ccmsetup.xml from file C:\Windows\ccmsetup\ccmsetup.cab. ccmsetup 7/17/2013 12:42:47 PM 1068 (0x042C)

    ====================================================================================

    I have been testing with other application packages that I've built and distributed to the same DPs and everyone of those apps is using the local DP properly.  So I'm not sure why the client push isn't working properly.  Thanks in advance.


    Wednesday, July 17, 2013 9:35 PM

Answers

  • I was able to fix it by removing the site server at our HQ from the boundary group content location.  Now the client push sees the 1 local DP and downloads from there.  Then I just set our HQ site server as a fallback distribution point, and that seems to work pretty well
    • Marked as answer by Edd B Thursday, July 18, 2013 9:43 PM
    Thursday, July 18, 2013 9:43 PM

All replies

  • Are you sure your boundaries are correct?

    Using IP Subnet boundaries is not straight forward as you must ensure the Subnet ID calculated on the client matched the subnet ID you entered in the site (IP subnet boundaries are not ranges of IPs).

    From the above, your content location is off.

    Also, when creating your Boundary groups, did you add site servers to them?

    And, as a general best practice, are you using separate boundary groups site assignment and content location?


    Jason | http://blog.configmgrftw.com

    Wednesday, July 17, 2013 10:51 PM
  • I verified that the boundary subnet ID and the IP subnet property under discovery data for the device match.

    On the boundary group I have added the site server that is hosting the local DP at the site as well as my primary site server that's at our corporate HQ.  Not sure if this matters, but I also set the connection for our Corporate HQ as "Slow", and left the local site server connection as "Fast"

    Regarding your last point, I am not using separate boundary groups for site assignment and content locations.  Since I only have a single SCCM site would that really matter?  The machines I have tested on show that they have properly been assigned to the correct SCCM site.

    Thursday, July 18, 2013 12:08 AM
  • I was able to fix it by removing the site server at our HQ from the boundary group content location.  Now the client push sees the 1 local DP and downloads from there.  Then I just set our HQ site server as a fallback distribution point, and that seems to work pretty well
    • Marked as answer by Edd B Thursday, July 18, 2013 9:43 PM
    Thursday, July 18, 2013 9:43 PM