locked
SCCM 2007 to SCCM 2012 R2 SP1 Migration RRS feed

  • Question

  • Hi All,

    Any one suggest me whether we can migrate MDT Tasksequences and Bootimages to SCCM 2012?

    Also suggest me whether we can re-create (Drivers,Driver Packages ) in SCCM 2012 or migration from SCCM 2007 is the best approch?




    Friday, June 3, 2016 1:06 AM

Answers

  • Are you talking about stand-alone MDT or MDT integrated into ConfigMgr?

    IMO, migrating driver packages is a waste of time and effort and it's better to start over and fresh on the new site. It is technically possible to migrate them though.

    Side question: why would you migrate to 2012 instead of Current Branch (which is the current version of ConfigMgr)?


    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Marked as answer by Sreenivas C Sunday, June 5, 2016 6:10 PM
    Friday, June 3, 2016 1:44 PM
  • It is possible to migrate those TSes but the MDT tasks won't migrate cleanly from memory and there's a lot of cleanup to do so it's actually less work and less problematic to start over. If you've done things correctly using MDT though, most (if not all) of your configurations should be in your customsettings.ini or your DB anyway so re-creating them will be easy.

    "Is there any issues we can expect while migrating the Drivers and driver packages and boot images from SCCM 2007 to SCCM 2012?"

    No, issues to my knowledge, but once again, why would you migrate your boot images? They don't match the version of the ADK that you'll be using so won't be editable and won't be usable for WIn10 deployment.

    "We will migrate to currenbranch once migration activity completed."

    Why? This is completely wasted effort. There's absolutely no reason to migrate to 2012 if you will be going to CB except that you like to waste time (or you're working for a customer and like billing them for unnecessary work).


    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Marked as answer by Sreenivas C Sunday, June 5, 2016 6:09 PM
    Saturday, June 4, 2016 1:24 PM
  • For your TS's make a note of the MDT steps in the them. Remove those steps. Migrate the TS and recreate the steps.

    Cheers Paul | http://sccmentor.wordpress.com

    • Marked as answer by Sreenivas C Sunday, June 5, 2016 6:09 PM
    Saturday, June 4, 2016 9:43 PM

All replies

  • Are you talking about stand-alone MDT or MDT integrated into ConfigMgr?

    IMO, migrating driver packages is a waste of time and effort and it's better to start over and fresh on the new site. It is technically possible to migrate them though.

    Side question: why would you migrate to 2012 instead of Current Branch (which is the current version of ConfigMgr)?


    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Marked as answer by Sreenivas C Sunday, June 5, 2016 6:10 PM
    Friday, June 3, 2016 1:44 PM
  • Thanks Jason.

    MDT integrated into Configmgr 2007. we need to migrate those task sequences. As per Technet not possible those TS?

    Is there any issues we can expect while migrating the Drivers and driver packages and boot images from SCCM 2007 to SCCM 2012?

    We will migrate to currenbranch once migration activity completed.



    Saturday, June 4, 2016 1:15 PM
  • It is possible to migrate those TSes but the MDT tasks won't migrate cleanly from memory and there's a lot of cleanup to do so it's actually less work and less problematic to start over. If you've done things correctly using MDT though, most (if not all) of your configurations should be in your customsettings.ini or your DB anyway so re-creating them will be easy.

    "Is there any issues we can expect while migrating the Drivers and driver packages and boot images from SCCM 2007 to SCCM 2012?"

    No, issues to my knowledge, but once again, why would you migrate your boot images? They don't match the version of the ADK that you'll be using so won't be editable and won't be usable for WIn10 deployment.

    "We will migrate to currenbranch once migration activity completed."

    Why? This is completely wasted effort. There's absolutely no reason to migrate to 2012 if you will be going to CB except that you like to waste time (or you're working for a customer and like billing them for unnecessary work).


    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Marked as answer by Sreenivas C Sunday, June 5, 2016 6:09 PM
    Saturday, June 4, 2016 1:24 PM
  • For your TS's make a note of the MDT steps in the them. Remove those steps. Migrate the TS and recreate the steps.

    Cheers Paul | http://sccmentor.wordpress.com

    • Marked as answer by Sreenivas C Sunday, June 5, 2016 6:09 PM
    Saturday, June 4, 2016 9:43 PM
  • we can use ADK 10 boot image for windows 7 Deployments but Present one tested and using in SCCM 2007. If we import the SCCM 2007 custom boot image/ MDT boot image in SCCM 2012 and use any issue?

    CB implementation -  we need minimum of Windows 2008 R2 or above AD domain functional level. Currently we have 2003 AD domain controllers also we have implemented SCCM 2012 in the month of Jan-2016.



    Monday, June 6, 2016 1:45 AM
  • Asked and answered already on the boot image.

    For CB and AD, the whole point is that Windows Server 2003 itself is no longer supported. Having an AD based on server 2003 works fine but isn't technically supported because those don't test against it because, as mentioned, server 2003 hasn't been supported for almost a year now.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Monday, June 6, 2016 1:54 AM