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

The list of Supported Platforms for AppClarity 7.1 is identical to Tachyon 5.2 because AppClarity is a Tachyon consumer application.

1E will provide you with a Tachyon.lic license file that defines the products and features your Tachyon System is able to use, for how long, and how many devices it supports, this may be an evaluation or subscription license.

  • The license must be activated. Once activated, it may be used only by the Tachyon System that activated it.
  • Licenses can be renewed or updated, but if allowed to expire, then the affected products or features will not be usable.
  • For a new installation, the Tachyon Setup program will let you select the license file from any folder on disk.
  • For an existing installation, the license file is copied into the folder: %PROGRAMDATA%\1E\Licensing on your Tachyon Server.

For details of what the license file needs to contain, please refer to Design Considerations: License requirements for consumer applications.

On this page:

Supported Platforms


Server OS

  • Windows Server 2022
  • 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.

If TLS 1.0 is disabled, then please ensure you follow the steps in Preparation: If TLS 1.0 is disabled to add registry entries, for the 1E Catalog Update Service to successfully connect to the 1E Cloud Catalog.

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

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.

If you intend to integrate with third-party business intelligence products such as Power BI, you must install the Enterprise edition of SSAS as per their requirements.

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

  • 1ECatalog
  • ContentDistribution (optional - required for Nomad)
  • SLA-BI (optional - required for Patch Success)
  • SLA-Data
  • SLA-Integrate
  • SLA-Shared
  • TachyonExperience (optional - required for Tachyon 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 Tachyon 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.

Tachyon Experience

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

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

Distributed Transaction Coordinator (MSDTC) is not required. Prior to Tachyon Platform 5.2, MSDTC was required by the Nomad Dashboard feature of ActiveEfficiency, and had to be installed on SQL Servers hosting databases for ActiveEfficiency and Configuration Manager. This is not required by the Nomad app and Content Distribution, which has replaced ActiveEfficiency in Tachyon Platform 5.2 onwards.

Microsoft Endpoint Configuration Manager

  • SCCM CB 2111
  • SCCM CB 2107
  • SCCM CB 2103
  • SCCM CB 2010
  • SCCM CB 2006
  • SCCM CB 2002
  • SCCM CB 1910

Tachyon Platform uses Configuration Manager for the following optional apps and features:

Nomad provides the following Content Distrubution features for Configuration Manager:

The Nomad app requires the Content Distribution web service to synchronize with the Configuration Manager database. For standalone primary site environments, permissions are automatically assigned to the service account of Content Distribution's web application pool service (by default Network Service) using the ConfigMgr_DViewAccess localgroup native to Configuration Manager. For a CAS, this group is not created natively therefore additional steps are required to allow access. Please refer to Preparation: Microsoft Endpoint Configuration Manager preparation.

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
  • ASP.NET Core Framework 3.1
  • .NET Framework 4.8
  • .NET Framework 4.7.2

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 2016 has .NET Framework 4.6.2 installed by default.
  • Windows Server 2019 has .NET Framework 4.7.2 installed by default.

ASP.NET Core Hosting Bundle is required only for Nomad's Content Distribution component. It is not included with the Operating System, and must be downloaded and installed separately. If it not already installed, Tachyon Setup will attempt to automatically download version 3.1.11 and install it. Alternatively you can download it, or a later version, and install it yourself. For more detail please refer to Preparation: ASP.NET Core Hosting Bundle.

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
  • Microsoft Edge (Chromium)
  • Mozilla Firefox

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

The Portal and any API should be added as a trusted site. This is especially important when running scripts which may produce unexpected errors.

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.

1E Companion Products

Supported versions of 1E companion products that AppClarity 7.1 features depend on.

Products and features that AppClarity depends onSupported versions of companion products
1E CatalogRequired by all AppClarity features.
  • 1E Catalog (included in Tachyon Platfom)
TachyonTachyon powered inventory using the optional Tachyon connector and full Tachyon infrastructure.
  • Tachyon Platform 5.2
  • Tachyon Platform 5.1
AppClarity 5.2

Optional feature of AppClarity 7.1 to use its AppClarity 5.2 connector to migrate entitlements from AppClarity 5.2. Only requires the AppClarity 5.2 database, not the full AppClarity 5.2 infrastructure.

  • AppClarity 5.2.0

Supported versions of 1E companion products with features that depend on AppClarity 7.1.

Products and features that depend on AppClaritySupported versions of companion products


The following table shows the supported versions of software used by the Tachyon out-of-box connectors.



  • ServiceNow Jakarta release

Please refer to the ServiceNow connector page for prerequisites.

SCCM (Microsoft System Center Configuration Manager)

  • SCCM CB 2111
  • SCCM CB 2107
  • SCCM CB 2103
  • SCCM CB 2010
  • SCCM CB 2006
  • SCCM CB 2002
  • SCCM CB 1910

Please refer to the System Center Configuration Manager connector page for prerequisites.


  • Tachyon Platform 5.2
Please refer to the Tachyon connector page for prerequisites.


  • VMware PowerCLI 11.1.0

VMware PowerCLI 11.1.0 ( must be installed on the Tachyon Master server (where the SLA Integrate Services Agent service is hosted) before you can configure and use the vCenter connector. Earlier or later versions of PowerCLI are not supported and may cause errors. VMware PowerCLI is freeware and was previously known as vSphere PowerCLI.

VMware PowerCLI supports multiple versions of VMware vCenter Server. For details, please refer to the VMware compatibility matrix using the following link:

Please refer to the vCenter connector page for configuration details.