locked
ConfigMgr2012 Migration Question!!! RRS feed

  • Question

  • Hi, i need the following:

    I have an SCCM 2007 Server with only a "C:\" Drive and on this drive have the "C:\SCCM_Package" folder that contains all packages of 
    Config Mgr 2007.

    **SCCM 2007 R3

    **C:\ -> 90GB used of 130GB -- Contains Package Sources, 
    Wsus Sources, and all Binaries.



    In the other server i have SCCM 2012 with the following disc Configuration:

    **SCCM 2012 SP1

    **C:\ -> 50GB for OS

    **D:\ -> 50GB for SCCM installation

    **E:\ -> 200GB for Packages Sources & WSUS Files.



    And The Question: ¿Is Supported the migration from the package source in C:\ from SCCM 2007 server to the E:\ Drive of SCCM 2012 Server in the migration 
    Process.???

    and what would mean?

    Please Help I need it!!!!


    Best Regards - Saludos cordiales Juan Carrillo Vaccaris Engineer - Management, IT Professional Services, DATCO Chile S.A. E-Mail: Juan.Carrillo@datco.cl Website: http://www.datco.cl

    Tuesday, March 19, 2013 7:10 PM

Answers

  • It depends how you are referencing your package source in the 2007 site. In order to migrate packages you need to reference the package source location using UNC paths. For example if your package source locations are using C:\SCCM_Package\YourPackagePath you will not be able to migrate it, but if the SCCM_Package folder is being shared and your source is something like \\sccm2007\SCCM_Package\YourPackageSource it could be migrated because the SCCM 2012 server can access that source.

    More info: http://technet.microsoft.com/en-us/library/gg712672.aspx#Plan_Migrate_content

    When you migrate packages and programs, they are not modified by migration. However, before you migrate these, you must configure each package to use a Universal Naming Convention (UNC) path for its source file location. As part of the configuration to migrate packages and programs, you must assign a site in the destination hierarchy to manage this content. The content is not migrated from the assigned site, but after migration the assigned site accesses the original source file location by using the UNC mapping.


    Here's a tool that can help you change your package source location in mass if you are referencing location path instead of UNC: http://blog.coretech.dk/jgs/coretech-package-source-changer-0-3-0-0/


    Justin Chalfant | Blog: setupconfigmgr.com | SCUP Catalog: patchmypc.net/scup | Please mark as helpful/answer if this resolved your issue




    Tuesday, March 19, 2013 7:19 PM
  • The cm2012 server will need to access the original source locations for the packages.  For example in CM2007, your original source location might have been \\server\share\packagesource.  CM2012 will read your CM2007 server and it's configurations, then build packages in 2012 using those same original source locations that are documented in your package properties in 2007. 

    The Distribution point on your CM2012 server can be on any drive you designate on that server, or on another site server setup as a DP.  But your packages sources will remain the same in 2012 as they were in 2007. 

    Tuesday, March 19, 2013 7:23 PM

All replies

  • It depends how you are referencing your package source in the 2007 site. In order to migrate packages you need to reference the package source location using UNC paths. For example if your package source locations are using C:\SCCM_Package\YourPackagePath you will not be able to migrate it, but if the SCCM_Package folder is being shared and your source is something like \\sccm2007\SCCM_Package\YourPackageSource it could be migrated because the SCCM 2012 server can access that source.

    More info: http://technet.microsoft.com/en-us/library/gg712672.aspx#Plan_Migrate_content

    When you migrate packages and programs, they are not modified by migration. However, before you migrate these, you must configure each package to use a Universal Naming Convention (UNC) path for its source file location. As part of the configuration to migrate packages and programs, you must assign a site in the destination hierarchy to manage this content. The content is not migrated from the assigned site, but after migration the assigned site accesses the original source file location by using the UNC mapping.


    Here's a tool that can help you change your package source location in mass if you are referencing location path instead of UNC: http://blog.coretech.dk/jgs/coretech-package-source-changer-0-3-0-0/


    Justin Chalfant | Blog: setupconfigmgr.com | SCUP Catalog: patchmypc.net/scup | Please mark as helpful/answer if this resolved your issue




    Tuesday, March 19, 2013 7:19 PM
  • The cm2012 server will need to access the original source locations for the packages.  For example in CM2007, your original source location might have been \\server\share\packagesource.  CM2012 will read your CM2007 server and it's configurations, then build packages in 2012 using those same original source locations that are documented in your package properties in 2007. 

    The Distribution point on your CM2012 server can be on any drive you designate on that server, or on another site server setup as a DP.  But your packages sources will remain the same in 2012 as they were in 2007. 

    Tuesday, March 19, 2013 7:23 PM
  • both answers works thanks!!!!  SpecialEdward and Justin Chalfant!!

    Best Regards - Saludos cordiales Juan Carrillo Vaccaris Engineer - Management, IT Professional Services, DATCO Chile S.A. E-Mail: Juan.Carrillo@datco.cl Website: http://www.datco.cl

    Wednesday, March 20, 2013 2:22 PM
  • It depends how you are referencing your package source in the 2007 site. In order to migrate packages you need to reference the package source location using UNC paths. For example if your package source locations are using C:\SCCM_Package\YourPackagePath you will not be able to migrate it, but if the SCCM_Package folder is being shared and your source is something like \\sccm2007\SCCM_Package\YourPackageSource it could be migrated because the SCCM 2012 server can access that source.

    More info: http://technet.microsoft.com/en-us/library/gg712672.aspx#Plan_Migrate_content

    When you migrate packages and programs, they are not modified by migration. However, before you migrate these, you must configure each package to use a Universal Naming Convention (UNC) path for its source file location. As part of the configuration to migrate packages and programs, you must assign a site in the destination hierarchy to manage this content. The content is not migrated from the assigned site, but after migration the assigned site accesses the original source file location by using the UNC mapping.


    Here's a tool that can help you change your package source location in mass if you are referencing location path instead of UNC: http://blog.coretech.dk/jgs/coretech-package-source-changer-0-3-0-0/


    Justin Chalfant | Blog: setupconfigmgr.com | SCUP Catalog: patchmypc.net/scup | Please mark as helpful/answer if this resolved your issue




     Does this tool change the package source location on the 2007 site?  If yes,  doesnt that resend the packages to all DPs because the source location has changed?
    Monday, March 25, 2013 3:29 AM