- Side by Side upgrade only.
- great opportunity for a hardware refresh and start with a clean environment
- SCCM 2012 has a built in migration tool with reporting
- migration of object
- migration of client
- minimize WAN impact
- assist with flattening hierarchy Plan
- look at current design. Flatten hierarchy if necessary
- Ensure that SCCM 2007 SP2 is installed on all site servers and clients
- SCCM 2012 requires Sever 2008 (x64) and SQL 2008 SP1 (x64) (cumulative update 10)
- Deploy
- Install SCCM 2012 site
- configure Software update point and sync
- migrate
- Using the migration feature, specify top level site of the SCCM 2007 hierarchy
- once the connection is configured, SCCM 2012 will check SCCM 2007 every four hours to keep data accurate for migration jobs and retrieve package status from DP’s
- create one migration for each SCCM 2007 Primary site in your hierarchy
- Object Migration by type / instance
- cherry pick what object to migrate
- can migrate objects that where modified (on SCCM 2007) after they were migrated to SCCM 2012
- Collection Migration
- include all related objects for a collection and all object targeted to the members of the selected collection
- can exclude collections
- object supported for migration
- Collections (NOT empty ones)
- advertisements
- boundaries
- packages and virtual application placates
- software updates
- OSD
- settings
- Distribution Point sharing
- utilize existing SCCM 2007 DP’s in SCCM 2012 (only for objects that you have migrated)
- Can now (with SCCM 2012 Beta 2) upgrade 2007 DPs
- content of migrated packages converted to SCCM 2012
- can’t have any other site system roles on the DP. This will be addressed in the future
- need double the amount of disk space used to convert
- BDP’s can’t be upgraded
- Secondary Sites need to be uninstalled and re-installed to SCCM 2012
- consider replacing Secondary Sites with DPs
- All other site system roles need to be uninstalled and reinstalled to SCCM 2012
- Client Migration
- Clients retain execution history (so that advertisements don’t rerun!)
- minimum supported clients: XP SP2, Server 2003 SP2, Windows 7 and Server 2008 RTM
- Inventory does not get migrated
- Migration Reports are available through SSRS
- Packages can only be migrated as long as they are using a UNC for their source location
- OSD migration
- OS image / package
- task sequences
- drivers and packages
- Boot images are NOT migrated
- SCCM Client installation package is NOT migrated
- DCM migration
- CI’s and Baselines are migrated as a new version in SCCM 2012
- ability to import Config Packs
- Other object that can be migrated
- Software metering rules
- Search and Admin folders
- Reports
- Reports must be manually exported to RDL files.
- SSRS is the only reporting mechanism