Microsoft has just updated the following KB Article:
The Add-CMDistributionPoint cmdlet in Configuration Manager sets an incorrect ServerRemoteName value
Symptoms
Consider the following scenario:
- You use the Add-CMDistributionPoint PowerShell cmdlet introduced in Cumulative Update 1 for System Center 2012 Configuration Manager Service Pack 1 to create a new remote Distribution Point (DP).
- You deploy content to the new DP and then create a deployment that requires that content for a client in the same remote location as the new DP.
After doing so, you find that the client tries to download the content from the first server installed in the hierarchy (the CAS or stand-alone Primary). In the event that the first server in the hierarchy is a stand-alone Primary that is a Distribution Point hosting the content, the client successfully downloads the content. This is evidenced by the DataTransferService.log entries on the client