Wally Mead presents a plan for migrating from Configuration Manager 2007 to Configuration Manager 2012 R2. The plan includes verifying the existing 2007 environment is ready, preparing the new 2012 environment, mapping the 2007 hierarchy, sharing distribution points, migrating objects, clients, and distribution points, and finally cleaning up migration data. The migration process will take time but involves mapping the hierarchies, migrating collections and associated objects, upgrading clients, and converting distribution points before removing references to the 2007 site. Cireson can assist with Configuration Manager migrations, upgrades, and health checks.

1. Date: July 16th, 2014
Name: Wally Mead
Leaving the Dark Ages: Migrating from
Configuration Manager 2007 to Configuration
Manager 2012 R2

2. Agenda
 CiresonValue Proposition
 Verifying that the existing environment is ready for migration
 Preparing the new environment
 Mapping the source hierarchy
 Sharing distribution points
 Migrating objects
 Migrating clients
 Migrating distribution points
 Cleaning up
 Let’s GetYou Current 

3. TheCiresonValue Proposition
Experts
We are 100% focused on System Center. It’s all we do. Period.
Consulting Services™
System Center implementations, upgrades, & health checks. Delivering world class value to the business. Plain and simple.
Cireson Store™
Best-in-breed apps designed to complement, enhance, and optimize the System Center platform that perfectly align with your needs.
Custom Built Apps and Features
Do you log an enhancement request with Microsoft Support or Cireson?
We can help with adding additional functionality to meet your exact needs. We’re the experts.
Training
SystemCenter training help to maximize the solution and your career.
Your Community
Microsoft, System CenterAlliance, http://scsm.us/, myITforum,Think HDI, & itSMF.

4. VerifyingThat the Existing Environment is Ready
 Verify that the Configuration Manager 2007 is a supported version for migration
 Must be service pack 2 (build 6487.2000)
 The R2 or R3 add-ons do not matter for migration
 Understanding what can, and can’t, be migrated
 Most of your objects can be migrated
 The migration process won’t migrate reports, queries, security configuration
 However there are manual processes to migrate custom reports and queries
 You don’t want the security stuff – role-based administration is way cooler and easier to use 
 Remote distribution points with no other site roles can be migrated
 Distribution points with any other roles on them cannot be migrated
 The one exception is a secondary site can be migrated to a Configuration Manager 2012 DP
 Clients supported by Configuration Manager 2012 can be migrated
 Windows XP SP2/3 and newer
 Of course, you should be offWindows XP by now 

5. Preparing the New Environment
 Must stand up a new Configuration Manager 2012 environment as no in-place upgrade is available
 Preferably Configuration Manager 2012 R2  however migration works from Configuration Manager 2007
to Configuration Manager 2012 RTM, SP1 or R2
 Try to collapse the number of sites
 The preference is to be running in a stand-alone primary site environment with no child sites
 That’s not always possible, however a very strong recommendation
 As a general rule, map site systems one-to-one
 Whatever site roles you have installed in Configuration Manager 2007, you will likely need in Configuration
Manager 2012
 Roles that no longer exist in Configuration Manager 2012:
 Server locator point – functionality added to the management point
 PXE service point – functionality added to the distribution point
 Reporting point – replaced by the reporting services point
 Ensure software update point metadata is synced the same as previously
 If not, won’t be able to migrate software update objects

6. Mapping theSource Hierarchy
 This establishes a connection between the old and new infrastructures
 Map from the Configuration Manager 2007 central site to theConfiguration Manager 2012 primary
site (or CAS if applicable)
 Need to configure two accounts:
 One to connect to the source SMS Provider
 One to connect to the source Configuration Manager site database
 This will ‘discover’ all objects from Configuration Manager 2007 that can be migrated to Configuration
Manager 2012
 It does not migrate any objects
 The Migration Dashboard will display available objects and clients

7. Sharing Distribution Points
 As part of the mapping process, you can configure to share distribution points
 A shared distribution point allows Configuration Manager 2007 clients, as well as Configuration
Manager 2012 clients, to access content on the same distribution point
 This is still a Configuration Manager 2007 site system, which means you cannot add new Configuration
Manager 2012 content to it
 This also implies that Configuration Manager 2012 clients can only use a shared distribution point to access
migrated content
 All distribution points can be shared – branch DP, shared DP, standard DP
 Caveats:
 Sharing distribution points shares “all” distribution points
 You can’t pick and choose which ones to share
 Sharing creates boundaries and boundary groups in Configuration Manager 2012 automatically
 These are required to allow Configuration Manager 2012 clients to find the shared distribution points

8. MigratingObjects
 After data gathering has completed, you can start object migration
 Two primary types of migration jobs:
 Collection migration
 This migrates collection definitions and objects associated with/assigned to the collection(s)
 Likely will be the majority of migration jobs created
 Object migration
 This is the manual selection method of objects you want to migrate
 Can migrate all OSD objects, all of “John’s” objects, etc.
 In either job type, many configuration settings to configure
 A few are unique to the job type
 Migration is not a one-time task
 It will take time to migrate everything desired to be migrated
 May need to ‘re-migrate’ some objects after modification in Configuration Manager 2007

9. MigratingClients
 You can start migrating clients at any time, however usually will be after object migration has completed, at
least for the collection that the client is a member of
 Migrating clients essentially uninstalls the Configuration Manager 2007 client and reinstalls the
Configuration Manager 2012 client
 Maintains client information so that it does not re-run previously run advertisements
 You can use any client deployment methods you want to migrate clients
 Software distribution is a very popular client upgrade/migration method
 Point to Configuration Manager 2012 client installation binaries
 This process will take time to complete, as you may have hundreds, or thousands, of clients
 Likely not a single weekend task
 Recommendation – pre-install .NET Framework 3.5 or later prior to client migration
 Configuration Manager 2012 clients require it, and it takes ~20 minutes to install and reboot

10. Migrating Distribution Points
 Once you have the clients migrated, you can migrate any desired distribution points
 Migrating a distribution point maintains the content, and converts it to the content library
 Must have enough disk space (roughly twice the shared content size)
 The old SMSPKGx$ share is cleaned up after migration
 Must be a stand-alone distribution point
 Can’t have any other site system roles installed, not even a PXE Service Point
 The one exception is a secondary site which can have all of its normal roles installed
 Once migrated, the distribution point is removed from the Configuration Manager 2007 site
 That means it is no longer accessible by Configuration Manager 2007 admins or clients
 Now new Configuration Manager content can be distributed to the migrated distribution point

11. CleaningUp Migration Data
 Now that you have successfully migrated all appropriate:
 Collections
 Objects
 Clients
 Distribution points
 You can clean up the migration data
 Stop data gathering
 Clean up migration data
 This removes all references to the Configuration Manager 2007 site from Configuration Manager 2012
 This does NOT remove any migrated objects, collections, clients or distribution points
 Start the process over for any Configuration Manager 2007 child primary sites that contain objects owned by
the child site that you want to migrate
 Repurpose the old Configuration Manager 2007 hardware

12. Summary
 Migration is not a hard process to complete, just time consuming
 Verify that the existing environment is ready to migrate
 Prepare the new environment
 Map the source hierarchy
 Share distribution points
 Migrate objects
 Migrate clients
 Migrate distribution points
 Clean up
 Pretty simple – now go do it! Leave the dark ages and join us in the here and now 

13. Cireson can help withConfiguration Manager!
 Cireson can help yourConfiguration Manager needs by aligning with the
following initiatives:
 Configuration Manager 2007 or 2012 health checks
 Configuration Manager 2007 to 2012 migrations
 Configuration Manager 2012 R2 upgrades
 Configuration Manager 2012 full implementation deployments
 System Center full upgrades or full implementation deployments
 We’re here to help, contact Cireson at team@cireson.com

14. @teamcireson
We’re here to help
CiresonTeam
team@cireson.com
Tel: 855-871-1232