Summary

Application Migration is implemented as an application that runs on the Tachyon 5.0 platform, which includes SLA and 1E Catalog components. The Tachyon 5.0 platform must be installed before installing Application Migration. Refer to Implementing Tachyon for more details.


Application Migration 3.0 requires Tachyon 5.0 and is not supported on SLA Platform 3.3 or Tachyon 4.1. If you are currently using SLA Platform 3.3 for Application Migration 2.5, you will need to upgrade SLA Platform to Tachyon 5.0 before upgrading Application Migration.

Please refer to Release notes for details of changes since Application Migration 2.5

Application Migration 3.0 Licensing

Application Migration is now licensed through the Tachyon Platform. You will require a Tachyon license file that includes Application Migration. Refer to License File in the Tachyon Requirements documentation for more information.


On this page:

Preparing Tachyon 5.0

Currently installedOption

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

Upgrade your existing SLA Platform 3.3 to Tachyon 5.0 first, then upgrade Application Migration to 3.0.
 
Please refer to Tachyon 5.0 - Preparation and Tachyon 5.0 - Upgrading Tachyon for details on preparing for and upgrading SLA Platform 3.3 to Tachyon 5.0.

If you are upgrading SLA Platform 3.3 to Tachyon 5.0, 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.

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.

This feature requires 1E Catalog 2.0. For details of additional hardware requirements please refer to AI Powered Auto-curation.

If you are already using Application Migration on Tachyon 4.1 and want to upgrade to Tachyon 5.0.

Upgrade to Tachyon 5.0 first, then install Application Migration 3.0.

Please refer to Tachyon 5.0 - Implementing Tachyon for details on preparing for and upgrading Tachyon 4.1 to Tachyon 5.0.

Refer to  Installation  for details on installing Application Migration 3.0.

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.

This feature requires 1E Catalog 2.0. For details of additional hardware requirements please refer to AI Powered Auto-curation.

If you have neither SLA Platform nor Tachyon 4.1 installed.

Install Tachyon 5.0 first, then install Application Migration 3.0. 

Refer to Tachyon 5.0 - Implementing Tachyon for details on preparing for and installing Tachyon 5.0 on the Tachyon server.

Refer to Installation for details on installing Application Migration 3.0.

Tachyon Setup 5.0 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.

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.

SQL Server

Application Migration installation and upgrade requires the SLA Platform service account to have the following role in SQL Server:

  • dbcreator on the SQL Server instance that hosts the SLA Platform databases

By default the SLA Platform service account is the Network Service account. Tachyon services, which include SLA Platform services, always uses the Network Service account.

If the databases are hosted on the SLA Platform (or Tachyon) server, grant this role to the Network Service account. If the databases are installed on a remote SQL Server, grant this role to the computer account of the SLA Platform (or Tachyon) server.

Accounts needed to install Application Migration

Installing Application Migration on Tachyon 5.0

The user installing Application Migration on Tachyon 5.0 needs the following permissions, it must:

  • Have local admin rights on the Tachyon server
  • Be an existing Tachyon user with a minimum of the following Tachyon roles:

    • Permissions Administrators
    • Instruction Set Administrators
    • Consumer Administrators.

    For a new installation of Tachyon, the only account that exists in Tachyon will be the installation account, which by default is assigned to the Tachyon roles listed above. You will need to add users and assign roles to them.

    When upgrading from SLA Platform, SLA users are migrated to Tachyon, but are not assigned to any roles. You will need to assign users to appropriate roles in Tachyon.

    For steps on viewing existing users and adding a new user in Tachyon 5.0, please refer to Tachyon 5.0 - Users page.

    When installing Tachyon or upgrading from SLA Platform, do not install Tachyon using an installation account that you also intend for using and administrating Tachyon and Application Migration. The Tachyon installation account is purposefully given limited capabilities which can't be easily edited later.

    A recommended workaround for this is to add the installation account to an AD security group, and then assign the security group to appropriate roles in Tachyon, for example Global Administrators.

Installing 1E Task Sequence Tools

The 1E Task Sequence tools are installed on the Configuration Manager site server, SMS provider and any devices on which the Configuration Manager console is installed. The user installing 1E Task Sequence Tools  needs the following permissions, it must:

  • Have local admin rights on the device you are installing on
  • Be a Full Administrative user in Configuration Manager.


Accounts needed to use Application Migration

Tachyon platform 5.0 introduces Role-based Access Control, which requires users to be assigned roles associated with the tasks that they are required to perform. The user that installed Tachyon (the Tachyon Installation Account) is assigned the Permissions Administrator role so can be used to add other users and assign roles to them, but you cannot add or change the roles assigned to the Tachyon Installation Account. It is therefore important to install Tachyon with an account that will NOT be using Application Migration (or any other Tachyon applications for that matter) after installation.    

There are three types of users that are involved in the setup and operation of Application Migration.

  • Platform Administrators - users who can manage users, connectors, management groups and other common components in the Tachyon platform. These users are typically set up after installing Tachyon platform and can be added at any time by other platform administrators (specifically users with the Permissions Administrators role) 
  • Application Migration Administrators - users who can use the Application Migration application for day-to-day operation
  • Task Sequence step user - the account used by the Application Migration step in a Configuration Manager Task Sequence to connect to the Application Migration web API.   

Refer to Application Migration roles for further details on setting up users to perform tasks in Application Migration and the Tachyon platform after installing Application Migration.

If you upgraded SLA Platform 3.3 to Tachyon 5.0, all previously defined users will be present in Tachyon, but will not be assigned any security roles. You will need to assign the appropriate roles after upgrading the platform.

Integrating Application Migration with Shopping

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

Networking

Firewall

PortTrafficNotesConfigurable
TCP 80 (HTTP)Inbound/OutboundUsed by the website hosting the SLA Operations Provider API for HTTP traffic.Yes, during installation.
TCP 443 (HTTPS)Inbound/Outbound

Used by the website hosting the SLA Operations Provider API for all HTTPS traffic. A web server certificate is required.

Yes, during installation.

Previous versions of the SLA Platform used port 8080 by default for HTTP communication. If you are upgrading from SLA Platform 3.3 to Tachyon platform 5.0, you should retain the port settings currently used by SLA Platform by defining the port on the Web Site Configuration page of Tachyon Setup.

For full details of communications, please refer to Communication Ports.