Wednesday, 10 July 2013

ConfigMgr 2012 / SCCM 2012 Migration - Pre-Migration tasks

Back to Migration menu

Back to ConfigMgr 2012 menu

The following tasks should be carried out before attempting to migrate ConfigMgr 2007 objects to ConfigMgr 2012.

1. Collections: Collections containing both users and systems or devices are not supported in ConfigMgr 2012 and can't be migrated – create separate collections

2. Software Updates: add the WSUS role and the Software Update Point as described in this section:

Classifications and products must match the ConfigMgr 2007 environment and be successfully synchronized. If a single update is missing from an entire update package the migration of that package will fail. 

3. Package Source Directory: copy your source share to the new server (using your favourite file copying software), while retaining folder structure and permissions.

If you are using local paths (F:\Sources\Microsoft\Office\2013) as your package source directories you are in good shape. The packages should migrate with no bother. 

However if you have used UNC paths (\\Server\Sources\Microsoft\Office\2013) you will need to change this for all the affected packages (\\NewServer\Sources\Microsoft\Office\2013).

Luckily Coretech have provided a free utility to help you to do this. 

You can download the Coretech Package Source Changer here

Extract the files to a folder 

Run PackageSourceChanger.exe as administrator

Accept the License Terms

This is the generic startup screen. You must configure for your environment. Select "Configuration".

Enter your ConfigMgr server name and Save. Select List to see the configured paths 

The list of configured paths is displayed. Select the one you have to change and click OK.

Enter the new package source and click Select Packages.

Select all the packages and Save

Click Start to change the Source Path of the selected packages.


  1. Do I have to change the source path Prior or after migrating the packages to the new ConfigMgr-Server?

  2. Hi Gerry, why do we want to do this. is this not taken care when migration is in progress.

    1. Are you referring to the source path Nawaz? This is not altered during the migration.

  3. Hi Gerry,

    Just to confirm, copy the source files onto the new server then run the source file changer.
    or Copy the source files, Migrate some packages and then change source files.

    Sorry have not seen any clarificationon this point

    1. You can do this in whatever sequence you wish. The goal is the same. Ensure that you have copied your source files, migrated your packages & ensure that the source paths are correct.

      It can make sense to run the source changer tool only on the new server after the packages are migrated. In this way you can still use the CM 2007 environment during the migration.

  4. Hi Gary,

    Can you give post migration task or checklist to validate the migration.

    1. This is such a vast product and every deployment is different. Therefore there is no published "checklist" as such. You really have to review your logs and test all your required functionality.