Hello, I am wondering if anyone has any advice or links to some kind of migration path/roadmap when migrating from SCCM 2007 to 2012. All of the documentation for installing/configuring SCCM 2012 I have found deals exclusively with doing it in a lab environment and starting from scratch. In our environment we are currently running SCCM 2007 and we have that on its own server, the SQL stuff on it's own server and Active Directory on third server. So I am wondering exacty which components I need to install for SCCM 2012 (our install came with the following ISOs - App Controller, ConfigMgr, DataProtection Mgr Server, Operations Manager Server, Orchestrator Server, Service Manager Center, and Virutal Machine Manager Server) and how to go about installing SCCM 2012 when AD and SQL are already in production (on different servers). At this point, I am mostly worried about getting 2012 installed properly, as I have found some tutorials which seem to be usable for the actual migration of data between 07 and 2012.


0 Comments   [ + ] Show Comments


Please log in to comment

Community Chosen Answer


My advice, if you aren't 100% sure hire a consultant to come in for a few weeks and perform the migration.  You'll definitely spend some $$ but its better in the long term.  You really can't use any of your 2007 infrastructure for 2012.  So in a way you are kind of starting from scratch.  You'll need a new server, new DB, although its possible to re-use some distribution points (if setup correctly). 

There are some utilities out there to migrate your packages.  Personally I just used the migration as an excuse to clean out old apps, and rewrite a lot of them for the SCCM application model.  Hope that helps!

Answered 05/06/2013 by: bretthexum
Yellow Belt

  • Thanks for the reply. Unfortunately I work for the gov and due to budget cuts we have NO money for stuff like that. However you pretty much answered my question. So I am going to be installing everything from scratch - new SQL server and all that. Now that I think about it, even migrating over patches is not necessary. Basically we just need SCCM 2012 connected to our AD and we can "start over" with the rest.
  • You are correct from what I have read, you have to do a SxS install and move over. A bit lame, but I guess it will be clean (:
  • Here is a question, if i use the Unified Installer for SCCM 2012 will I still be able to connect it to our current AD structure? Or maybe I shouldn't use the unified installer at all, I've read it's only for geared towards use in a lab / test environment only...
    • I don't think it matters either way. You'll be able to see AD in both. Personally I just install it piece by piece for clients... just to make sure things are working correctly. If something bombs in the unified installer it can be tough to see what actually failed.
Please log in to comment



Stumbled across this while looking for something else, lol. Hopefully helpful.


Answered 05/13/2013 by: rileyz
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity