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.