This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 76%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERJ%3C/text%3E%3C/svg%3E)
I need to move our source distribution point which contains all packages, applications, images, drivers data to new hardware.
New server 2016 has been configured as a distribution point and all source data has been copied over.
I need to update source path for all application, packages, drivers in MECM Console.
Is there a reliable or supported tool I can use to update source path in console rather doing it all manually?
I do see Administration>Migration option since We're not moving our primary site server at this time Distribution Point Migration option is greyed out.
Please advise.
RJ
Other Configuration Manager-related features and issues
It seems there is no update for a couple of days. Have you tried the suggestions provided? How about the status of the problem?
I agree with Jason, that tool has saved me in the past.
I've documented my experience on my blog, and also I'd recommend using an Alias for your source server to help prevent this moving forward.
https://garytown.com/setup-alias-for-your-configmgr-content-source
This is a great tool for task that many have used over the years for similar tasks: https://msendpointmgr.com/2017/02/23/configmgr-content-source-update-tool-version-1-0-2-released/
The tool uses the supported PowerShell cmdlets so while we don't support the tool itself, it does use supported methods.
On a semantic note, source content locations are completely unrelated to distribution points. You may have them co-located, but that's a configuration choice that you've made and there is no technical connection.
Thanks for your response. After reviewing Q&A I am little hesitant to use source-update-tool.
You're free to do this manually then or write your own PowerShell.
Have you tested this in your lab environment?
Thanks Jason, I ran the script and it seems to work fine for me. I don't have a lab environment setup. I started with couple of applications and script seemed to work and updated everything.
Thanks for your valuable advise. It save me lot of time. Created a dns cname record for future.
RJ