Skip to main content

1E 8.1 (on-premises)

Design Considerations

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.1 - Integrating with Application Migration page in the Shopping documentation.

Preparing Tachyon Platform

Application Migration requires Tachyon Platform .

Current status


Tachyon Platform is not installed.

Use Tachyon Setup to install Tachyon Platform. We recommend installing Application Migration at the same time, but you can install it later.

Please refer to:

You have an older version of Tachyon Platform and Application Migration already installed.

Use Tachyon Setup to install Tachyon Platform 8.1. You must choose to install Application Migration 8.1 at the same time.

Please refer to:

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

Upgrade your existing SLA Platform 3.3 to Tachyon Platform 5.2 first, then upgrade to Tachyon Platform.

When you perform each upgrade, ensure you also install Application Migration at the same time, using Tachyon Setup.

If you are using Nomad, then you must also review Upgrading Nomad, before upgrading Tachyon Platform. This is because Tachyon Platform 5.2 and later replaces ActiveEfficiency with Nomad Content Distribution.

When upgrading, you will need to consider the following choice to ensure your existing Application Migration Task Sequence steps and Shopping integration settings will continue to work after the upgrade.

  • Either modify your existing Task Sequences (TS)

  • Ensure the Tachyon Platform (Master Stack) website provides the same binding(s) used by existing TS.

The choice depends on which DNS Names you want to use. Please refer to DNS Names.

When Using Application Migration in a task sequence, your Application Migration TS step includes Web Server Base URL, which uses a server or DNS Name, and either HTTP or HTTPS.

Tachyon Platform 5.2 and later, allows you to specify an additional (alternate) HTTPS binding during Setup. Please refer to Website configuration.

By default, Tachyon setup creates the following bindings:


Default binding

What you can do during Setup


HTTP - Tachyon server name (eg. ACME-TCN01.ACME.LOCAL) - Port 80

You can change the port. For example change it to 8080 to match the default HTTP port used by SLA Platform 3.3.

If for any reason you want to keep HTTP port 80 for other purposes, you can manually add an HTTP binding to the website after installation.

If your TS uses a different host header, then you can specify this during Setup.


HTTPS - DNS Name (included in the web server certificate) - port 443

You can change the DNS Name and port, for example to 8443 to match the default HTTPS port used by SLA Platform 3.3.

We recommend you do not change this binding just for the benefit of Application Migration. This is because this binding is typically used by administrators to connect to the Platform website, and also for Tachyon clients if the server has Response Stack components (Switch and Background Channel).

If you do not wish to edit your TS then we recommend you use the Alternate HTTP binding during Setup, or manually create an additional HTTPS binding after installation.

Alternate HTTPS


HTTPS - DNS Name (included in the web server certificate) - port 443

You can optionally configure the Alternate HTTPS binding during Setup, for the TS to connect to.

This is the recommended choice if you do not wish to edit your existing TS. If you need to use the Alternate HTTPS binding for other purposes, then you can manually create an additional HTTPS binding after installation.

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 Web Server certificate for more information.


Tachyon Setup includes 1E Catalog , and expects Catalog to be installed on the Tachyon Platform server. If your existing SLA Platform system has a remote Catalog server, then you will need to consider relocating it. Relocation probably means changing your firewall and whitelist settings. Please refer to Requirements: Whitelisting connections to 1E Cloud.

AI Powered Auto-curation

This feature was introduced in Tachyon 5.x. 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.