Version: 1



A list of all the platforms supported by Application Migration and the software required to allow Application Migration to be installed and work correctly.

Because Application Migration is an application on the Tachyon platform, the list of Supported Platforms for Application Migration is identical to the Tachyon platform. Application Migration only requires the Tachyon Master Stack to be implemented.

The Application Migration Task Sequence step requires PowerShell v4 or greater (included in Windows 8 and later).

The Application Migration 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.

On this page:

Tachyon Server Components


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

Please refer to 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 setup requires PowerShell 2.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
  • IIS 8.5

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
  • .NET Framework 4.7
  • .NET Framework 4.6.2
  • .NET Framework 4.6.1
  • .NET Framework 4.6

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:

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


Latest version of:

  • Google Chrome
  • Internet Explorer 11
  • Microsoft Edge
  • 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.

Tachyon Portal



Latest version of:

  • Google Chrome
  • Internet Explorer 11
  • Microsoft Edge
  • Mozilla Firefox

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

Please review Known issues: Using Tachyon.

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

Required by all Application Migration features. The Tachyon Platform 5.2 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 Platform 5.2
  • Tachyon Platform 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.2
  • 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.1
  • Shopping 6.0
  • Shopping 5.6

System Center Configuration Manager connector

The list below shows the versions of Configuration Manager supported by Tachyon 5.0. Please refer to Tachyon 5.0 - 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
  • SCCM CB 1810