Updating the package source in Configuration Manager 2007

In my “Migrating from Configuration 2007 to Configuration Manager 2012” session at the System Center User Group meeting in Copenhagen last Friday, I demonstrated a tool to automatically update the package source in Configuration Manager 2007. As promised, this tool is now available for download.

The background for the tool

As we start migrating from CM2007 to CM2012 one of the requirements is that the package source used for packages must be a UNC. I 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.

Together with my colleague Jakob G. Svendsen I developed a tool that can assist you in the process. The tool can be downloaded here.

Use the tool

In this example I will update two different package sources from the local CM2007 site server to my new file server. As you can see from the illustrations I have packages using two different sources:

Both sources will be updated to the new source location which is \\SCCM3\SCCM_Sources$\Software Along with updating the source, I will also copy the files to the new location.

  1. Start the tool by opening PackageSourceChanger.exe as administrator. Accept the license terms.
  2. Click Configuration and type the name of the Configuration Manager 2007 server. Click Save when done.
  3. I Find type: \\SCCM1\SCCM_Sources$\Software and click Verify.
  4. In Replace type: \\SCCM3\SCCM_Sources$\Software and click Verify.
  5. Check Copy content from Old to new source.
  6. Click Select Packages and select the packages from the list.
  7. Click Save when done.
  8. Click Start to start the package source update process.
  9. If you click Verify Location you should be able to see the packages in the new location.

The Consequences

You need to test and plan these package sources updates. Updating a package source will start a package update on all the distribution points. For even a medium size site this can take several hours.


By | 2011-05-03T20:14:21+00:00 May 3rd, 2011|Configuration Manager (SCCM), General info|4 Comments

About the Author:

Kent Agerlund
Microsoft Regional Director, Enterprise Mobility MVP. Microsoft Certified Trainer and Principal consultant. I have been working with Enterprise client management since 1992. Co-founder of System Center User Group Denmark in 2009. Certified MCITP: Enterprise Administrator, MCSA+Messaing, and much more. Member of: Microsoft Denmark System Center Partner Expert Team The Danish Technet Influencers program System Center Influencers Program.


  1. Jas May 2, 2012 at 19:21 - Reply

    Needn to fix the program. When updateing it leaves out the trailing in the file paths resulting in wrong unc path: so what should be \serverf$app comes out as \serverf$java

    on both from and to

  2. Swa May 30, 2012 at 11:33 - Reply

    Any plans to support driver and driver package migration?

  3. John Puskar June 18, 2012 at 20:58 - Reply

    Hey, this tool looks awesome! However, it crashes before actually changing any package data when pointed at my sccm 2012 site server. Also, it won’t let me add a fqdn as the target directory. Another thing: when you run as non-priv, it crashes instead of letting you know that you need to escalate. I assume this is due to the default log location being at C:.


Leave A Comment