Choosing your platform: SLA Platform 3.3 or Tachyon 4.1

Application Migration is implemented as a consumer that runs on the Software Lifecycle Automation (SLA) Platform. The SLA Platform, including the 1E Catalog, must be installed before Application Migration. SLA has been incorporated into the latest releases of Tachyon, so you have a choice about which platform you want to install the latest version of Application Migration on: SLA Platform 3.3 or Tachyon 4.1.

You should only use Tachyon 4.1 if you specifically want to take advantage of its ServiceNow integration or use any of its other real-time features. Otherwise, you should use SLA Platform 3.3. While Application Migration 2.5.200 supports all Application Migration functionality when installed on Tachyon 4.1, it is an interim solution for customers that require Tachyon 4.1 immediately. Application Migration will only be fully integrated into Tachyon (and will then require Tachyon) with the release of Tachyon 4.2 and Application Migration 3.0, expected early 2020.

Please refer to Changes when using Application Migration 2.5.200 on Tachyon 4.1 for more details.

AppClarity 6.0 requires SLA Platform 3.3 and is not supported on Tachyon 4.1. If you are currently using SLA Platform for AppClarity 6.0, you will need to retain SLA Platform 3.3. In this case, install or upgrade Application Migration on the existing SLA Platform server, and if you require Tachyon 4.1 install it on a separate server, as described in Choosing Tachyon 4.1 below.

On this page:

Choosing SLA Platform 3.3

If you do not already have SLA Platform 3.3 installed, you will need to install that before installing Application Migration. If you have an older version of SLA Platform installed, you will need to upgrade to SLA Platform to 3.3 before installing or upgrading to Application Migration 2.5.200. Refer to the SLA Platform documentation for information about preparing for and installing or upgrading the SLA Platform.

Once SLA Platform 3.3 has been installed, you must install the latest SLA Platform 3.3 hotfix available at the 1E Support Portal before installing or upgrading to Application Migration 2.5.200.

For detailed instructions on installing Application Migration, refer to Installation.

For details on upgrading Application Migration, refer to Upgrading to Application Migration 2.5.200 on SLA Platform 3.3

Choosing Tachyon 4.1

If you require Tachyon 4.1 for real-time features, such as Explorer, Guaranteed State or ServiceNow integration, you have a few options:

Currently installedOption

If you are already using Application Migration on SLA Platform 3.3 and now want to introduce Tachyon 4.1.

Upgrade your existing SLA Platform 3.3 to Tachyon 4.1 then upgrade Application Migration to 2.5.200. This option may require additional resources on your existing SLA Platform server, but will simplify the ongoing maintenance and upgrade of the platform (Tachyon) in the future. This option is recommended.
 
Please refer to Tachyon 4.1 - Implementing Tachyon for details on preparing for and upgrading SLA Platform 3.3 to Tachyon 4.1.

If you are upgrading SLA Platform 3.3 to Tachyon 4.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 (refer to Tachyon Preparation - Web Server Certificate for more information).

Retain your existing SLA Platform 3.3 server and upgrade Application Migration to 2.5.200 on that server (indicated by the red dotted line in the diagram below), then implement a new server for Tachyon 4.1 (indicated by the blue dotted line in the diagram below). This option may be necessary if the existing SLA Platform 3.3 server is unable to accommodate the system requirements for Tachyon. It will require you to maintain SLA Platform 3.3 on the original server and Tachyon on the new server. The next release of Application Migration (v3.0, expected early 2020) will only be supported on Tachyon, so at that point you will need to migrate Application Migration to the Tachyon server.
 
Please refer to Upgrading to Application Migration 2.5.200 on SLA Platform 3.3 for details on upgrading Application Migration on the existing SLA Platform 3.3 server. This can be done independently of installing Tachyon on the additional server.
For details on preparing for and installing Tachyon 4.1 on the Tachyon server please refer to Implementing Tachyon.

Shared SQL Server

You cannot install the Tachyon 4.1 databases on the same SQL Server instance as the SLA Platform 3.3 databases. If you are installing Tachyon 4.1 in parallel with SLA Platform 3.3 and intend to use a shared SQL Server, you must install the Tachyon databases on a different SQL Server named instance on the shared server.

If you do not have SLA Platform 3.3 installed but already have Tachyon 4.1 installed, you can install Application Migration 2.5.200 on the existing Tachyon 4.1 server. Please refer to  Installation  for details on installing Application Migration 2.5.200.

If you have neither SLA Platform nor Tachyon 4.1 installed.

Install Tachyon 4.1 then install Application Migration 2.5.200. Refer to Implementing Tachyon for details on preparing for and installing Tachyon 4.1 on the Tachyon server. Refer to Installation for details on installing Application Migration 2.5.200.

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.

Once Tachyon 4.1 has been installed, you must install the latest Tachyon 4.1 hotfix available at the 1E Support Portal before installing or upgrading to Application Migration 2.5.200.

Tachyon Setup 4.1 includes 1E Catalog 1.2.0.303. 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.

Integrating Application Migration with Shopping

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

SQL Server

Application Migration installation and upgrade requires the SLA Platform service account has 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 SLA Platform 3.3

The user installing Application Migration on SLA Platform 3.3 needs the following permissions:

  • must have local admin rights on the SLA Platform server
  • must be an existing SLA Platform user

    For steps on viewing existing users and adding a new user in SLA Platform 3.3, please refer to SLA Platform 3.3 - Creating a new user.

    If you have just installed SLA Platform then the only account that exists in SLA Platform will be the Default web user specified during installation, which by default is the same as the SLA Platform installation account.

Installing Application Migration on Tachyon 4.1

The user installing Application Migration on Tachyon 4.1 needs the following permissions:

  • must have local admin rights on the Tachyon server
  • must be an existing Tachyon user with a minimum of the following Tachyon roles:

    • Permissions Administrators
    • Instruction Set Administrators
    • Consumer Administrators

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

    If you have just installed Tachyon, or upgraded from SLA Platform 3.3, then the only account that exists in Tachyon will be the installation account, which by default is assigned to the Tachyon roles listed above.

When upgrading from SLA Platform 3.3, users are not migrated to Tachyon.

When installing Tachyon or upgrading from SLA Platform, do not use a Tachyon 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.

Installing 1E Task Sequence Tools

The user installing 1E Task Sequence Tools needs the following permissions:

  • must have local admin rights on the computer
  • must be a Full Administrative user in Configuration Manager.

Install the Task Sequence Tools on the following systems:

  • The Configuration Manager Primary Site server. In a multi-site hierarchy, install it on the CAS and each primary site.
  • If any site has one or more remote SMS Providers, install it on each remote SMS Provider server
  • Any remote Configuration Manager console systems that are used to edit task sequences.

For steps on viewing existing users and adding a new user in SLA Platform 3.3, please refer to SLA Platform 3.3 - Creating a new user.

Accounts needed to use Application Migration

Types of user accounts

There are potentially three types of users required, which may be combined depending on the platform and other needs:

  • users of the Application Migration website
  • users of the SLA Platform or Tachyon website
  • a user required by the Credentials (for web service call) setting in the 1E Application Migration task sequence step

If a domain account is specified in the Credentials (for web service call) setting then its password must also be provided, therefore you should treat the account like a service account. If the setting is left blank then the step will use the Configuration Manager Network Access Account and knowledge of its password is not required. In either case, the account must be a defined as a user.

More information about the task sequence step is provided in Using Application Migration in a task sequence: Configuring the 1E Application Migration Task Sequence step.

SLA Platform

When Application Migration is installed on SLA Platform, then any user defined in SLA Platform will have full access to the Application Migration, SLA Platform websites, and can be used in the 1E Application Migration task sequence step. Best practice is for the user specified in the 1E Application Migration task sequence to be a user defined in SLA Platform only for that purpose (equivalent to a service account).

For steps on viewing existing users and adding a new user in SLA Platform 3.3, please refer to SLA Platform 3.3 - Creating a new user.

If you have just installed SLA Platform then the only account that exists in SLA Platform will be the Default web user specified during installation, which by default is the same as the SLA Platform installation account.

Tachyon 4.1

When Application Migration is installed on Tachyon, any user defined in Tachyon will have full access to the Application Migration, SLA Platform websites, and can be used in the 1E Application Migration task sequence step. Best practice is for the user specified in the 1E Application Migration task sequence to be a user defined in Tachyon only for that purpose (equivalent to a service account). The Application Migration users and Task Sequence user do not need to be assigned to any Tachyon roles. 

If Application Migration users also need to configure Tachyon connectors and repositories, then users must have the minimum of the following Tachyon roles:

  • Connector Administrators
  • Consumer Administrators
  • Inventory Administrators
  • Log Viewers
  • Management Group Administrators
  • Management Group Sync Initiators

When upgrading from SLA PLatform, users are not migrated to Tachyon.

When installing Tachyon or upgrading from SLA Platform, use a dedicated Tachyon installation account. The Tachyon installation account is purposefully given limited capabilities which can't be easily edited later.

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

Networking

Firewall

PortTrafficNotesConfigurable
TCP 8080 (HTTP)Inbound/OutboundUsed by the website hosting the SLA API (providers) for HTTP traffic.Yes, during installation.
TCP 8443 (HTTPS)Inbound/Outbound

Used by the website hosting the SLA API (providers) for all HTTPS traffic. A web server certificate is required.

Yes, during installation.

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