Summary

Information that will help you design and plan the implementation of Application Migration in your organization.

Options for using Application Migration

To install migrated applications and packages in the Refresh and Replace OS Deployment scenarios, Application Migration provides a custom action that must be added to your task sequences to supplement the Install Application and Install Package actions. 

You can use these actions in your own task sequences, as described in Using Application Migration in a task sequence, and deploy them using Software Center or other means.

You can further simplify your processes and end-user experience by using 1E Shopping self-service features, where users use the Shopping web portal to start their own OS upgrades and migrations. The Wizards allow users to see a list of applications that are currently installed and the corresponding applications that will be installed as a result of applying the defined Application Migration rules. 

In each case:

  • For users requesting a self-service OS migration from the Shopping Web:
    • they cannot choose the applications to reinstall during a self-service OS migration
    • if you previously used the AppMapping feature and have migrated to Application Mapping, users will see a list of their previously shopped for apps in My Software
  • For administrators shopping on behalf of others:
    • on the Reinstall tab, the option to choose specific application to be reinstalled on machines is not available
    • on the Select New Apps tab, only applications that come with the new OS are listed and the option to select additional applications as part of this deployment is not available
    • OSD mapping rules and OSD machine mapping details are not available

If you want to use Application Migration with self-service OS deployment, please refer to the Shopping 6.0 - Integrating with Application Migration page in the Shopping documentation.

On this page:

Preparing Tachyon 5.1

Upgrading

Application Migration 3.1 requires Tachyon 5.1 and is not supported on SLA Platform 3.3 or Tachyon 4.1 or 5.0.

If you are currently using SLA Platform 3.3 for Application Migration 2.5, you will need to upgrade SLA Platform to Tachyon 5.1 before upgrading Application Migration.

If you are currently using Tachyon 4.1 or 5.0 for Application Migration, you will need to upgrade to Tachyon 5.1 before upgrading Application Migration.

Currently installedOption

If you have none of the following already installed:

  • SLA Platform 3.3
  • Tachyon 4.1
  • Tachyon 5.0

Install Tachyon 5.1 first, then install Application Migration 3.1. 

Please refer to:

If you are using Application Migration 2.5 on SLA Platform 3.3 and now want to upgrade to Application Migration 3.1.

Upgrade your existing SLA Platform 3.3 to Tachyon 5.1 first, then upgrade Application Migration to 3.1. 


Please refer to Tachyon 5.1 - Preparation and Tachyon 5.1 - Upgrading Tachyon for details on preparing for and upgrading SLA Platform 3.3 to Tachyon 5.1.

If you are upgrading SLA Platform 3.3 to Tachyon 5.1, when configuring Website Configuration in Tachyon setup, you should use the same host header and port numbers for HTTP and HTTPS as the current SLA Platform settings. For example, if SLA Platform was installed with the default settings (HTTP on port 8080, HTTPS on 8443), you should set the HTTP Port to 8080 and HTTPS Port to 8443 in the Website Configuration page of the Tachyon Setup Wizard. If a Host Header was used for SLA Platform, ensure the same host header is used for Tachyon.

This will ensure your existing Application Migration Task Sequence steps and Shopping integration settings will continue to work after the upgrade. If SLA Platform was configured to use HTTPS it is likely that you will need to generate a new Web Server certificate for Tachyon that meets the additional requirements of Tachyon, please refer to Tachyon Preparation - Web Server Certificate for more information.

Tachyon Setup 5.1 includes 1E Catalog 2.0. Tachyon Setup will only upgrade 1E Catalog if the server has an earlier version, otherwise the same or later version of 1E Catalog is not changed.

AI Powered Auto-curation

This is a new feature introduced in Tachyon 5.0.

Using the AI Powered Auto-curation feature you'll be able to increase the total amount of normalized software in your Inventory repositories. This is done using AI that integrates with the inventory consolidation process. By using AI your organization will benefit from significant numbers of normalized software and a reduced manual effort needed to normalize software.

For details of additional hardware requirements please refer to AI Powered Auto-curation.

If you want to upgrade to Tachyon 5.1  AND are already using

Application Migration 3.0 on Tachyon 5.0

OR

Application Migration 2.5.200 on Tachyon 4.1

Upgrade to Tachyon 5.1 first, then install Application Migration 3.1.

Please refer to:

AI Powered Auto-curation

This feature was introduced in Tachyon 5.0.

Using the AI Powered Auto-curation feature you'll be able to increase the total amount of normalized software in your Inventory repositories. This is done using AI that integrates with the inventory consolidation process. By using AI your organization will benefit from significant numbers of normalized software and a reduced manual effort needed to normalize software.

For details of additional hardware requirements please refer to AI Powered Auto-curation.


The Web Service used by Application Migration is provided by the Platform web application of the Tachyon website. This is configured by default to use Windows Authentication and its clients do not need to provide client certificates.