SCCM 2007 to 2012 R2 Migration why

A common answers from SCCM administrator for migration to SCCM 2007 to SCCM 2012.

As an IT administrator or technology lead you should look for migrating from SCCM 2007 to SCCM 2012

or higher versions if any of the below mentioned technologies are in your IT blue print. In addition, the

System Center Configuration Manager team of your organization would find the some of the features of

SCCM 2012 or higher versions are extremely handy in daily operations:
Deploying Windows 8 / 8.1 or Windows Server 2012 / R2 are available with System Center

Configuration Manager 2012 R2
Additional support for Unix, Linux, Apple, Android, and Nokia mobile devices will assist to enable a

BYOD environment

System Center Configuration Manager 2012 allows one to flatten the infrastructure, instead of having multi-tier hierarchy of Primary and Secondary Servers, significantly decreasing the management

Overhead

The new state-based application model replaces the conventional configuration manager package and programs, incorporating dependencies and requirements for more granular software distribution.

User device affinity is introduced, a method of associating a user with one or more devices

Software distribution in Configuration Manager 2012 is primarily user-based; applications are targeted to the user rather than the device
System Center Configuration Manager 2012 bring an in-built enterprise portal that allows for self

Service provisioning of applications
the new role-based administration feature flattens the complex hierarchies once required to isolate access to Configuration Manager Features
Assignment of client agent settings, inventory collection, and remote control settings by collection offers increased flexibility in configuration
Ability to “inject” new windows updates into existing WIM files used for operating system deployment by leveraging Component-Based Servicing.

The Desired Configuration Management client feature has been enhanced as Compliance

Settings, allowing for both identification of non-compliant systems and automatic remediation if desired

SCCM 2007 to SCCM 2012 Migration Target Objects

Administration

Discovery

Boundaries

Central site

Primary Site Server

Secondary Site Server

Client Settings

Security and Permission

Software Library

Software Packages

Virtual Application Packages

Operating System Boot Images

Operating System Driver Packages

Operating System Drivers

Operating System Images

Operating System Install Packages

Task Sequences

Software Update Deployment Packages

Software Update Deployment Templates

Software Update Lists

Assets and Compliance

Collections

DCM Configuration Baselines

DCM Configuration Items

Asset Intelligence Catalog

Asset Intelligence Hardware Requirements

Asset Intelligence Software List
Software Metering Rules

 

 

In System Center Configuration Manager 2012, you can migrate data from a supported

Configuration Manager Source hierarchy (SCCM 2007) to your destination hierarchy (SCCM 2012 R2). When you migrate data from a source hierarchy (SCCM 2007), you access data from the site databases that you identify in the source infrastructure (SCCM 2007 Infrastructure) and then transfer that data to your current environment (SCCM 2012). Migration does not change the data in the source hierarchy (SCCM 2007), but instead discovers the data and stores a copy in the database of the destination hierarchy (SCCM 2012)

 

Below is a list of best practices that one should follow before planning for the migration. This list is just a high level overview and not an exhaustive list.

 

·         SCCM 2012 Infrastructure should be designed and implemented

·         Security scopes should be created and designed

·         The current SCCM 2007 environment must be cleaned up and remove all unnessory objects that do not need to migrate

·         Remove application and driver packages that have local directory source code locations

·         Remove collections that are not used and Mixe of collection like devices and Users

·         Cleanup blank collections

·         Cleanup collections that have both users and systems

·         Resolve any overlapping boundaries

·         It is recommended to test the migration in QA or Dev environments before proceeding to the Production environment

·         The new feature called “Side by Side Migration” allows to migrate objects from Configuration Manager 2007 to new Configuration Manager 2012 automatically. Some of the key features of the Side by Side

Migration as follows:

·         Maximize the reusability of X64 bit hardware

·         Migrate Operating system Deployment Objects such as boot media, task sequence, packages, drivers etc.

Migrate Configuration Manager 2012 Objects

·         Migrate packages and programs in to the new Application Model ,i.e New application Model