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 Tachyon application and a custom Configuration Manager task sequence step. The Tachyon 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 the Application Migration API on the Tachyon Server 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.

New features in Application Migration 3.1

Features in the Application Migration 3.1.105 maintenance release:

  • Works with Tachyon Platform 5.2
  • No new features in this maintenance release.

Features in the main Application Migration 3.1 release:

  • Works with Tachyon 5.1
  • Improvements to upgrade rules to support scenarios where the currently installed software has a later version than the one listed in the upgrade rule - In versions prior to Application Migration 3.1, it was possible that upgrade rules had issues when the application they were trying to upgrade on the client devices were later versions than the ones they were trying to upgrade to.  To remedy these unpredictable and unwanted results, now if an upgrade rule tries to downgrade an application then it will be ignored. For more details please refer to Adding a rule to upgrade an application: What happens in upgrade scenarios where the currently installed version of the application is later than the target application?
  • Application and Package installation success has been improved  - this handles scenarios where the administrator has forgotten to check the Allow this application to be installed from the Install Application task sequence action without being deployed checkbox, which is a prerequisite for migrating an application. In practice, it was a common error for administrators to overlook this, which - in earlier versions - led to the Task Sequence failing. In Application Migration 3.1, if the administrator forgets to set the checkbox, a warning is now displayed that lets the administrator continue and Application Migration sets the option automatically. For more details please refer to Getting started with Application Migration: Auto Install for Configuration Manager Applications and Packages
  • Multiple exclusion of applications is now supported from the Installations page - please refer to Managing product exclusions.