Monday, 29 July 2013

ConfigMgr 2012 / SCCM 2012 Migration - Share Distribution Points

Back to Migration menu
 

During the migration from ConfigMgr 2007 to 2012 you can "share" your 2007 DPs as follows:
  • DPs are still owned by the 2007 environment
  • Content can be provided to the 2012 clients
  • Provides a mechanism to perform in place upgrades of DPs to 2012 (including migration of 2007 Secondary Sites to 2012 DPs)


Open the properties of the Source Hierarchy



Enable Distribution Point sharing for the Source Site. This is a site-wide configuration and cannot be done for individual DPs.

 


Enabling this setting starts a “data gathering job”. This job will synchronise details of the 2007 DPs so that they will be available in the 2012 environment.


 


View job in console


Verify progress using the migmctrl.log file.



On completion of this job the shared DPs are available in the SCCM 2012 console.



Note the column “Eligible for Upgrade”


17 comments:

  1. One gotcha is you have to remove the State Migration Point (SMP) and PXE in order for the Dp to be eligible. Might have to remove other roles too.

    ReplyDelete
  2. You're right there. Thanks. I've covered that in the "upgrade" section.

    http://gerryhampsoncm.blogspot.ie/2013/08/configmgr-2012-sccm-2012-migration.html

    ReplyDelete
  3. Hi Gerry,
    We are on the process of upgrading the server OS of an SCCM primary site and wanted to ask you what is the best way to approach this. We currently have SCCM 2012 R2 RTM running on a Windows Server 2008 R2. On the SQL side, the DB runs on SQL 2008 on a separate Win2008R2 server. Our goal is to bring a new Windows 2012 R2 server, install a new SCCM site and use the migrate feature.
    Do you have any recommendations/suggestions and are there any issues with this method?

    ReplyDelete
    Replies
    1. The correct procedure is to build the new server and recover the site from backup.

      Delete
  4. Hello Gerry,
    I have 23 SCCM 2007 SP2 Secondary Sites running on Windows Server 2003 x86 and i want to upgrade both OS Windows server to 2012 R2 and convert all secondary sites to Distribution Point on SCCM 2012 R2. What´s could be the best way to achieve this goal?

    ReplyDelete
  5. You won't be re-using the old secondary sites then. You'll have to decommission them and deploy new 2012 R2 DPs. You'll also have to re-assign the clients. You should also consider going straight to Current Branch (1511).

    ReplyDelete
    Replies
    1. could be possible next scenario???

      1.- Deploy 23 new boxes with W2K12 R2 OS and add them like Distribution Points in SCCM 2012 R2.

      2.- Upgrade old Secondary Sites with W2k3 x86 to DP´s in SCCM 2012 R2.

      3.- Replicate content among all DP´s and finally delete content from old DP´s and Decommission them. keep just the new DP´s

      Delete
  6. Thanks for your response Gerry. To avoid resend data over the LAN and appear some bottleneck problems, could make the following?

    1.-Upgrade those secondary sites with 2K3 x86 to DP´s in SCCM 2012 R2
    2.-Install new DP´s with 2K12 R2 OS and add it to DP´s in SCCM
    3.-Replicate all data content (folders and bynaries) among both old and new servers.
    4.- (Optional) Decommission all converted 2K3 x86 DP´s

    If it is possible, please guide me to an strategy to replicate the content.

    ReplyDelete
    Replies
    1. If you are worried about re-distributing over the WAN you should look at pre-staging the content

      https://technet.microsoft.com/en-us/library/gg712694.aspx?f=255&MSPPError=-2147217396

      Delete
  7. Would there be any issues on using APP-V application in SCCM 2007 using Shared DP?

    ReplyDelete
    Replies
    1. I'm not sure what you are asking. Are you asking if the AppV client package can be distributed to a shared DP? If so the answer is that this should be OK. It's just an app after all (although I haven't done much work with AppV).

      Delete
  8. Hi Gerry,

    We are migrating from SCCM 2007 to Current Branch v1606 and experience a problem when DP Sharing is enabled after the data gather job runs. All Boundaries from the source 2007 hierarchy are automatically migrated to the destination hierarchy, resulting in overlapping boundaries.

    As a result of the overlapping boundary configuration, 2007 clients struggle to find their DP. If I remove the Boundaries in the destination hierarchy they continue to migrate automatically after every data gather.

    Do you know if the migration process changed in v1606 and the Boundary migration is now an automatic process? If possible we would like to control Boundary migration to avoid overlapping and such issues with 2007 clients.

    Thanks...

    ReplyDelete
    Replies
    1. This is an automatic process and has always been the case as far as I recall. Boundaries are migrated when you enable DP sharing.

      Delete
  9. Hi Gerry,

    I am migrating from 2012 to 1610 and have shared the DPs. But Content download from shared DPs is not working for 1610 clients. Getting Http 404 error (0x87d0027e) in the datatransferservice.log.

    any idea?

    ReplyDelete
    Replies
    1. http 404 is file not found. Have you configured a boundary/boundary group for the new clients and added the DP as a site system?

      Delete
    2. Hi Gerry,
      Yes. The boundary and boundary groups are migrated and the DP is added as site system in the boundary group. CAS.log identifies the DP for the specific content. But It is not downloaded and datatransferservice.log shows the above error.

      Thanks.

      Delete