Several ConfigMgr scenarios require that the content Source Path be changed. This typically includes migrating to a new ConfigMgr environment (2007 to 2012, 2012 to Current Branch, etc.), and simply moving the source content to a new location such as a DFS Share or low-speed NAS device.
Updating the Source Path can be done manually via the ConfigMgr console. For Packages, Software Update Deployment Packages, Drivers, Driver Packages, Operating System Images, Operating System Upgrade Packages, Boot Images, and Virtual Hard Disks, just add the Pkg Source Path or Package Source Path column to the console view to review the paths, then edit the object’s Source Folder in the Data Source tab.
However, for Applications, you’ll have to step through each Deployment Type on each Application, view the properties and modify the Content Location in the Content tab.
This is all painfully slow if you have more then a handful to deal with. So, automate it!
The community has developed at least 5 solutions to this including
- Matt Shadbolt http://blogs.technet.com/b/configmgrdogs/archive/2013/05/09/package-amp-application-source-modification-scripts.aspx with some updates by Nick Moseley https://t3chn1ck.wordpress.com/2014/04/18/fixes-to-microsoft-package-source-conversion-scripts and additions https://t3chn1ck.wordpress.com/2014/05/05/configmgr-migration-script-driver-source-path-conversion/
- Alex Verboon http://www.verboon.info/index.php/2013/05/how-to-change-the-sccm-2012-package-source-path-with-powershell
- Inframon http://blogs.inframon.com/post/2012/05/31/Changing-the-Package-Source-Path-in-ConfigMgr-2012.aspx (no longer available)
- Coretech’s Package Source Changer http://blog.coretech.dk/jgs/coretech-package-source-changer/
- Nickolaj Andersen’s ConfigMgr Content Source Update Tool http://www.scconfigmgr.com/2015/08/26/configmgr-content-source-update-tool-1-0-0
CoreTech and Nickalaj have the slickest solutions. Sometimes a GUI gives the visual feedback you need to be confident in the final outcome.
Either of these two tools should effectively handle the changes. As a bonus, both will actually copy the content files from the old to the new path. Awesome!
chad September 28, 2016
Tags: ConfigMgr; SCCM