This is a white paper that my buddy Sandeep Chadda and I wrote on upgrade strategy from SCCM 2007 to SCCM 2012. A quick over view of the white paper before you can download the rest of the document:
Executive Summary :
This document reviews the impact of
most of the aspects, objects, and features of System Center Configuration
Manager when migrated from legacy SCCM 2007 to SCCM 2012. As part of this
exercise, we assessed all components of SCCM by dividing them into 3
categories:
1.
Administration
2.
Software
Library
3.
Assets
and Compliance
We considered 104 use cases of SCCM spanned
across the 3 categories for the purpose of this white paper. A high level
summary of the components assessed is as follows:
SCCM Components
|
# of use cases
|
Successfully Migrated
|
Not Migrated Automatically
|
Migrated with Limited Capability
|
Administration
|
27
|
09
|
17
|
1
|
Software Library
|
39
|
22
|
15
|
2
|
Assets and Compliance
|
38
|
19
|
14
|
5
|
Total
|
104
|
50
|
46
|
8
|
Interpretation of the Data
·
Most
of the components of SCCM related with packages, collections, advertisements
etc. are successfully migrated automatically. These components will be migrated
from SCCM 2007 to SCCM 2012 as-is.
·
Some
of the components and aspects of SCCM such as site servers, SCCM roles,
maintenance tasks, SCCM Client Agents etc. need to be setup manually. There is
no migration path for these components.
·
in
addition, aspects such as boundaries, boundary groups, collection settings, and
boot media settings are migrated automatically however certain settings require
additional manual intervention
Based on the use cases reviewed, we
found that
·
48%
of the SCCM components migrated as-is automatically without any intervention
·
44%
of the SCCM components did not migrate at all
·
8%
of the SCCM components migrated successfully but manual interventions were
required
Link
