You can migrate software update objects, such as software update packages and software update deployments.

To successfully migrate software update objects, in your Configuration Manager 2012 hierarchy, you must first deploy an active software update point and synchronize it with Windows Server Update Services (WSUS) before you run migration.

Use the following table to help you plan the migration of software update objects to Configuration Manager 2012.

You can migrate Configuration Manager 2007 software distribution packages and programs and virtual applications, such as Microsoft Application Virtualization (App-V), to Configuration Manager 2012. When you migrate content, it is the compressed source files that migrate to Configuration Manager 2012.

Packages and Programs

Virtual Applications

When you migrate App-V packages, they are converted to applications in Configuration Manager 2012, and you must create a deployment for each App-V package that you migrate.

Important
If you migrate a previously migrated Configuration Manager 2007 App-V package to Configuration Manager 2012, the migration fails because virtual application packages do not support the overwrite migration behavior. In this scenario, you must delete the migrated virtual application package from Configuration Manager 2012, and then create a new migration job to migrate the virtual application.

Advertisements

You can migrate advertisements from Configuration Manager 2007 to Configuration Manager 2012. If you upgrade a client, it retains the history of previously run advertisements to prevent the client from rerunning migrated advertisements.

Note
You cannot migrate advertisements for virtual packages. This is an exception to the migration of advertisements.

You can migrate the following Configuration Manager 2007 operating system deployment objects:

• Operating system images and packages. The source path of boot images are updated to the default image location for the Windows Administrative Installation Kit (Windows AIK) on the Configuration Manager 2012 site.
  
  

  Note
  To successfully migrate image files, the computer account of the SMS Provider server for the Configuration Manager 2012 central administration site must have read permission to the image source files of the Configuration Manager 2007 Windows AIK location.

• Task sequences. After you migrate a task sequence that contains a reference to a client installation package, you must update the task sequence to reference the Configuration Manager 2012 client installation package.
  
  
• Drivers and driver packages.
  
  
• Client installation packages, which are migrated, are not converted to Configuration Manager 2012 client installation packages.
  
  

You can migrate Configuration Manager 2012 configuration items and configuration baselines.

Note
Uninterpreted configuration items are not supported in Configuration Manager 2012. You cannot migrate or import these. For information about uninterpreted configuration items, see “Uninterpreted Configuration Item” in .

You can import Configuration Manager 2007 Configuration Packs to Configuration Manager 2012. The import process automatically converts the Configuration Pack to be compatible with Configuration Manager 2012.

When you migrate boundaries from Configuration Manager 2007 to Configuration Manager 2012, each boundary from the source site migrates at the same time and is added to a new boundary group that is created in Configuration Manager 2012. Each automatically created boundary group is enabled for content location and not for site assignment. This prevents overlapping boundaries for site assignment and also helps to keep Configuration Manager 2007 clients from incorrectly assigning to a Configuration Manager 2012 site.

If you configure a shared distribution point, any Configuration Manager 2007 boundaries that are associated with that distribution point are automatically migrated. A new read-only boundary group is created for each shared distribution point. If the boundaries for the distribution point change in Configuration Manager 2007, during the next data gathering cycle, the boundary group is updated with these changes.

You cannot migrate Configuration Manager 2007 reports to Configuration Manager 2012. Instead, use SQL Server Reporting Services Report Designer to export reports from Configuration Manager 2007, and then import them to Configuration Manager 2012.

Note
Due to schema changes for reports in Configuration Manager 2012, test each report that you import to ensure it functions as expected.

For information about reporting, see Reporting in Configuration Manager 2012.

By default, you maintain your search folder and administrative folder structures for objects and collections when you migrate to Configuration Manager 2012. However, in the Create New Migration Job Wizard, on the Settings page, you can configure a migration job to not migrate the organizational structure for objects by clearing the checkbox for this option. The organizational structures of collections are always maintained.

You can migrate your Asset Intelligence customizations to Configuration Manager 2012. There are no significant changes to the structure of Asset Intelligence customizations in Configuration Manager 2012.

You can migrate your software metering rules to Configuration Manager 2012. There are no significant changes to software metering in Configuration Manager 2012.

Concepts