CEP Configuration Manager 2012 Migration (2)

While taking part of the first wave of the CEP sessions, the Migration subject was already be part of the program. Today as part of the rerun of the CEP, Migration is again on the program for today. Let’s see today if again Eric Ormar shows us some new Configuration Manager Beta2 features.

News from the Configuration Manager product team:

  • Prerelease documentation is on Technet
  • Beta Feedback is also open for CEP members, so submit your feedback! :)
  • Next meeting May 4, is about Application Management

In the last CEP Summary about the Migration subject, I fortgot to mention the Configuration Manager 2012 Migration approach. Because of the redevelopment of Configuration Manager it isn’t possible to perform an in-place upgrade. That is one of the reasons why Microsoft invested lots of money and time to develop the out of the box side by side migration scenario. As mentioned in the earlier blog Migration is a real feature in Configuration Manager 2012.

The current prerequisites to be able to migrate Configuration Manager 2007 to Configuration Manager 2012 are:

  • SCCM 2007 SP1
  • For SCCM 2012; Windows Server x64, SQL Server 2008 (SP1 & CU 10)

Five new reports are added for migration reporting:

  • Clients in exclusion list
  • Dependency on a Configuration Manager 2007 collection
  • Object Migration Job Properties
  • Object Migration Jobs
  • Object failed to migrate

A new feature in Configuration Manager 2012 Beta2 is that you can Migrate objects again that are already migrated but maybe changed in Configuration Manager 2007

The SQL Database is renamed from SMS_<sitecode> to CM_<sitecode>

The next CEP session will have to following subjects:

  • Application Management part 1 and 2
  • Application Package Migration
  • 4th topic Q&A session with Microsoft SCCM program managers

Now topics like Configuration Manager SDK and Forefront Endpoint Protection will come up later this year.

Comments

 
Comments

Trackbacks for this post

Leave a Reply
*