You can use the Application Migration pages to manage the migration of applications from one system, or one version of a system to another.
In this section
An outline of the steps you need to take after installing Application Migration to get you migrating applications through your OS Deployment Task Sequences.
On the Installations page you can view installed applications in your environment, see how frequently they're used, and whether migration rules exist. You can also create and modify migration rules and exclude applications you're not interested in.
- Adding a rule to retain an applicationA retain migration rule reinstalls exactly the same version of the application during the migration.
- Adding a rule to replace an applicationA replace migration rule replaces an application with an alternative. This is useful for standardizing on common tools such as file compression applications.
- Adding a rule to upgrade an applicationAn upgrade migration rule upgrades an existing application to a newer version.
- Viewing and resolving migration rule conflicts
Conflicts arising from having more than one migration rule for a computer belonging to more than one management group can be easily resolved before the migration takes place.
- Working offline on migration rules
You can export your installed applications to an Excel format file that can be worked on offline, with template columns that let you define new migration rules. Once you've finished defining the rules you can then import them back into Application Migration.
- Managing Configuration Manager association alerts
Application Migration users will see alerts on specific pages that identify orphaned applications - when one or more rules or applications in an application set reference Configuration Manager objects that no longer exist, or where the Configuration Manager association has been deleted.
Products can be excluded from consideration by Application Migration, helping you to focus on the important products and minimizing effort during the Application Migration workflow.
Before deploying the OS Deployment Task Sequence, you can preview the effect that Application Migration will have on the software installed on a device. This can be for existing or new build devices. This is done from Preview Device, where you can see the following menu items:
Post-migration application status for existing computers undergoing an in-place upgrade or a computer refresh.
Applications to be installed on new-build computers by Management Groups or device attributes.
A Role Based Application Set defines a set of applications that should be installed on a computer for a user performing a particular role, or perhaps working at a particular location.
- Managing Role-based Application Sets
You can add, edit and delete Role-based Applications Sets from the Role Based Application Sets page.
In some cases, when some applications are installed together, they need to be installed in a certain order. You can do this in Application Migration by adding applications that have specific installation order constraints to the Install Sequence.
The actual process of migrating applications is performed during an OS deployment task sequence in Configuration Manager.
Application Migration uses a custom task sequence action that calls an Application Migration API. The API gets a list of Configuration Manager Applications and Packages that need to be installed on a computer based on previously installed software titles (determined through inventory) and the migration rules applying to those titles.