Summary

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

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

Application Migration 3.1 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:

Accounts needed to install Application Migration

Installing Application Migration on Tachyon 5.1

The user installing Application Migration on Tachyon 5.1 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:

    • Component Viewers
    • Permissions Administrators
    • Provider Configuration Administrators
    • Schedule 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.1, please refer to Tachyon 5.1 - 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.

Service Accounts

Details of Tachyon service accounts are included in Tachyon 5.1 - Requirements: Service accounts.

The SQL Login that is used by the Tachyon Server web applications and services depends on whether the SQL Server is remote from the Tachyon Server or is local, as described in the following table:

Installation scenarioService account SQL Login
Tachyon Server is remote from SQLThe computer account of the remote Tachyon Server. For example ACME\ACME-TCN01$
Tachyon Server and SQL are localThe local network service account, NT AUTHORITY\NETWORK SERVICE

Before upgrading Tachyon, or installing or upgrading Consumer applications like Application Migration or AppClarity, the SQL Login must be granted the following rights to support Database Snapshot of the Catalog and SLA databases, to restore them if an error occurs:

  • dbcreator rights on the SQL database instance hosting the 1E Catalog database
  • dbcreator rights on the SQL database instance hosting the SLA databases

During installation, the Tachyon Setup will  always :

  • attempt to create the SQL Login
  • grant it db_owner  permission on each of the Tachyon databases
  • remove the  db_owner  permissions when installation is completed.


Accounts needed to use Application Migration

Tachyon Platform uses Role-based Access Control to associate users with the tasks that they are required to perform. The Application Migration Administrators role is the only role associated with Application Migration. Other platform roles are required in order to complete some post-installation setup and ongoing management of the platform necessary for Application Migration to function but not considered part of the day-to-day operation of an Application Migration administrator.

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 original 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.

If you upgraded SLA Platform 3.3 to Tachyon 5.1, 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.

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

Platform administrator roles

These are Tachyon 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 is a Tachyon platform application and has a dependency on certain platform components, such as Users, Connectors and optionally Management Groups, Tasks associated with these components would typically be performed by a platform administrator (a user with the Global Administrator role). In smaller organizations, or organizations only using the Tachyon platform for Application Migration, it is likely that the same one or two people will be responsible for managing all aspects of the platform as well as managing Application Migration. In this scenario it is likely that those users would be assigned the Global Administrator role in the Tachyon platform. Other organizations may be using several Tachyon platform applications and may want to restrict the number of users that have the Global Administrator role. The following Tachyon security roles will be required as a minimum to complete the post-installation tasks outlined in Getting started with Application Migration.

  • Application Migration Administrators
  • Connector Administrators
  • Inventory Administrators
  • Management Group Administrators
  • Permissions Administrators
  • Schedule Administrators

Refer to Tachyon 5.1 - Users page for details on how to add users and assign security roles in the Tachyon platform.

Application Migration Administrators role

These are Tachyon users who can use the Application Migration application for day-to-day operation

In order to use Application Migration, users must be added and assigned the Application Migration Administrators role in the Tachyon platform. This role is added to Tachyon platform when Application Migration is installed, so you will need to install Application Migration first, then add users and assign them to the Application Migration Administrators role as required.

Alternatively, you can create your own custom role, which must have the following permissions assigned as a minimum.

NameTypePermissions
ConnectorConnectorExecute.
Process logProcess logRead.
Repository: InventoryRepository: InventoryRead, Write, EvaluateManagementGroups, Populate.
InventoryInventoryRead.
Inventory: AssociationInventory: AssociationRead, Write, Delete.
Repository: Application migrationRepository: Application migrationRead, Write, Delete, Archive, Populate.

Task Sequence step user

This is the account specified in the Application Migration Task Sequence step used to connect to the Application Migration API (one of the SLA Provider API). It must be a Tachyon user, but it does not require any specific roles to be assigned.

It can be either a dedicated user account or the Configuration Manager Network Access Account.

Supported Platforms

Tachyon Server components

This version of Application Migration requires Tachyon Platform 5.1. Only the Tachyon Master Stack is required, a Response Stack is not required unless you also want to use Tachyon's real-time features. Because Application Migration is an application on the Tachyon platform, the list of Supported Platforms for Application Migration is identical to Tachyon Platform 5.1.

CategoryProductNotes

Server OS

  • Windows Server 2019
  • Windows Server 2016

For more detail, please refer to Requirements: Server requirements.

Only 64-bit server OS are supported. The server must be domain-joined.

This version of Tachyon requires the server OS to be English because of a known issue with certain regional settings.

This list is automatically updated to show only those OS versions in mainstream support by Microsoft, and therefore supported by 1E. However, the following OS continue to be supported as exceptions to help customers with their migration to the latest OS:

  • Windows Server 2012 R2.

Please refer to Constraints of Legacy OS regarding end of mainstream support.

For Microsoft product lifecycle details, please refer to https://support.microsoft.com/en-us/lifecycle/search.

Please refer to https://1eportal.force.com/s/support-for-msft-rapid-release-cycle for details of which Current Branch versions are supported by 1E products, and known issues regarding specific versions.

SQL Server and SQL Server Analysis Services (SSAS)

  • SQL Server 2019
  • SQL Server 2017
  • SQL Server 2016 SP2

For more detail, please refer to Requirements: SQL Server requirements.

Standard and Enterprise editions of these versions of SQL Server and SQL Server Analysis Services (SSAS) are supported.

SQL Server 2016 RTM is not supported due to some issues, which are resolved by SP1.

Microsoft requires you to use the Enterprise edition of SSAS if you use third-party business intelligence products such as Power BI to connect directly to the cube. You would normally only do this if you want to build a dashboard with the exact preset dimensions that are in the cube, which provides faster UI navigation. However, you can use any edition of SSAS if you want to create a custom dashboard by connecting to the database instead.

A SQL Server database instance is required for the following databases:

  • 1ECatalog
  • ActiveEfficiency (optional)
  • SLA-BI (optional - required for Patch Success)
  • SLA-Data
  • SLA-Integrate
  • SLA-Shared
  • TachyonExperience (optional - required for 1E Experience)
  • TachyonMaster
  • TachyonResponses

SLA databases

Tachyon Setup can install the above databases on separate SQL Server instances, however SLA-Data, SLA-Integrate, and SLA-Shared must exist on the same instance.

A SQL Server Analysis Services (SSAS) instance installed in Multidimensional mode is required for SLA Business Intelligence and 1E Experience.

SLA Business Intelligence

SLA Business Intelligence (BI) is required for the Patch Success application.

The BI installer creates the following:

  • A database called SLA-BI on the SQL Server database instance.
  • A MOLAP cube called SLA-BI on the SSAS instance.
  • A linked server for the SLA databases to get data from the SLA-BI database and then from the SLA-BI cube.
  • A linked server for the SLA-BI database to get data from the SLA databases.
  • A datasource definition used by the SLA-BI cube to connect to the BI database.

If the SLA databases, BI database, or SSAS instance for BI, are on different SQL Servers then the BI installer enforces the use of a SQL login on each instance. If they are on the same SQL Server then the installer gives you a choice of using integrated security (domain user account) or a SQL login.

However, if you are installing all the components from Tachyon Setup instead of their individual installers, then you are not given the choice. Tachyon Setup always uses integrated security. Contact 1E for support if your scenario requires the above mentioned databases to be on different SQL Servers. This affect different servers, not different instances.

1E Experience

1E Experience creates the following:

  • A database called TachyonExperience on the SQL Server database instance.
  • A MOLAP cube called TachyonExperience on the SSAS instance.

All SQL Server instances must be configured with the following:

  • A case-insensitive, accent-sensitive collation which is SQL_Latin1_General_CP1_CI_AS by default,
  • Allow remote connections to this server enabled.

All SQL Servers should be configured with the SQL Server Browser service running in order for the BI installer to select from a list of instances.

All SQL Servers must have SQL Server 2012 Native Client installed, in order to support linked server and datasource connections. This is included in the Client Tools Connectivity feature that SQL Server Setup normally installs by default. See Preparation: If TLS 1.0 is disabled.

SQL Server Management Studio is required to review the configuration and edit settings in 1E database tables.

If installing SQL Server locally, note:

  • SQL Server 2016 and 2017 require .NET Framework 4.6 which requires KB2919355 on Windows Server 2012 R2
  • SQL Server 2016 and 2017 setup requires PowerShell 2.0
  • SQL Server 2019 setup requires .NET Framework 4.6.1 and PowerShell 3.0.

For latest information about SQL Server prerequisites, please refer to MSDN: Hardware and Software Requirements for Installing SQL Server.

ActiveEfficiency Server requires Distributed Transaction Coordinator (MSDTC) to be enabled and configured on each of the SQL Servers used by:

  • ActiveEfficiency database
  • Configuration Manager site database - specified in the Nomad Sync settings during installation of ActiveEfficiency. This would normally be the CAS in a multi-site hierarchy, or the Primary Site in a single-site hierarchy.

MSDTC is a feature of Windows Server and is used to track of transactional processes, usually over multiple resource managers on multiple computers. MSDTC ensures that the transactions are completed and can be rolled-back if any part of the process fails. Nomad Sync uses MSDTC to perform complex queries on Configuration Manager and ActiveEfficiency data. For example, to retrieve computers targeted with Nomad Pre-cache policies and Nomad Dashboard data.

For details of how to configure MSDTC on SQL Servers, please refer to Preparation: MSDTC for ActiveEfficiency.

Microsoft System Center Configuration Manager

Not applicable.

Tachyon Server components have no dependencies on Configuration Manager, other than the SCCM Connector as described in Connectors below.

Use the links below for other components that use Configuration Manager:

Web Server
  • IIS 10

See Preparation: Windows Server roles and features for details about required Web Server roles and features.

Other Software

  • Visual C++ 2013 Redistributable
  • .NET Framework 4.8
  • .NET Framework 4.7.2
  • .NET Framework 4.7.1

See Preparation: Windows Server roles and features for details about required .NET Framework roles and features. To know supported combinations of OS and .NET Framework, please refer to: https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies.

  • Windows Server 2012 R2 has .NET Framework 4.5.1 installed by default. You will need to upgrade to one of these supported versions.
  • Windows Server 2016 has .NET Framework 4.6.2 installed by default.
  • Windows Server 2019 has .NET Framework 4.7.2 installed by default.

Tachyon Server installer includes and automatically installs the redistributable package for Visual C++ 2013. The Tachyon Coordinator (licensing module on the Master Stack), and Tachyon Switch (on Response Stack) are written in C++ using Visual Studio 2013 and therefore require Visual C++ 2013 runtime (x64); other server components use .NET Framework.

SQL BCP is required by the Export All feature described in Exporting data from Tachyon Explorer, and must be installed on each Tachyon Response Stack server (specifically the servers which have the Tachyon Core installed). BCP uses ODBC, which requires Microsoft ODBC Driver versions 13.1 and 17 and Visual C++ 2017 Redistributable to be installed first. Please refer to Preparation: SQL BCP for more detail.

PowerShell is required by Tachyon installer during installation.

Browsers

Latest version of:

  • Google Chrome
  • Microsoft Edge (Chromium)
  • Mozilla Firefox

A browser is not a prerequisite for installation of Tachyon Server, but is required to use and administer it. Administration is performed via the Tachyon Portal and can be on a remote computer.

These browsers are supported on all OS platforms which the browser vendor supports.

Please review Known issues: Using Tachyon.

Microsoft legacy browsers

Support has been withdrawn for Internet Explorer 11 and legacy Microsoft Edge (non-Chromium version). 1E has taken this decision for new releases that are expected to remain in support by 1E beyond March 2021 when Microsoft Edge goes end of life and August 2021 when Internet Explorer 11 goes end of life. We recommend you use Google Chrome, Firefox or Microsoft Edge Chromium browser.

System Center Configuration Manager connector

The list below shows the versions of Configuration Manager supported by Tachyon 5.1, please refer to Tachyon 5.1 - System Center Configuration Manager connector for detailed prerequisites and configuration.

  • SCCM CB 2103
  • SCCM CB 2010
  • SCCM CB 2006
  • SCCM CB 2002
  • SCCM CB 1910
  • SCCM CB 1906
  • SCCM CB 1902

1E Client

This version of Application Migration requires 1E Client 5.1 with the Shopping client enabled. Shopping client provides WSA features.

CategoryProductNotes
Windows OS

  • Windows Server 2019
  • Windows Server 2016
  • Windows 10 CB 21H1
  • Windows 10 CB 20H2
  • Windows 10 CB 2004
  • Windows 10 CB 1909
  • Windows 10 CB 1903
  • Windows 8.1

The zip for 1E Client for Windows is available for download from the 1E Support Portal .

Professional and Enterprise editions of Windows 10 are supported.

All versions are provided with 32-bit & 64-installers, and can be installed on physical and virtual computers.

This list is automatically updated to show only those OS versions in mainstream support by Microsoft, and therefore supported by 1E, and by 1E Client 5.1. However the following OS continue to be supported as exceptions to help customers during their migration to the latest OS:

  • Windows Server 2012 R2
  • Windows 7 SP1

Please refer to Constraints of Legacy OS regarding end of mainstream support.

For Microsoft product lifecycle details, please refer to https://support.microsoft.com/en-us/lifecycle/search.

Please refer to https://1eportal.force.com/s/support-for-msft-rapid-release-cycle for details of which Current Branch versions are supported by 1E products, and known issues regarding specific versions.

For installation guidance on Windows, please refer to Deploying 1E Client on Windows.

The following 1E Client features and modules are supported on Windows OS:

  • Tachyon client
  • Nomad client
  • PXE Everywhere Agent
  • Shopping client
  • Shopping WSA (workstation OS only, not server OS)
  • WakeUp client

Runtime libraries

  • .NET Framework 4.8

.NET Framework is required only for the following features of 1E Client:

  • The 1E Client User Interaction (UI) component of the Interaction module, which supports the notification and survey features
  • Windows Servicing Assiatant (WSA) feature of the Shopping client module, which supports OS deployment, upgrades and migrations

This list is automatically updated to show only those .NET Framework versions in mainstream support by Microsoft, and therefore supported by 1E, and by 1E Client 5.1.

For Microsoft product lifecycle details, please refer to https://support.microsoft.com/en-us/lifecycle/search.

Other Windows Software

  • Visual C++ 2013 Redistributable
  • PowerShell 3.0 (or later)
  • Nomad 7.0 (or later)

Visual C++ 2013 - 1E Client installer includes the redistributable package for Visual C++ 2013.

PowerShell - PowerShell is not a prerequisite for installation of the 1E Client.

PowerShell 3.0 or later (included in Windows 8.0 and later) is required if you are using Tachyon real-time features. Some Tachyon instructions use PowerShell (commands are embedded or scripts are downloaded).

PowerShell 4.0 or later (included in Windows 8.1 and later) is required if you are using Application MigrationThe Application Migration Task Sequence step executes in a Configuration Manager OS deployment task sequence after the new OS is installed. If you are deploying Windows 7 images, upgrade PowerShell in the image or install it using a task sequence step before executing the Application Migration step.

Nomad - 1E Client includes the Nomad client module (disabled by default) which optionally replaces the legacy Nomad Branch client. Tachyon real-time features can optionally use Nomad to download content (feature enabled by default).

For more details please refer to Design Considerations: Downloading Tachyon client content and Nomad integration .

Non-Windows OS

macOS

  • macOS Catalina 10.15.1
  • macOS Mojave 10.14
  • macOS High Sierra 10.13

Linux

  • CentOS 8.1
  • Debian 10.4
  • Fedora 32
  • Red Hat Enterprise Linux 7.1
  • Red Hat Enterprise Linux 8.1
  • SUSE Linux Enterprise 15.1
  • Ubuntu 18.04

Solaris

  • Solaris 11.3

1E Client supports only Tachyon features on non-Windows devices.

Other versions of these non-Windows OS should work but have not been tested by 1E.

The 1E Client for non-Windows zip is available for download from the 1E Support Portal, and includes 1E Client packages for the following architectures:

  • Linux variations on Intel 64-bit platforms
  • Solaris on Intel 64-bit and SPARC platforms

Also included in the download are 1E Client packages for the following legacy Linux distributions:

  • Fedora 21
  • openSUSE Leap 42.1

1E Client packages for other Linux distributions can be requested, including Raspbian for Raspberry Pi.

For Solaris, the following specific libraries are required, but are usually installed by default:

  • libcurl
  • zlib

For installation guidance on the following OS, please refer to:

For installation guidance on other non-Windows OS, please contact 1E.

Mobile OS

Android

N/A

1E Client supports only Tachyon features on non-Windows devices.

Other versions of these mobile OS should work but have not been tested by 1E.

The 1E Client for Android zip is available for download from the 1E Support Portal, and includes 1E Client packages for the following architectures:

  • Android ARM


Other Non-Windows Software

  • Bash
  • Perl

Bash and perl are required for installation of 1E Client on all non-Windows OS, with the exception of the 1E Client for Android which is available from the Google Play Store.

Tachyon instructions support the use of Bash scripts on all supported non-Windows OS.

To see if an Instruction requires a Bash script, look in its Instruction Definition XML file for Bash script resources defined under the <Resources> tag. Bash is the preferred choice when developing custom instructions for non-Windows OS.

There are slight differences between OS implementations of Bash, particularly on the Mac. Therefore 1E recommends testing custom Bash scripts on each supported OS.

Microsoft System Center Configuration Manager Client

  • SCCM CB 2103
  • SCCM CB 2010
  • SCCM CB 2006
  • SCCM CB 2002
  • SCCM CB 1910
  • SCCM CB 1906
  • SCCM CB 1902

The following client features work with these versions of Configuration Manager on Windows computers:

  • Tachyon client - instructions used by Tachyon Configuration Manager Console extensions
  • Nomad client - all Nomad features

  • PXE Everywhere Agent - N/A
  • Shopping client - N/A
  • Wakeup client - 1E WakeUp Policy Refresh and REFRESHONSUBNETCHANGE

Configuration Manager is not a prerequisite for installation of the 1E Client, and except for above features, the 1E Client, its features and modules, have no dependency on Configuration Manager.

Tachyon, Nomad, WakeUp and Application Migration have Configuration Manager Console extensions which are available separately.

This list is automatically updated to show only those Configuration Manager versions in mainstream support by Microsoft, and therefore supported by 1E, and by 1E Client 5.1.

For Microsoft product lifecycle details, please refer to https://support.microsoft.com/en-us/lifecycle/search.

Please refer to https://1eportal.force.com/s/support-for-msft-rapid-release-cycle for details of which Current Branch versions are supported by 1E products, and known issues regarding specific versions.

(Microsoft System Center Configuration Manager is also known as Configuration Manager, ConfigMgr, Config Man, CM and SCCM among other names. Version names include 2012 and Current Branch or CB.)

PowerShell

PowerShell 4.0 or later (included in Windows 8.1 and later) is required by the Application Migration Task Sequence step. The step executes in a Configuration Manager OS deployment task sequence after the new OS is installed.

If you are deploying Windows 7 images, upgrade PowerShell in the image or install it using a Task Sequence step before executing the Application Migration step.

1E Companion Products

Supported versions of 1E companion products that Application Migration 3.1 features depend on.

Products and features that Application Migration depends onSupported versions of companion products
Tachyon

Required by all Application Migration features. The Tachyon 5.1 Master Stack installation is required with the System Center Configuration Manager connector enabled. The Tachyon Response Stack is only required if you will be using additional Tachyon real-time features outside of Application Migration.

  • Tachyon 5.1
1E Client

1E Client, with Shopping client enabled, needs to be deployed to devices if using Application Migration with 1E Shopping and Windows Self-service Assistant (WSA).

1E Client, with Tachyon client enabled, does not need to be deployed to devices unless Tachyon real-time features are required by other 1E applications.

  • 1E Client 5.1
  • 1E Client 5.0
  • 1E Client 4.1

Supported versions of 1E companion products with features that depend on Application Migration 3.1.

Products and features that depend on Application MigrationSupported versions of companion products
ShoppingSelf-service OS deployment integrated with Application Migration. Optional feature.
  • Shopping 6.0
  • Shopping 5.6

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.1, 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.