PKI Blog

In Part 1 we discussed the requirements overview on preparing for a migration and in Part 2 we covered the types of objects that are available for migration and the exclusions. In this final write up in the series we will go through the process using the migration utility that has been hyped up by Microsoft within Configuration Manager 2012.

In Part 1 of this blog series I presented an overview of the requirements for preparing a migration from Configuration Manager 2007 to 2012. With that information in hand I believe that you should have a general understanding of the pre-requisites necessary to begin your migration process.

Migration Objects

We’re going to cover the types of objects that can be migrated and how they are translated to Configuration Manager 2012. Bulleted below are all of the objects that can be migrated from ConfigMgr 2007 to ConfigMgr 2012.

As we all wait in anticipation for Configuration Manger 2012, there are a number of concerns that present themselves from an administrator’s perspective. One of those primary concerns, and the topic of this post, is the lack of upgrade path from SCCM 2007. At first glance it seems like a show stopper as companies may balk at a whole new infrastructure while already having one already in place for SCCM 2007. However, as Microsoft has made giant strides forward in terms of Systems Management and Hierarchy Simplification with ConfigMgr 2012, they have also reduced the pains of migration immensely. With the release of ConfigMgr 2012 RC some of you may be gearing up for testing, with that in mind the first part of this three part blog will highlight the requirements for preparing a migration along with any caveats and information pertaining to the migration process.