Hey,
Yes, You shound create a distribution point at the remote site, configure a boundary for the remote site and add the boundary to a boundary group for that site (This is how clients will know to pull the package binaries from the local DP at the remote site).
When you create to boundary group for the remote site, you would select the remote distribution point for the content location for that remote site more info about setting up boundaries/boundary groups here:
http://technet.microsoft.com/en-us/library/gg712679.aspx . You definitely wouldn't want to create a secondary site for a remote site with only 20-25 clients and DP would work fine and reduce
complexity. The only reason would want to considerer a secondary site would be when you have over 400 + clients at a remote site and the connection is slow and you don't want all those clients coming back to the main site client policy and software update
evaluation etc.
Justin Chalfant | Blog: setupconfigmgr.com | SCUP Catalog: patchmypc.net/scup | Please mark as helpful/answer if this resovled your issue
