Information Technology Reference
In-Depth Information
■
Deployments
■
Deployment packages
■
Templates
■
Software update lists
■
Operating system deployment:
■
Boot images
■
Driver packages
■
Drivers
■
Images
■
Packages
■
Task sequences
■
Desired configuration management:
■
Configuration baselines
■
Configuration items
■
Asset Intelligence customizations
■
Software metering rules
The following objects cannot be migrated from a Configuration Manager 2007 R2 hierar-
chy to a Configuration Manager 2012 R2 hierarchy:
■
Queries
■
Security rights and instances for the site and objects
■
Configuration Manager 2007 reports from SQL Server Reporting Services
■
Configuration Manager 2007 web reports
■
Client inventory and history data
■
AMT client provisioning information
■
Files in the client cache
Once the data gathering process is complete, you configure migration jobs to migrate
specific objects to the Configuration Manager 2012 R2 environment. You should only migrate
Configuration Manager clients after all objects that the client uses have been migrated. For
example, you might have an advertisement for a program that is deployed to a custom col-
lection that contains a specific client. Migrate the advertisement, program, and the custom
collection before migrating the client.
MORE INFO
MIGRATION TO CONFIGURATION MANAGER
You can learn more about migrating to System Center 2012 R2 Configuration Manager at
the following address:
http://technet.microsoft.com/en-us/library/gg681981.aspx
.
