1. Moving to Configuration Manager Current Branch
#ITDevConnections

2. Agenda Migration From Configuration Manager 2007
Upgrading or Migrating From Configuration Manager 2012
Staying Current with Current Branch
#ITDevConnections

3. Understanding Configuration Manager Current Branch
Naming and Versions
#ITDevConnections

4. Getting on the Same Page
The official product name is “System Center Configuration Manager”
No date, no version, just the name
Most references now add “current branch” after the name
Need to also know the build, as there are three production builds currently available
1511, 1602 and 1606
YYMM the build was finished, not necessarily availability
#ITDevConnections

5. Migrating From Configuration Manager 2007
Essentially the same process as migrating from ConfigMgr 2007 to ConfigMgr 2012
#ITDevConnections

6. Moving off ConfigMgr 2007
Configuration Manager 2007 is no longer within mainstream product support
Hasn’t been for over two years now
You should really consider getting off this old platform
And no reason to consider moving to Configuration Manager 2012
Mainstream support for it ends in July of 2017
#ITDevConnections

7. Migrating to Current Branch
So your real option is moving to Configuration Manager current branch
You cannot upgrade, however can perform a migration
Migration allows you to keep your administrative objects you want, and ignore those that are obsolete
You could do a wipe-and-load if you want to start fresh with a completely clean environment, or maintain the same site code
#ITDevConnections

8. Migration Procedure
Ensure that you are running ConfigMgr 2007 SP2 (including R2/R3)
Stand up a brand new current branch environment
Install latest supported server OS and SQL Server version
Use current hardware
Consider hierarchy reduction (as in NO hierarchy 
Install 1511 with a new site code!
Most of the same site system roles
#ITDevConnections

9. Migration Procedure (2)
From the new site:
Map to the source (old site)
Discover objects on source site
Determine which objects to migrate
Create migration jobs
Enable Shared DPs
Upgrade clients
Upgrade Shared DPs
Migrate secondary sites to DPs
#ITDevConnections

10. Migration Demo

11. Upgrading From Configuration Manager 2012
Should you do in-place upgrade or migrate?
#ITDevConnections

12. Considering an Upgrade
You can perform an in-place upgrade to Current Branch from:
Configuration Manager 2012 SP1/SP2
Configuration Manager 2012 R2/SP1
Generally is the recommended way to get to Current Branch
Very easy process, just like implementation of previous service packs (process will be covered soon)
#ITDevConnections

13. Considering Migration
You can perform a migration process to Current Branch from:
Configuration Manager 2012 SP1/SP2
Configuration Manager 2012 R2/SP1
Usually considered when:
You want to swap hardware
You want to reduce/eliminate a hierarchy (chance to finally get rid of that CAS you were forced to install)
You want to update your server’s OS or SQL Server versions
#ITDevConnections

14. Moving off ConfigMgr 2012
If you choose to migrate, the process is the same as just covered in the ConfigMgr 2007 section:
Stand up a brand new current branch environment
Install latest supported server OS and SQL Server version
Use current hardware
Consider hierarchy reduction (as in NO hierarchy 
Install 1511 with a new site code!
Most of the same site system roles
#ITDevConnections

15. Migrating from ConfigMgr 2012
From the new site:
Map to the source (old site)
Discover objects on source site
Determine which objects to migrate
Create migration jobs
Enable Shared DPs
Upgrade clients
Upgrade Shared DPs
Migrate secondary sites to DPs
#ITDevConnections

16. Upgrading to Current Branch
Verify that your OS and SQL Server versions are supported
Only Windows Server 2008 R2 and SQL Server 2008 R2 and newer are supported
Verify current environment is healthy:
Site systems and components are OK
No inbox backlogs
Clients are communicating
Deployments are working
#ITDevConnections

17. Upgrading to Current Branch (2)
Back up current environment
Prepare for upgrade:
Remove MP replicas
Uninstall AMT OOB and System Health Validator roles
Remove SUP NLBs
Disable maintenance tasks
Run Prereqchk.exe
Run TestDBUpgrade
Initiate upgrade from the top
#ITDevConnections

18. Preparing for Upgrade and initiating the upgrade

19. Completing the Upgrade
Verify the upgrade status
Upgrade log
Site system and component status
Reports run
Usually, to complete the upgrade
Upgrade remote consoles
Upgrade child sites
Upgrade clients
#ITDevConnections

20. Before Considered Completed
You don’t want to remain on 1511, however must upgrade to it
Let the Updates and Servicing feature discover, download, and prepare 1602 and 1606
Will be discussed later in this presentation
Will happen automatically with an online Service connection point site system and Internet access
#ITDevConnections

21. Before Considered Completed (2)
Update your top level primary site to 1606
Could be 1602 if preferred, however no reason to install it
Once your primary site is 1606, then go back and complete the remainder of the upgrade
Remote Consoles
Any child sites (hopefully you got rid of them)
Clients
#ITDevConnections

22. Completing the upgrade

23. Keeping Current Branch Current
Once you get to Current Branch, how do you keep it up to date?
#ITDevConnections

24. Staying Current with Current Branch
Once you’ve upgraded to 1511, you now want to upgrade it 
The Updates and Servicing feature is the way to do this
Will automatically discover, download, and prepare new builds for you
You get to install whatever builds you want
Can skip builds
Installed version supported for one year
#ITDevConnections

25. Staying Current with Current Branch
Once you’ve upgraded to 1511, you now want to upgrade it 
The Updates and Servicing feature is the way to do this
Will automatically discover, download, and prepare new builds for you
You get to install whatever builds you want
Can skip builds
Installed version supported for one year
#ITDevConnections

26. Initiating a Site Update

27. Summary You really want to be on Current Branch
Tons of great features to take advantage of
See the “What’s New in Configuration Manager Current Branch” presentation for details
Migrate from Configuration Manager 2007
Migrate or in-place upgrade from Configuration Manager 2012
Stay current with Current Branch
#ITDevConnections

28. WIN Rate This Session Now! Tell Us What You Thought of This Session
Rate with Mobile App:
Be Entered to
WIN
Prizes!
Tell Us What You Thought of This Session
Select the session from the Agenda or Speakers menus
Select the Actions tab
Click Rate Session
Rate with Website:
Register at
Go to
Select this session from the list and rate it
#ITDevConnections