© 2012 Microsoft Corporation. All rights reserved.

Microsoft Confidential
System Center 2012 Configuration Manager
Concepts & Administration Workshop

Module 11: Migrating from Configuration Manager 2007

to System Center 2012 Configuration Manager

Microsoft Confidential
Conditions and Terms of Use
Microsoft Confidential
This training package is proprietary and confidential, and is intended only for uses described in the training materials. Content and software
is provided to you under a Non-Disclosure Agreement and cannot be distributed. Copying or disclosing all or any portion of the content
and/or software included in such packages is strictly prohibited.
The contents of this package are for informational and training purposes only and are provided "as is" without warranty of any kind, whether
express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, and non-
infringement.
Training package content, including URLs and other Internet Web site references, is subject to change without notice. Because Microsoft
must respond to changing market conditions, the content should not be interpreted to be a commitment on the part of Microsoft, and
Microsoft cannot guarantee the accuracy of any information presented after the date of publication. Unless otherwise noted, the companies,
organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association
with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred.

Copyright and Trademarks

© 2012 Microsoft Corporation. All rights reserved.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this
document. Except as expressly provided in written license agreement from Microsoft, the furnishing of this document does not give you any
license to these patents, trademarks, copyrights, or other intellectual property.
Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this
document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic,
mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
For more information, see Use of Microsoft Copyrighted Content at
http://www.microsoft.com/about/legal/permissions/
Microsoft®, Internet Explorer®, and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the United States
and/or other countries. Other Microsoft products mentioned herein may be either registered trademarks or trademarks of Microsoft
Corporation in the United States and/or other countries. All other trademarks are property of their respective owners.
Migrating from Configuration Manager 2007 to
System Center 2012 Configuration Manager

Lesson 1: Introduction

Microsoft Confidential
 Overview
No upgrade path
Maintain your investment using migration features

5 Microsoft Confidential
 Objective
After completing this lesson, you will be able to understand:
Migration benefits and concepts
Migration workflow

6 Microsoft Confidential
 Migration – Concepts
Source hierarchy
Source sites
Data gathering
Migration jobs
Client migration
Shared Distribution Points
Monitoring migration
Stop gathering data
Clean up migration data

7 Microsoft Confidential
 Migration - Workflow
Decom
Enab Migr Depl
missio
le ate oy n

1. Enable migration specifying a Configuration Manager 2007

source hierarchy
2. Enable Distribution Point sharing
3. Create migration jobs
4. Deploy migrated objects to Configuration Manager 2012
clients
5. Begin to upgrade and reassign clients to Configuration
Manager 2012 sites
6. In-place upgrade Configuration Manager 2007 distribution
points
7. Decommission Configuration Manager 2007 infrastructure

8 Microsoft Confidential
 Lesson Review
Is it possible to upgrade your Configuration Manager 2007
infrastructure to System Center 2012 Configuration
Manager?
During the migration period, are clients able to access
Configuration Manager 2007 shared content?

9 Microsoft Confidential
 Lesson Summary
In this lesson, you learned:
Migration Benefits
Migration concepts
Migration workflow

10 Microsoft Confidential
Migrating from Configuration Manager 2007 to
System Center 2012 Configuration Manager

Lesson 2: Migration Planning in System Center 2012

Configuration Manager

Microsoft Confidential
 Objective
After completing this lesson, you will be able to understand:
Prerequisites for migration
Administrator checklist for migration planning
Administrator checklist for hierarchy deployment prior to
migration
Administrator checklist for migration
Which objects to migrate
Migration jobs

12 Microsoft Confidential
 Prerequisites
Migration Operation Details
To configure, run, and monitor migration in the Role-based administration security role of Full
Configuration Manager console Administrator.
Supported Configuration Manager 2007 site version Only Configuration Manager 2007 sites with SP2 are
supported for migration

Data Gathering • Source Site SMS Provider Account: Read

permission to all source site objects required.
• Source Site SQL Server Account: Read and
Execute permissions to the source site database
required.
• TCP 445, TCP 135 and TCP 1433

Migrate Software Updates Must configure System Center 2012

Configuration Manager hierarchy with a SUP
Share distribution points At least one Primary site or the CAS must use the
same port numbers for client requests

Upgrade distribution point The Source Site Access Account configured to

gather data from the SMS Provider of the source site
must have site Delete permissions.
13 Microsoft Confidential
 Checklist for Migration Planning
Assess the current environment, network and AD topology
Review the functionality and changes in System Center
2012 Configuration Manager
Finalize your System Center 2012 Configuration Manager
hierarchy design
Map your hierarchy to the computers that you will use for
System Center 2012 Configuration Manager
Plan your object migration strategy
Plan your client migration strategy
Plan for inventory and compliance data
Plan for the completion of migration from the source
hierarchy

14 Microsoft Confidential
 Checklist for Hierarchy Deployment Prior to Migration
Identify the computers to use in the System Center 2012
Configuration Manager hierarchy
Create your System Center 2012 Configuration Manager
hierarchy
If you want to migrate information that is related to
software updates, configure a Software Update Point in
System Center 2012 Configuration Manager and
synchronize software updates
Install and configure additional site system roles in System
Center 2012 Configuration Manager
Verify site functionality

15 Microsoft Confidential
 Migration Steps
Configure Active Source Hierarchy
Configure Share Distribution Points
Create and run migration jobs to migrate objects and
collections to System Center 2012 Configuration Manager
Install System Center 2012 Configuration Manager client
Upgrade Configuration Manager 2007 Distribution Points
Complete migration
Clean up Migration Data

16 Microsoft Confidential
 Data Migration
Data you can migrate Data you cannot migrate
Collections Queries
Advertisements Security rights and instances for the
site and objects
Boundaries System Center Configuration
Manager 2007 reports from SQL
Server
Software distribution packages Reporting Services
Virtual application packages System Center Configuration
Manager 2007 web reports
Software Updates: Client inventory and history data
• Deployments
• Deployment packages
• Templates
• Software update lists
17 Microsoft Confidential
 Data Migration (continued)
Data you can migrate Data you cannot migrate

Operating System Deployment: AMT client provisioning information

• Driver packages
• Drivers
• Images
• Packages
• Task sequences
Desired Configuration Management: Files in the client cache
• Configuration baselines
• Configuration items
Asset Intelligence customizations Boot Images do not migrate however
boot image settings such as F8 and
bitmap will
Software metering rules

18 Microsoft Confidential
 Migration Jobs
Three types of migration job are available:
Migration Job Type Info
Collection Migration Migrate objects related to a selected
collection, and objects associated with
members of the collection. You can exclude
specific object instances when using the
collection migration job.
Object Migration Migrates individual objects that you select.
You select only the specific data that you
want to migrate.
Previously migrated object Migrates objects in the source hierarchy
migration previously migrated but updated in the
source ensure
Important: Before you migrate clients, hierarchy
objects that are used by clients have
migrated and that these objects are available in the System Center 2012
Configuration Manager hierarchy

19 Microsoft Confidential
 Migration Jobs (continued)
Create migration job(s) to migrate objects from
Configuration Manager 2007 to 2012 hierarchy
Can be run on a schedule if desired and repeated to pick
up objects that are changed in Configuration Manager
2007 hierarchy
Monitor progress in the UI
Migration Manager processes the job and logs results to
MigMCtrl.log
A .syn file in the migration manager inbox triggers a job to
run. The number of the syn file (e.g. 2.syn) indicates which
job is to run from the Mig_SiteInfo table

20 Microsoft Confidential
Demo

Microsoft Confidential
Migration Jobs (continued)

22 Microsoft Confidential
 Collection/Object Migration
Collection migration All related objects migration

Exclude related objects

migration

Empty Collection Folders

Top level Collection Folders

with criteria

Collection with
Users and Devices

Collection with reference

to a collection of a
different resource type

23 Microsoft Confidential
 Collection/Object Migration (continued)
Collections
Any dependent
packages/advertisements already
selected for migration
Specific objects can be excluded from a
collection migration job and that object
is added to an exclusion list
Exclusion lists are still available for
future migration jobs but not
automatically selected
24
Objects
Must select each object and object
instance that you want to migrate
Any objects that you do not add to the
migration list are not migrated but they
are not added to the exclusion list either
N/A
Microsoft Confidential
 About Previously Migrated Object Migration
Use “Objects modified after migration” option
Similar to object migration type except it only shows the
objects that have updated since they were migrated by a
previous job
Conflict resolution settings – New migration is configured
to overwrite previously migrated objects and you cannot
change this setting.

25 Microsoft Confidential
 Lesson Review
Are Client inventory and history data of Configuration
Manager 2007 client migrated?
If an object that you have already migrated to
System Center 2012 Configuration Manager is updated in
the Configuration Manager 2007 hierarchy, what kind of
actions do you have to do?
How many job types exist?

26 Microsoft Confidential
 Lesson Summary
In this Lesson, you learned:
Prerequisites of migration
About migration planning
Administrator checklist for hierarchy deployment prior to migration
Administrator checklist for Migration
Objects that you can and cannot migrate
Migration jobs

27 Microsoft Confidential
Migrating from Configuration Manager 2007 to
System Center 2012 Configuration Manager

Lesson 3: Migration Planning in System Center 2012

Configuration Manager-2

Microsoft Confidential
 Objective
After completing this lesson, you will be able to:
Migrate clients
Migrate content
Migrate objects
Monitor the migration

29 Microsoft Confidential
 Client Migration - Overview
After the migration, you can no longer manage that device
by using your Configuration Manager 2007 hierarchy
Ensure that the client’s operating system is supported and
meets minimum requirements
GUID and advertisement execution history are retained
Client cache, inventory and compliance data are not
retained

30 Microsoft Confidential
 Planning for Client Migration
Migrate collections and related objects before migrating
clients
Use SMSSITECODE=<sitecode> instead of AUTO option to
avoid conflict between two hierarchies
Compliance data - Recreated in the System Center 2012
Configuration Manager hierarchy when clients first send
information to their assigned site
Hardware inventory customizations cannot be migrated
You must import any Hardware Inventory customizations
to System Center 2012 Configuration Manager
independently from migration

31 Microsoft Confidential
 Planning for Content Deployment
Shared Distribution Points
Planning to upgrade Distribution Point in System Center
2012 Configuration Manager
Planning to upgrade Configuration Manager 2007
Secondary sites

32 Microsoft Confidential
 Shared Distribution Points
Management of Shared Distribution Points:
Cannot distribute Configuration Manager 2012 content to Shared DP
Configuration Manager client can only acquire migrated content from a
Shared DP
Cannot change boundaries of Shared DP within Configuration Manager
2012, clients will adhere to boundary policies set for the Shared DP in
Configuration Manager 2007
Dependent upon the Data Gathering process (default setting is 4 hours)
App-V cannot use Shared Distribution Points
Configuring and Enabling:
Per Primary site configuration (including any direct Secondary sites)
Cannot select individual DPs for sharing
Enable for each Primary site
No multi-select
Shared Distribution Points are viewed in Migration node

33 Microsoft Confidential
 ConfigMgr 2007 ConfigMgr 2012
1. Client requests
content location
2. Client downloads
Primary Site Primary Site content from DP or
Management Management Point shared DP
Point
3. 2012 client will
Shared Distribution Point NOT communicate
prior versions
Distribution Point

Distribution Point

1. Client requests
content location
2. Client downloads
content from DP

3. 2012 MP will
reject requests and ConfigMgr ConfigMgr
client will NOT 2007 Client 2012 Client
receive 2012 DP
locations

34 Microsoft Confidential
 Planning to Upgrade Distribution Points
In-place Distribution Point upgrade:
Upgrade is a migration job type
Allows ability to monitor upgrade and content
conversion
Allows ability to restart in failed cases
Content for migrated packages converted
into Configuration Manager 2012 content
library and single instance store
Supports *Branch, Server Share and
standard Distribution Points
Distribution Point upgrade wizard:
Allows for all deployment configurations as if using
Standard Distribution Point upgrade. Specify drive,
install IIS, etc.
Displays list of hosted migrated packages
Choose which Configuration Manager 2012 Primary
or Secondary site to host the upgraded Distribution
Point
Ensure no additional site system roles exist
If other roles are deployed, uninstall before upgrade
can be performed. SUP, SMP, or PXE will prevent the
DP upgrade executing

35 Microsoft Confidential
 Distribution Point Upgrade
Content
Configuration Manager 2007 content is preserved after upgrade (manual clean-up required)
Content conversion
Will copy between drives
Restart functionality in case of failed conversions

Platform support
Configuration Manager 2012 Distribution Points support client OS Vista SP2/Win7 (no WinXP
and no workgroup systems)
Configuration Manager 2012 Distribution Points can be x86 or x64

Migrating Branch DP’s

Only allow upgrade of supported Configuration Manager 2012 platforms
Upgrade current WinXP Configuration Manager 2007 BDPs to a supported operating system
(Win7).
Share Distribution Points with Configuration Manager 2012
Uninstall Configuration Manager 2007 client
Upgrade the Shared DPs to Configuration Manager 2012 Distribution Point

36 Microsoft Confidential
 Content Conversion During DP Upgrade

Package type Is converted? Must be redistbuted?

Boot Image No Yes

OS Image Yes No

App-V Yes No

Software Updates Yes No

Software Distribution Yes No

Important:
Please note that Boot Images can be migrated during normal migration process but
not converted during DP upgrade process

37 Microsoft Confidential
 Data Migration
Data you can migrate Data you cannot migrate

Collections/Advertisements Queries

Boundaries Security rights and instances

Software distribution/Virtual Reports from SSRS

packages

Software Updates Web Reports

OSD AMT client provisioning Information
DCM Files in the client cache
Asset Intelligence customizations Power Management settings

Software metering rules

38 Microsoft Confidential
 Objects Migration –Software Update

2007 2012

Software Update lists Software Update groups

Software update deployments Deployments and Update groups

Software update packages Software update packages

Software update templates Software update templates

Important:
Custom updates published with System Center Updates Publisher (SCUP) cannot be
migrated
Software update deployment that contains more than 500 updates cannot be migrated

39 Microsoft Confidential
 Package Conversion Manager

Feature pack download

Convert packages into applications
Applications provide additional user-centric
functionality (i.e. Application may contain different
deployment types – local installation of software
package, virtual application package, or a version of
application for mobile devices)

40 Microsoft Confidential
 Migrating to Configuration Manager 2012 Application
Model

Keep packages in
2012 (no app model)

Migrated
Packages &
Programs Convert to 2012
App Model

Rebuild applications
in 2012

41 Microsoft Confidential
 Monitoring the Migration
In the Configuration Manager console, in the Administration workspace on
the Migration node, you can monitor the migration actions

42 Microsoft Confidential
 Lesson Review
Is the cache client retained after the client migration to
System Center 2012 Configuration Manager?
When is a distribution point eligible to be a Shared
Distribution Point?

43 Microsoft Confidential
 Lesson Summary
In this lesson, you learned:
How to plan a Client migration
How to migrate content or share it with DP
What we can and cannot migrate
Monitoring the migration

44 Microsoft Confidential