Skip to main content

1E 8.1 (on-premises)

Windows Server requirements

You will need to provision one or more servers using the guidance provided here as the minimum specification.

For comprehensive guidance for CPU, RAM, disk volumes, and network connections, please refer to the Server sizing requirements page.Server sizing requirements

You will install each Tachyon Server using a wizard called Tachyon Setup . To make the process easier for installing Tachyon platform and its applications, the Tachyon Setup wizard aims to help you:

  • Prepare for a successful deployment of Tachyon platform and applications

  • Find online resources for Tachyon platform and applications

  • Check and configure prerequisites

  • Create the Tachyon Server certificate for use with the Tachyon Server website and the Tachyon Switch

  • Deploy selected components

  • Perform post-installation tasks, including configuring the components for interaction with each other

  • Running validation tests on the completed installation.

The correct choice of DNS Name(s) for your Tachyon Servers is perhaps the most fundamental decision you will make.

Server software




Server OS

  • Windows Server 2022

  • Windows Server 2019

  • Windows Server 2016

For more detail about configuration of servers, please refer to Windows 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 issues with certain regional settings.

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


This list shows only those OS versions in mainstream support by Microsoft, and therefore supported by Tachyon, and by 1E Client .

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

For Microsoft product lifecycle details, please refer to

Refer to Support for Microsoft Rapid-Release Cycle on 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 SP3

For more detail, please refer to 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 SP3.


Tachyon only supports AlwaysOn Availability Groups on SQL Server Enterprise Edition. Please refer to High Availability options for SQL Server for HA options and their requirements.


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

SLA Business Intelligence

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

Together, the SLA Platform and BI installers create 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 using Tachyon Setup instead of their individual installers, then you are not given the choice. Tachyon Setup always uses integrated security. Contact your 1E Account Team if your scenario requires the above-mentioned databases to be on different SQL Servers. This affects different servers, not different instances.

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 the latest information about SQL Server prerequisites, please refer to

Microsoft Endpoint Configuration Manager

  • MECM CB 2303

  • MECM CB 2211

  • MECM CB 2207

  • MECM CB 2203

  • MECM CB 2111

  • MECM CB 2107

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

Nomad provides the following Content Distribution features for Configuration Manager:

Nomad 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 Windows Server roles and features for details about required Web Server roles and features.

Runtime libraries

  • Visual C++ 2013 Redistributable

  • Visual C++ 2015-2019 Redistributable

  • ASP.NET Core Framework 3.1

  • .NET Framework 4.8

See 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 2022 has .NET Framework 4.8 installed by default.

  • Windows Server 2019 has .NET Framework 4.7.2 installed by default.

  • Windows Server 2016 has .NET Framework 4.6.2 installed by default.

ASP.NET Core Hosting Bundle is required only for the Nomad. 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 ASP.NET Core Hosting Bundle.

Installers include and automatically installs the redistributable packages for Visual C++ 2013 and Visual C++ 2015-2019. The Coordinator (licensing module on the Master Stack), and Switch (on Response Stack) are written in C++ using Visual Studio 2013 and 2019, therefore require the runtime (x64) versions of these packages. Other server components use .NET Framework.

SQL BCP is required by the Export All feature described in Exporting data from 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 toP SQL BCP for more detail.

Other software

  • PowerShell

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 servers but is required to use and administer the Tachyon platform. The 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.

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

Please review Known Issues Using Tachyon.


Microsoft legacy browsers

Support has been withdrawn for Internet Explorer 11 and legacy Microsoft Edge (non-Chromium version) because Microsoft no longer supported them since 2021. We recommend you use Google Chrome, Firefox, or Microsoft Edge Chromium browser.


The computername of a Tachyon Server must comply with Microsoft NetBIOS naming standards, which includes having a length of 15 characters or less.

Microsoft's guidance can be found here:

DNS Names and SPNs

Please refer to the following sections on the Network requirements page:

Windows Server roles and features

Items in bold are included in the PowerShell script available for download from Windows Server roles and features.


Tachyon Setup will create a website with the necessary bindings, therefore please do not pre-create a website of the same name.

The following roles, role services and features must be installed/enabled as a minimum. The Name column is the reference used in PowerShell commands.

In the case of .NET Framework features we refer to 4.X in the Display Name, as X may be different depending on the server OS. The PowerShell Name always uses 45 instead of the actual version.

Role or Feature

Display Name



Web Server

Web Server (IIS)


Web Server Common HTTP Features

Default Document


Included in Web-Server.

Directory Browsing


Included in Web-Server.

HTTP Errors


Included in Web-Server.

Static Content


Included in Web-Server.

HTTP Redirection


Only required to support legacy Nomad clients after upgrading ActiveEfficiency.

Web Server Health and Diagnostics

HTTP Logging


Included in Web-Server.

Web Server Performance

Static Content Compression


Included in Web-Server.

Dynamic Content Compression


Web Server Security

Request Filtering


Included in Web-Server.

Basic Authentication


Only required if using 1E ITSM Connect or 1E Core for integrating ServiceNow and Tachyon.

IP Address and Domain Restrictions


See note below.

Windows Authentication


Web Server Application Development

.NET Extensibility 4.X


Included in Web-Asp-Net45.



ISAPI Extensions


Included in Web-Asp-Net45.

ISAPI Filters


Included in Web-Asp-Net45.

Web Server Management Tools

IIS Management Console


.NET Framework 4.X Features

.NET Framework 4.X




The following roles, role services and features must be removed/disabled.


Display Name


Web Server Common HTTP Features

WebDAV Publishing


IIS Features Configuration

Core web applications use IP and Domain Restrictions so that only specific servers can access it. Other web applications cannot be accessed using HTTP because their SSL Settings are configured with Require SSL.

The web applications for the Consumer API and Explorer use Tachyon role-based security and therefore have Windows Authentication enabled. The other web applications have Anonymous Authentication enabled.

HTTP Redirection (Web-Http-Redirect) is only required to support legacy Nomad clients after an In-place upgrade of ActiveEfficiency Server for Nomad

Basic Authentication (Web-Basic-Auth) is required only if you will be installing 1E ITSM Connect or 1E Core for integrating ServiceNow and Tachyon.


Web-Http-Redirect is only required to support legacy Nomad clients after an In-place upgrade of ActiveEfficiency Server for Nomad.

Web-Basic-Auth is only required if you will be installing 1E ITSM Connect or 1E Core for integrating ServiceNow and Tachyon.

Anti-Virus and Malware

The following should be excluded from scans to prevent file locking and resource deletion.

  • 1E log files. See Log files for details of Tachyon Server and 1E Client logs

  • The Background channel virtual directories (Agent, Content, Installers, PolicyDocuments, and Updates, which by default are in %programdata%\1E\Tachyon)

Constraints of Legacy OS

In this documentation, the following are referred to as legacy OS. Below are described some known issues for these OS.

1E does not provide support for 1E products on the following OS unless the OS is explicitly listed as being supported for a specific 1E product or product feature. This is because Microsoft has ended mainstream support for these OS or they are not significantly used by business organizations.

  • Windows XP *

  • Windows Vista

  • Windows 7

  • Windows 8.0

  • Windows 8.1

  • Windows Server 2003 *

  • Windows Server 2008

  • Windows Server 2008 R2

  • Windows Server 2012

  • Windows Server 2012 R2


1E Client and later will not install on Windows XP and Windows Server 2003. Please contact 1E if you intend to continue using any of the other legacy OS. If you experience an issue, then please try replicating the issue on a supported OS.

For Microsoft product lifecycle details, please refer to

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.

Certificate limitations - SHA2

Like most software vendors, 1E software requires the OS to support SHA2. If your organization has a PKI configured to use SHA2 256 or higher encryption, then your legacy OS may have already been updated to support it.

  • Windows XP and Server 2003 require an update as described in KB968730. Microsoft no longer provides this hotfix as a download. You must contact Microsoft Support if you need it

  • Windows 7 and Server 2008 R2 require an update as described in KB3033929. This update is not available for Vista and Server 2008

  • Windows 8, 8.1, Server 2012, Server 2012 R2 and later OS already support SHA2.

Certificate limitations - encrypted certificate requests

Windows XP and Server 2003 are unable to encrypt certificate requests, whereas later OS are able to support higher more secure RPC authentication levels. If you are using a Microsoft CA and expect these clients to request (enrol) certificates then the CA must have its IF_ENFORCEENCRYPTICERTREQUEST flag disabled. It is disabled by default on Windows 2003 and 2008 CA, but is enabled by default on Windows 2012 CA.

To determine which InterfaceFlags are set, execute the following command on the CA server:

       certutil -getreg CA\InterfaceFlags

If the following is specified then it means the flag is enabled.


To disable the encrypt certificate requests flag, execute the following commands on the CA server:

  certutil -setreg CA\InterfaceFlags -IF_ENFORCEENCRYPTICERTREQUEST
  sc stop certsvc
    sc start certsvc
Certificate limitations - signing certificates missing

On Windows computers, the installation MSI files, and binary executable and DLL files of 1E software are digitally signed. The 1E code signing certificate uses a timestamping certificate as its countersignature. 1E occasionally changes its code signing certificate, and uses it for new releases and patches for older versions, as shown in the table(s) below.

Root Certificate Authorities are implicitly trusted to validate certificates, and their certificates must be correctly installed to do this. Your computers should already have the necessary root CA certificates installed, however this may have been prevented by your organization's security policies, or inability to connect to the Internet, or they are legacy OS. In general this is not an issue because by default Windows allows software to be installed and run without validation, although you may see a warning or experience a delay. However, you must have relevant CA certificates installed if you are using 1E Client (which self-validates its own files), or your organization has applied more secure polices (for example UAC, AppLocker or SmartScreen).

Typical reasons for issues with signing certificate are:

  • If your organization has disabled Automatic Root Certificates Update then you must ensure the relevant root CA certificates are correctly installed on each computer

  • If computers do not have access to the Internet then you must ensure the relevant root and issuing CA certificates are correctly installed on each computer, numbered in the table(s) below.

The signature algorithm of the 1E code signing certificate is SHA256RSA. In most cases, the file digest algorithm of an authenticode signature is SHA256, and the countersignature is a RFC3161 compliant timestamp. The exception is on legacy OS (Windows XP, Vista, Server 2003 and Server 2008) which require the file digest algorithm of an authenticode signature to be SHA1, and a legacy countersignature.

The table below applies to software and hotfixes released in 2020.


Signing certificate

Timestamping certificates


1E Limited

TIMESTAMP-SHA256-2019-10-15 and DigiCert Timestamp Responder

Issuing CA

DigiCert EV Code Signing CA (SHA2)

Thumbprint: 60ee3fc53d4bdfd1697ae5beae1cab1c0f3ad4e3

DigiCert SHA2 Assured ID Timestamping CA

Thumbprint: 3ba63a6e4841355772debef9cdcf4d5af353a297

and DigiCert Assured ID CA-1

Thumbprint: 19a09b5a36f4dd99727df783c17a51231a56c117

Root CA

DigiCert High Assurance EV Root CA

Thumbprint: 5fb7ee0633e259dbad0c4c9ae6d38f1a61c7dc25

DigiCert Assured ID Root CA

Thumbprint: 0563b8630d62d75abbc8ab1e4bdfb5a899b24d43

Certificate limitations - expired root certificates

Ensure that your Root CA Certificates are up-to-date on clients and servers. The Automatic Root Certificates Update feature is enabled by default, but its configuration may have been changed or restricted by Group Policy Turn off Automatic Root Certificates Update.

If this GPO is enabled, then you will see DisableRootAutoUpdate = 1 (dword) in HKLM\Software\Policies\Microsoft\SystemCertificates\AuthRoot.

PowerShell limitations

PowerShell version 3.0 (required by some Tachyon instructions) is not supported on Windows XP, Vista and Server 2003. However, PowerShell 2.0 is supported on the following OS versions:

  • Windows XP SP3

  • Vista SP1 & SP2

  • Windows Server 2003 R2 & SP2.