locked
Side-by-side migration RRS feed

  • Question

  • Hi,

    I have a SCCM 2007 installation, one site/server only. Just installed SCCM 2012 R2 on a new machine, same domain. I'd like to migrate from 2007 to 2012 but (for now) keep the 2007 as the 'live' SCCM and have 2012 for testing only. What would be the best way to go about this?

    And when it's time to "flip the switch" and make 2012 the 'live' one, what would be needed?

    Thanks in advance.

    Tuesday, November 19, 2013 11:21 AM

All replies

  • This is a supported way forward. Make sure not to write overlapping boundaries to Active Directory and you should more or less be home safe.

    For migration, you can read more on:

    Good luck!


    Tim Nilimaa | Blog: http://infoworks.tv | Twitter: @timnilimaa

    Tuesday, November 19, 2013 12:02 PM
  • Thanks for the reply Tim. To make sure the 2007 site is still the one serving the clients (and visible to them), do I need to do something specific? The current boundary is an "AD Site", so I guess I could, for now, just create an "IP Subnet" boundary on the 2012 server.

    And will enabling (or not) shared distribution points have any impact as well?

    Thanks.


    • Edited by Dan Tei Tuesday, November 19, 2013 12:18 PM
    Tuesday, November 19, 2013 12:17 PM
  • I recommend not to use IP Subnets at all, in that case use IP Address Range instead.

    When you create a Boundary Group (new in SCCM 2012) you can opt-out from writing the information to Active Directory by not use the Boundary Group for site assignments. You can read more on Client Assignment and Boundary Groups here http://technet.microsoft.com/en-us/library/gg682060.aspx and http://technet.microsoft.com/en-us/library/hh427326.aspx

    Shared Distribution Points do not affect client Site Assignment. You can read more on Content Deployment Migration and Shared DPs on this site http://technet.microsoft.com/en-us/library/gg712275.aspx


    Tim Nilimaa | Blog: http://infoworks.tv | Twitter: @timnilimaa

    Tuesday, November 19, 2013 12:27 PM
  • Tuesday, November 19, 2013 12:44 PM
  • Thanks for the replies Tim and Gerry, appreciate it :)
    Tuesday, November 19, 2013 1:51 PM
  • Sorry guys, but wonder if you've seen this. When trying to migrate data from 2007 to 2012, it stops when it reaches a boot img with the error "provider exception: failed to verify that the WIM file has a valid compression type". Yesterday the message (on the same object) was "provider exception failed to insert OSD binaries into the WIM file".

    This happens if I try a collection migration or, tried this morning an object migration, just selecting the task sequences, same thing.

    I read somewhere it might be because I installed the latest MDT and the original task sequences were built using MDT 2010, but I can't find it anywhere to download, so can't test that.

    Thanks in advance.

    Wednesday, November 20, 2013 10:42 AM
  • See smsprov.log then.

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, November 20, 2013 11:26 AM
  • Thanks for the tip Torsten, silly me forgot about it. 

    After several errors which I managed to solve one by one, I've now come to this error message:

    "failed with: Type BDD_UsePackage are not found"

    When migrating the task sequences. I'm guessing this is because the 2007 setup has MDT 2010 U1 and this new server has MDT 2013. 

    Are the only two solutions either upgrade the 2007 task sequences to MDT 2013 and then migrate or install MDT 2010 on the new server and migrate the task sequences? If so, I'd rather go with the 2nd scenario but can't find MDT 2010 U1 anywhere to download.

    Wednesday, November 20, 2013 2:31 PM
  • Just remove all MDT specific task sequence steps (there are not much, gather, use toolkit package etc), migrate the task sequence and re-add them.

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, November 20, 2013 2:41 PM
  • Hi,

    By default MDT task sequence from SCCM 2007 cannot be migrated to SCCM 2012. As probably the MDT versions will be different.

    There is a way to migrate them but then you have to update MDT on the SCCM 2007 server to the same version as MDT on the SCCM 2012 server, more information can be found here: http://www.ronnipedersen.com/2012/03/migrate-a-configmgr-2007-mdt-task-sequence-to-configmgr-2012/

    In my experience it's easier to just manually recreate the SCCM 2007 task sequences in SCCM 2012. Well, that's what I've been doing in my past migration projects.

    Kind regards,

    Bert

    Wednesday, November 20, 2013 2:43 PM
  • There is a way to migrate them but then you have to update MDT on the SCCM 2007 server to the same version as MDT on the SCCM 2012 server, more information can be found here: http://www.ronnipedersen.com/2012/03/migrate-a-configmgr-2007-mdt-task-sequence-to-configmgr-2012/
    This might or might now work. Is it supported in case it works? No.

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, November 20, 2013 3:11 PM
  • Thanks Bert. I just saw your reply, in the meantime I used Torsten's tip and removed the MDT steps from the test task sequence, migrated and re-added them, thanks Torsten.

    Thursday, November 21, 2013 11:45 AM