1. Introduction

As we start migrating from CM2007 to CM2012 one of the requirements is that the package source used for packages must be a UNC.

we have seen many site installations where the package source is either a local source on the site server or a UNC pointing to the site server. In either case, you must somehow update the package source before starting the migration.

You can use the “list” button to list all sources that are current in use, and select the one you want to edit.

This utility is Freeware, making it illegal to change or sell, but legal to use in any purposes.

This is the second beta version. Please report any failures or bugs!

Thank you! 🙂

We hope you’ll benefit from our application. Please report any suggestions problems or errors to Coretech at configmgr@coretech.dk

2. Installation

No installation needed. Unpack the zip file to a folder on the site server

Share This Story, Choose Your Platform!

Jakob Gottlieb Svendsen is a Microsoft Cloud and Data Center Management MVP (http://mvp.microsoft.com/en-us/default.aspx), Working as Global Lead Developer, Senior Consultant and Trainer at CTGlobal, where he is one of the driving forces in keeping CTGlobal a System Center Gold Partner and member of the System Center Alliance.

Since he started at Coretech in 2007, he has focused on Scripting and Development, primarily developing tools, extensions and scripts for the System Center Suite. His main area is Automation (including OMS/Azure Automation, Service Management Automation, PowerShell and Orchestrator). Another area is Windows Azure Pack / Azure Stack, where he does implementation, development, workshops and presentations. He is a world-wide renowned voice in the Automation field.

He is passionately devoted to the community, to which he contributes by being a moderator at TechNet and sharing his knowledge at https://blog.ctglobalservices.com/jgs

Thanks for your excellent work. Really helps me in prepairing the move from 2007 to 2012!

One simpel request 🙂

Is it possible for you to make the copy files function keep the letter formatting after copying over a folder from the old to the new package source? It’s a bummer that i have to rename every folder after moving, changing small letters to capital letters. E.g. folder named ‘Adobe’ on old source becomes ‘adobe’ on new source.

Quick Question: Kent’s instruction on his book walks me through this tool to perform the source reference change (and file copy) on SCCM *2007* (BEFORE the migration)
Can I actually migrate over with existing source location as-is first then run through this tool to migrate/copy over to a new server?

This way, we can go through the list and migrate only things that are valid/useful first then migrate the actual packages/files/folders meaningful…

I can just run it and see what happen but as you are the creator of it so… 🙂

Thanks for a good tool for administration, allthough there is one caveat I noticied. The SMSPackage table in the database does not get updated with a new blank package share name, hence the v_Package view also retains the value of the custom share name.

Thanks for the wonderful tool. I had a question, we have around 600 distribution points and would the change in source trigger an update to all DP’s? This would create a lot of traffic and a big chance of getting the slow networks down.
We tried using sql to update the source location, but it does trigger an update to all the DP’s for that package. Is there anyway we can disable the update, change the source and re-enable it?

I can confirm as Jan Jaap Schoone says 11th Mar 2013. The database don’t update when you set the “Clear custom package share name”.
I noticed this problem when starting migration from 2007 to 2012. The packages won’t simply migrate over. So i had to revert this back, and then it worked.