Application Migration intelligently automates the migration of applications during a Configuration Manager OS deployment. Using migration rules (defined by an administrator), previously installed applications can be reinstalled, upgraded or replaced with an alternative during an OS deployment task sequence.

These rules can include usage criteria, allowing you to choose to only install previously installed applications if they were being used, or perhaps replace a rarely used application with a less costly alternative. This functionality enables applications to be actively rationalized during an OS migration exercise, standardizing on products and versions and reclaiming unused software.

Application Migration is implemented as a consumer on the SLA platform and a custom Configuration Manager task sequence step. The SLA platform provides inventory data from Configuration Manager, normalized through the 1E Catalog, that it uses to determine the applications installed and used on each computer.

The 1E Application Migration task sequence step is added to an existing OS Deployment Task Sequence. This step calls an Application Migration API to return a list of Configuration Manager Applications and Packages that need to be installed, based on the source computer's inventory and applicable Application Migration rules. The Applications and Packages are installed using the standard Configuration Manager Install Application and Install Package steps, each configured to install based on dynamic variables defined in the 1E Application Migration step. For details, please refer to Using Application Migration in a task sequence.

This 2.5.200 maintenance release contains the following enhancements:

The 2.5.100 maintenance release contained the following enhancements:

  • Support for TLS 1.1 and 1.2
  • Support for changes made in SLA Platform v3.3.

The 2.5 main release introduced the following features: