Saturday, 10 August 2013

ConfigMgr 2012 / SCCM 2012 Migration - Upgrade Distribution Points

Back to Migration menu

Back to ConfigMgr 2012 menu

Now that you have "shared" your ConfigMgr 2007 Distribution Points they are now available in the ConfigMgr 2012 console.

Administration > Migration > Source Hierarchy > Shared Distribution Points

ConfigMgr 2012 supports an in-place upgrade of 2007 DPs in the following scenario:
  • No additional roles can be present. (PXE, SMP, etc)- only distribution point role (can be secondary site server)
  • 100% free disk space is required so that 2007 content can be converted to 2012 single instance content library (see *** below)
  • Can be Windows 2003 server upwards
  • Configuration Manager 2007 client must be removed before performing upgrade
*** Edit:
For System Center 2012 Configuration Manager with no service pack, this conversion requires available free disk space equal to two times the size of the existing data on the distribution point. Beginning with System Center 2012 Configuration Manager SP1 and System Center 2012 R2 Configuration Manager, this conversion requires available free disk space equal to the size of the largest package that is stored on the distribution point.***

In my case all servers are Secondary Site servers. There is no direct upgrade path from a Configuration Manager 2007 Secondary Site to a Configuration Manager 2012 Secondary Site (as 2012 now requires SQL replication).
However, in most cases, 2012 secondary sites may not be required. You would only need a secondary site if you also need to control traffic sent from client systems to the site server, as the secondary site has a Management Point.
You can now enable PXE support and bandwidth throttling (with scheduling and rate limits) directly on 2012 Distribution Points.

These are the basic steps to carry out the in-place upgrade

Distribution Point only upgrade step by step:

Create site hierarchy (previously completed)
Enable distribution point sharing(previously completed)
Select a Shared Distribution Point to upgrade
Complete migration job wizard
Migration job

Configuration Manager 2012 distribution point installs
Content conversion is performed
Job is completed.

Secondary Site / Distribution point upgrade step by step:

Create site hierarchy (previously completed)
Enable distribution point sharing (previously completed)
Navigate and select a Shared Distribution Point to upgrade
Migration job
Configuration Manager 2012 uninstalls Configuration Manager 2007 secondary site
Upgrade job pauses awaiting next data gathering job to verify if the Secondary Site uninstall is completed (can manually start this task)
Configuration Manager 2012 distribution point installs
Content conversion is performed
Job is completed.

Choose server, right click, select Upgrade to launch the "Upgrade Shared Distribution Point Wizard"

Select new Site Code

Choose to “Install and configure IIS if required”

PXE not required at this time

Verify boundary group and click Next

Review existing content on DP. See space required for content conversion.

Verify summary

Finish wizard

Distribution Point Migration > See job – Secondary Site uninstalling

Monitor progress using migmctrl.log file

After a short period the secondary site will no longer be available in ConfigMgr 2007 environment. However the job will still show pending in 2012 console.
Manually run Data Gather (or wait for schedule)

Right click the hierarchy and select "Gather Data now"

Data Gather commences

Monitor progress using migmctrl.log

After Data Gathering completes 2012 detects that Secondary Site has been uninstalled and in place upgrade starts automatically

Monitor progress using distmgr.log

Upgrade complete

Packages now being processed and migrated to ConfigMgr 2012 Content Library

Perform test distribution of new package or application

Verify success

Configure Rate Limits and schedule in DP properties

Post-Upgrade Tasks

1. Manually delete 2007 content from DP
2. Manually delete 2007 Secondary Sites from System Management container


  1. Hi Gerry...during the period when DPs are shared between 2007 and 2012 for SCCM 2007 and 2012 clients...will it be possible to access 2012 DP from 2012 client ?
    I see that my SCCM 2012 client was working with my SCCM 2012 DPs, but when i enabled the DP share option in the migration wizard, the SCCM 2012 client can't access the SCCM 2012 DP any more :-(

  2. The "Share DP" option should have no effect on 2012 site client/DP communication. The only effect should be that the 2007 DPs should be come available to the 2012 clients.

  3. Hi Gerry, for manually deleting the old 2007 content can you remove file the SMSPKG and SMSPKGD$ folders with the old .pck and package files? Or keep the folders but flush the contents?

    1. Sorry for the late response. I've been on vacation. What version are you using?

      After Configuration Manager converts the content to the single instance store, the following action is taken depending on the version of the Configuration Manager destination hierarchy:
      • A hierarchy that runs System Center 2012 Configuration Manager with no service pack leaves the original source content intact on the distribution point computer.

      • Beginning with System Center 2012 Configuration Manager SP1 and System Center 2012 R2 Configuration Manager, Configuration Manager deletes the original source content on the distribution point computer to free up disk space and does not use the original source content location.

  4. Hi Gerry, what is the best option of migrating/updating 2007 Secondary Sites with DPs installed on Server shares, to SCCM 2012 R2 DP? This is the produciton environment with 17 remote secondary sites with Distribution Points on server shares. thanks

    1. DPs on Server Shares are handled in the same way as Standard DPs Sakib.

  5. Overlapping boundaries will cause an issue. When DPs are in shared mode, the boundary group created in the destination hierarchy will still have a reference for the 2007 DP and if the new 2012 client is in an IP boundary of the 2007 DP you will see issues with deployments. This is a common issue when attempting pilot group upgrades for clients.