Ok, I have got a new blog post, finally! 😉
This time I’ll explain how to migrate to the newest version of Configuration Manager 2012. In-place upgrade is not possible for the Configmgr 2007 to 2012. Configmgr 2012 has a built-in migration functionality. This functionality replaces the in-place upgrade of the existing Configuration Manager infrastructure. So, that means we have to use a site-to-site deployment. We have to create a new destination hierarchy.
Read this for more information. http://technet.microsoft.com/en-us/library/gg712991.aspx. Also handy which data you could migrate and which one not.
- Lab environment. (Simple hardware config, Pentium G620 with 32GB of RAM. ISCSI NAS with 1TB LUN)
- Windows Server 2012 Hyper-V
- DC01, Domain Controller Windows Server 2008 R2 (with the schema update from Configmgr2012 (it’s the same of Configmgr2007)
- SCCM2007, Windows Server 2008R2 with SQL 2005 SP4 and the necessary prerequisites. (ISS,BITS, WDS, WSUS and RDC, for more information check Windows-Noob.com: HowTo install Configmgr 2007)
- SCCM 2012, Windows Server 2008R2 (2012 is also possible in SP1) with SQL 2008 R2 SP2 CU2 (SQL 2012 is also possible) and the necessary prerequisites (check my blog how to install Configmgr 2012: Prerequisites)
- Enabled the PXE services on SCCM2007.
- I’m also using App-v (5.0) packages.
- Don’t use the same site code. Site code must be unique.
More information about the SCCM servers:
SCOM 2007 server: This one is standard installation, PXE is enabled for OSD. Configure it and test it. You have to add some clients, packages, OSD and software updates. OSD has to work, this means you have to use a client computer/vm for testing.
SCOM 2012 server: I have installed the standalone version. I don’t use a CAS and Child site. If you want a CAS and Child you can also follow this how to for migration. I have only installed SCCM 2012 SP1 and the roles, like de Software updates point and Endpoint protection Roles.
If you are using Hyper-V as a client, then you have to import the Hyper-V drivers in SCCM 2007 and add the necessary drivers in the Boot Image. These drivers are added in the Boot Image:
- Virtual Machine BUS
- Network adaptor
- Input (but I think this one is not necessary)
First you have to know is that SCCM 2012 uses only UNC. If you use local path locations in SCCM 2007 you have to edit the packages, driverpackages, and images to the correct UNC path before migrating to SCCM 2012. There is a handy tool to change this is easier. Check this site http://www.myitforum.com/myITToolbar/frame-click.asp?url=http://blog.coretech.dk/kea/updating-the-package-source-in-configuration-manager-2007/
Ok, let’s begin:
First go to the console of SCCM 2012 and go to Administration -> Migration. Beneath the folder Migration you have to right click on Specify Source Hierarchy.
Add the source credentials in the wizard. I’m using the administrator for SCCM. Also for the database.
After hitting the Ok button the gathering begins.
In a complex hierarchy you will install your top SCCM 2012 server (CAS) and connect that one to the SCCM 2007 Central Server to gather all necessary hierarchy info.
If you have more than 1 primary sites you will create an active source hierarchy for each SCCM 2007 site to the SCCM 2012 CAS to gather all info.
Secondary sites need to uninstall manually from the SCCM 2007 site. For installing a new secondary site in SCCM 2012 consider it if this still required. Maybe a Distribution Points (DP) role is enough as we can now throttle DP’s with SCCM 2012. Simplify hierarchy J
By default SCCM 2012 will check each 4 hours to keep the gathered data up-to-date.
If you receive an error maybe you have to turn off the firewalls on both servers, or configure the firewall. You have to use an inbound rule for all programs, any ports and remote IP address of the SCCM server. This must be on both servers.
The gathering is finished:
Right click on Migration Jobs in the menu beneath Migration and choose for Create Migration Job.
Follow the instructions in the wizard. Choose for a name and Job Type is Object Migrations.
Select the objects. I have select the most except to old versions of SCCM clients, hotfixes and boot images. Boot images are not necessary because of the new version of WAIK in 2012.
Change here the correct ownership if you have a complex hierarchy. For me was it simple, because I’m using only a standalone primary site.
Do the same for Collection migration.
After that you have the objects and collections in your new hierarchy.