KB: The Add-CMDistributionPoint cmdlet in Configuration Manager sets an incorrect ServerRemoteName value

KB: The Add-CMDistributionPoint cmdlet in Configuration Manager sets an incorrect ServerRemoteName value

  • Comments 2
  • Likes

 Just a quick FYI on a new Knowledge Base article we published today. This one talks about 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.

In this scenario you find that the client tries to download the content from the first server installed in the hierarchy (the CAS or stand-alone Primary).

You can get all of the details in the article below:

KB2935813 - The Add-CMDistributionPoint cmdlet in Configuration Manager sets an incorrect ServerRemoteName value (http://support.microsoft.com/kb/2935813)

J.C. Hornbeck | Knowledge Engineer | Microsoft GBS Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • There is another workaround than using a VBScript as the article linked suggests. Below is a link to a PowerShell script by Arun Ramakrishnan that MSIT uses to build DPs using Orchestrator:

    http://sdrv.ms/10VYNqK

    The script is in the folder InstallDP.

  • Actually, the script linked shared previously is shared by Shitanshu Verma rather than Arun Ramakrishnan. They both describe how they use the scripts with Orchestrator below:

    How Microsoft IT Upgrades System Center Configuration Manager 2012 Hierarchy with System Center Orchestrator Automation

    channel9.msdn.com/.../UD-B319