locked
SCCM 2007 to 2012 Migration RRS feed

  • Question

  • Hey Guys,

    i just started working for a company as an SCCM administrator, they are doing and SC07 to SC12 migration using a script!!

    i only knew 1 way to do the migration which is using the tool provided in SC12.

    i can think of few things that can go wrong such as any modification to the object in SC07 will not be picked up by SC12, i have also noticed thousands of warnings in the SMS_INVENTORY_DATA_LOADER componenet:

    Inventory Data Loader failed to process the delta MIF file "XHT1JYI9J.MIF" and has moved it to "D:\Program Files\Microsoft Configuration Manager\inboxes\auth\dataldr.box\BADMIFS\NonExistentRow\wuh11y1f.MIF."
    
    Possible cause: The file attempted to update inventory information in the site database that does not already exist, or the file contains invalid syntax.
    Solution: The client inventory needs to be resynchronized, which will be done automatically. Look for the status messages 2714 and 2715, which indicate the resynchronization has begun.

    i am trying to tell them we should go back and do the migration using the SC12 tool but so far no one is listening, any ideas on what could possibly go wrong by not using the migration tool??

    
    
    
    
    
    

    thanks in advance.

    Wednesday, July 8, 2015 4:08 AM

Answers

  • any ideas on what could possibly go wrong by not using the migration tool?? - No one can answer this question unless we know what that script is and what it does. The correct way is to use SC2012 tool, but if its a script I hope it is well written and should perform proper migration. Best of luck !!!

    Prajwal Desai, http://prajwaldesai.com

    • Marked as answer by Imad Ubadat Wednesday, October 14, 2015 12:30 AM
    Wednesday, July 8, 2015 4:15 AM
  • Looking at the above screenshots, I don't think this is a script for SCCM 2007 -> 2012 migration.  What I could understand from the script is the ConfigMgr clients are being patched to the CU1 version.

    KB2938441


    Prajwal Desai, http://prajwaldesai.com


    • Edited by Prajwal DesaiMVP Wednesday, July 8, 2015 6:06 AM
    • Proposed as answer by lthomas.85 Wednesday, July 8, 2015 11:51 AM
    • Marked as answer by Imad Ubadat Wednesday, October 14, 2015 12:29 AM
    Wednesday, July 8, 2015 6:06 AM
  • I concur. That script has little to do with actually migrating the site. It's simply installing the 2012 R2 client agent with CU1.

    Not sure why in the world you would do CU1 instead of SP1 or at least CU5 at this point though if the migration if happening now.

    Also, the script has issues when calling ccmsetup as it places the /mp switch after the PATCH property and thus the /mp switch will be ignored as all switches must come before properties for ccmsetup. This implies that /mp is not needed which it usually isn't because it does *not* set the MP for the client agent.


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

    • Marked as answer by Imad Ubadat Wednesday, October 14, 2015 12:29 AM
    Wednesday, July 8, 2015 1:53 PM
  • its so meeded up, the script is packaged in SC07, they advertise it to a specific collection in SC07, it think it install the SC12 client and off you go.

    AD System discovery has been enabled in SC12, so all objects exist in both enviorments!

    i am tempted to ignore everything thats been done and remigrate everything including object with the SC12 client.

    • Marked as answer by Imad Ubadat Wednesday, October 14, 2015 12:29 AM
    Thursday, July 9, 2015 12:03 AM

All replies

  • any ideas on what could possibly go wrong by not using the migration tool?? - No one can answer this question unless we know what that script is and what it does. The correct way is to use SC2012 tool, but if its a script I hope it is well written and should perform proper migration. Best of luck !!!

    Prajwal Desai, http://prajwaldesai.com

    • Marked as answer by Imad Ubadat Wednesday, October 14, 2015 12:30 AM
    Wednesday, July 8, 2015 4:15 AM
  • Wednesday, July 8, 2015 4:57 AM
  • Looking at the above screenshots, I don't think this is a script for SCCM 2007 -> 2012 migration.  What I could understand from the script is the ConfigMgr clients are being patched to the CU1 version.

    KB2938441


    Prajwal Desai, http://prajwaldesai.com


    • Edited by Prajwal DesaiMVP Wednesday, July 8, 2015 6:06 AM
    • Proposed as answer by lthomas.85 Wednesday, July 8, 2015 11:51 AM
    • Marked as answer by Imad Ubadat Wednesday, October 14, 2015 12:29 AM
    Wednesday, July 8, 2015 6:06 AM
  • I concur. That script has little to do with actually migrating the site. It's simply installing the 2012 R2 client agent with CU1.

    Not sure why in the world you would do CU1 instead of SP1 or at least CU5 at this point though if the migration if happening now.

    Also, the script has issues when calling ccmsetup as it places the /mp switch after the PATCH property and thus the /mp switch will be ignored as all switches must come before properties for ccmsetup. This implies that /mp is not needed which it usually isn't because it does *not* set the MP for the client agent.


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

    • Marked as answer by Imad Ubadat Wednesday, October 14, 2015 12:29 AM
    Wednesday, July 8, 2015 1:53 PM
  • its so meeded up, the script is packaged in SC07, they advertise it to a specific collection in SC07, it think it install the SC12 client and off you go.

    AD System discovery has been enabled in SC12, so all objects exist in both enviorments!

    i am tempted to ignore everything thats been done and remigrate everything including object with the SC12 client.

    • Marked as answer by Imad Ubadat Wednesday, October 14, 2015 12:29 AM
    Thursday, July 9, 2015 12:03 AM