Summary

A list of all the platforms supported by Tachyon, and the software required to allow Tachyon to be installed or to work.
On this page:

Tachyon Agent

CategoryProductNotes

Windows OS

  • Windows Server 2019
  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows 10 CB 1903
  • Windows 10 CB 1809
  • Windows 10 CB 1803
  • Windows 10 CB 1709
  • Windows 10 CB 1703
  • Windows 8.1

Professional and Enterprise editions of Windows 10 are supported.

All versions are provided with 32-bit & 64-installers.

Can be installed on physical and virtual computers.

A service is installed called 1E Tachyon Agent with a small footprint.

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 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 Tachyon Agents: Deploying on Windows platforms.

Runtime libraries

  • .NET Framework 4.7
  • .NET Framework 4.6.2
  • .NET Framework 4.5.2
  • .NET Framework 3.5 SP1

One of these versions of .NET Framework is required, but only by the WSA executable in the Shopping module. It is not required by any other 1E Client features or modules.

Other Windows Software
  • Visual C++ 2013 Redistributable
  • PowerShell 3.0 (or later)
  • Nomad 6.2 (or later)

Tachyon Agent installer includes the redistributable package for Visual C++ 2013.

PowerShell is not a prerequisite for installation of the Agent. PowerShell is used by some Tachyon instructions (that have PowerShell commands embedded or scripts that are downloaded) and some of these require PowerShell 3.0 or later.

1E Nomad Branch service is not a prerequisite for installation of the Agent. Nomad is only used to download instruction resource files if it is installed and the Tachyon Agent integration with Nomad feature is enabled.

For more details please refer to Design Considerations: Downloading Agent Resources and Nomad Integration.

Non-Windows OS

macOS
  • macOS Mojave 10.14
  • macOS High Sierra 10.13

Linux

  • CentOS 7
  • Red Hat Enterprise Linux 7.1
  • SUSE Linux Enterprise (SLES) 12
  • Ubuntu 14.04

Solaris

  • Solaris 11.3

Android

  • Android Pie 9.0
  • Android Oreo 8.1
  • Android Oreo 8.0

Other versions of these Operating Systems should work but have not been tested by 1E.

The Tachyon Agent is available for download from the 1E Support Portal, for the following architectures:

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

Also included in the download are Tachyon Agents for the following legacy Linux distributions:

  • Fedora 21
  • openSUSE Leap 42.1

Tachyon Agents for other Linux distributions can be requested, including Raspbian for Raspberry Pi, and Debian.

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.

Other Non-Windows Software

  • Bash
  • Perl

Bash and perl are required for installation of all non-Windows Agents, with the exception of the Agent for Android which is available from the Google Playstore.

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

  • CB 2002
  • CB 1910
  • CB 1906
  • CB 1902
  • CB 1810
  • CB 1806
  • CB 1802
  • CB 1710

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

  • 1E WakeUp Policy Refresh and REFRESHONSUBNETCHANGE
  • Tachyon instructions used by Tachyon Configuration Manager Console extensions

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.

For more details please refer to Microsoft System Center Configuration Manager Console Extensions.

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

Tachyon Server

CategoryProductNotes

Server OS

  • Windows Server 2019
  • Windows Server 2016
  • Windows Server 2012 R2

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 to be US-English because of a known issue with certain regional settings.

If TLS 1.0 is disabled either on the Web server, or on the SQL Server, you must install SQL Server Native Client 11.0 on the Web server before installation. If your SQL Server is local you will probably have the SQL Server Native Client installed already. The requirement is for installing, not running the client, but it should remain installed to support future patching and upgrades.

SQL Server

  • SQL Server 2017
  • SQL Server 2016 SP2
  • SQL Server 2014 SP2

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

You must have one of these versions of SQL Server installed. 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 SQL Server Analysis Services (SSAS) as per their requirements.

You will need the following:

  • A SQL Server database instance for the following databases:
    • 1ECatalog
    • SLA-Data
    • SLA-Integrate
    • SLA-Shared
    • TachyonMaster
    • TachyonResponses
  • A SQL Server Analysis Services (SSAS) instance installed in Multidimensional mode.

    The SLA.BI installer creates the following:

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

    If the SLA Platform databases, BI database or SSAS instances 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.

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

If installing SQL Server locally, note:

  • SQL Server 2014 requires .NET 3.5 SP1 and .NET 4.x - supported Server OS include both which will need to be enabled in Server Manager roles and features
  • SQL Server 2016 and 2017 require .NET 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.

Microsoft System Center Configuration Manager

Not applicable.

Tachyon Server components have no dependencies on Configuration Manager.

Instead, see Tachyon Toolkit and Microsoft System Center Configuration Manager Console Extensions.

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.7
  • .NET Framework 4.6.2
  • .NET Framework 4.5.2
  • .NET Framework 3.5 SP1

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

Windows Server 2012 R2 has .NET Framework 4.5.1 installed by default. You will need to upgrade to 4.6.1 or 4.6.2.

Windows Server 2016 has .NET Framework 4.6.1 installed by default.

Tachyon Server installer includes the redistributable package for Visual C++ 2013. The Tachyon Switch is written in C++ using Visual Studio 2013 and therefore requires the C++ 2013 runtime (x64); other server components use .NET.

PowerShell is required by the installer during installation.

Browsers

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 Explorer Portal and can be on a remote computer.

Tachyon Portal

CategoryProductNotes

Browsers

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.

Tachyon Toolkit

Microsoft System Center Configuration Manager Console Extensions

CategoryProductNotes

Client OS

  • Windows Server 2019
  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows 10 CB 1903
  • Windows 10 CB 1809
  • Windows 10 CB 1803
  • Windows 10 CB 1709
  • Windows 10 CB 1703
  • Windows 8.1

For OS supported by the 2012 Configuration Manager Console, see Configuration Manager Console Requirements (Microsoft).

For OS supported by Configuration Manager Current Branch (CB) see Supported configurations for System Center Configuration Manager (Microsoft).

Microsoft System Center Configuration Manager Admin Console

  • CB 2002
  • CB 1910
  • CB 1906
  • CB 1902
  • CB 1810
  • CB 1806
  • CB 1802
  • CB 1710

These are the versions of Configuration Manager that 1E has tested and therefore support, but later versions are assumed to work also.

Please see Configuring the Tachyon Configuration Manager console extensions.

TIMS (Tachyon Instruction Management Studio)

CategoryProductNotes

Windows OS

  • Windows Server 2019
  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows 10 CB 1903
  • Windows 10 CB 1809
  • Windows 10 CB 1803
  • Windows 10 CB 1709
  • Windows 10 CB 1703
  • Windows 8.1

Professional and Enterprise editions of Windows 10 are supported.

All versions are provided with 32-bit & 64-installers.

TIMS is currently only available for Windows OS. For installation guidance, please refer Tachyon SDK - Getting started with TIMS.

Other Windows Software
  • Visual C++ 2013 Redistributable
  • .NET Framework 4.5.1 (or later)

TIMS installer includes the redistributable package for Visual C++ 2013.

PowerShell 3.0 or later is required when testing instructions that have PowerShell commands embedded or scripts that are downloaded.

Connectors

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

ConnectorProductNotes

ServiceNow

  • ServiceNow Jakarta release

Please refer to the ServiceNow connector page for prerequisites.

System Center Configuration Manager

  • CB 2002
  • CB 1910
  • CB 1906
  • CB 1902
  • CB 1810
  • CB 1806
  • CB 1802
  • CB 1710

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

Tachyon

  • Tachyon 4.0
Please refer to the Tachyon connector page for prerequisites.

vCenter

  • VMware PowerCLI 11.1.0

VMware PowerCLI 11.1.0 (code.vmware.com/web/dp/tool/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: https://www.vmware.com/resources/compatibility/sim/interop_matrix.php#interop&2=&106=

Please refer to the vCenter connector page for configuration details.

Scripting

Tachyon Agent language SCALE directly supports running PowerShell on Windows OS and bash on non-Windows OS devices, which can be scripts that must be downloaded by SCALE when an instruction runs, or actual command text. You will very probably want to use this feature in your own instructions and ones that you download from 1E. Therefore you must ensure the appropriate scripting environment is present on Agent devices.

PowerShell on Windows OS

PowerShell is used by some Tachyon instructions (that have PowerShell commands embedded or scripts that are downloaded) and some of these require PowerShell 3.0 or later, although some scripts will support PowerShell 2.0. PowerShell scripts are supported only on Windows OS. 

To see if an instruction requires PowerShell, look in its Instruction Definition XML file for PowerShell resources defined under the <Resources> tag.

If installing or upgrading PowerShell, it is best to install the latest version available. However, do not expect full forward or backward compatibility between PowerShell versions.

The table below shows which versions of PowerShell are supported on each OS version and Service Pack, and if it is built-in or needs to be installed.

OS VersionPowerShell VersionNotes
1.02.0 (Note 3)3.04.05.05.1
Windows Server 2016, 2019



RTM (Note 9)RTM (Notes 12, 13)Note 4
Windows 10



RTM (built-in)Anniversary Update (built-in)
Windows Server 2012 R2


RTM (built-in)RTM (Note 9)RTM (Note 12)Note 4
Windows 8.1


RTM (built-in)RTM (Note 9)RTM (Note 12)
Windows Server 2012 *

RTM (built-in)RTM (Note 7)RTM (Note 9)RTM (Note 12)Note 4
Windows 8 *

RTM (built-in)



Windows Server 2008 R2 *
RTM (built-in)SP1 (Note 6)SP1 (Note 7)SP1 (Note 8)SP1 (Note 10)Note 4
Windows 7
RTM (built-in)SP1 (Note 6)SP1 (Note 7)SP1 (Note 8)SP1 (Note 10)
Windows Server 2008 *RTM (built-in)
SP1 & SP2 (Note 2)



Windows Server 2003 *RTM & SP1R2 & SP2



Notes 1, 2
Windows Vista *RTMSP1 & SP2



Notes 1, 2
Windows XP *RTM, SP1 & SP2SP3



Notes 1, 2

* These OS are regarded as Legacy OS.

  1. PowerShell is not built-in for these OS. These OS do not support 3.0 or later. See Constraints of Legacy OS.
  2. If PowerShell 1.0 is installed it must be removed in order to install a later version.
  3. Support for PowerShell 2.0 is included in PowerShell 3.0 and later.
  4. PowerShell is not installed by default on these OS but is an optional feature that should be enabled using Server Manager.
  5. PowerShell 2.0 is part of WMF Core package (KB968930) with prerequisite of .NET Framework 3.51 (which includes .NET 2.0 SP1).
  6. PowerShell 3.0 is part of WMF 3.0 with prerequisite of .NET Framework 4.0 or later. Refer https://www.microsoft.com/en-us/download/details.aspx?id=34595
  7. PowerShell 4.0 is part of WMF 4.0 with prerequisite of .NET Framework 4.5 or later. Refer https://www.microsoft.com/en-us/download/details.aspx?id=40855
  8. PowerShell 5.0 is part of WMF 5.0 with prerequisites of .NET Framework 4.5 or later and WMF 4.0. Refer https://www.microsoft.com/en-us/download/details.aspx?id=50395
  9. PowerShell 5.0 is part of WMF 5.0 without any other prerequisites. Refer https://www.microsoft.com/en-us/download/details.aspx?id=50395
  10. PowerShell 5.1 is part of WMF 5.1 with prerequisites of .NET Framework 4.6 or later, WMF 4.0 and SHA-2 Code Signing. Refer https://msdn.microsoft.com/en-us/powershell/wmf/5.1/install-configure
  11. PowerShell 5.1 is part of WMF 5.1 with prerequisites of .NET Framework 4.6 or later and WMF 4.0. Refer https://msdn.microsoft.com/en-us/powershell/wmf/5.1/install-configure
  12. PowerShell 5.1 is part of WMF 5.1 with prerequisite of .NET Framework 4.6 or later. Refer https://msdn.microsoft.com/en-us/powershell/wmf/5.1/install-configure
  13. In these Server OS, PowerShell 5.1 is referred to as the Desktop Experience. You can use the PowerShell Core version if you prefer.

Bash on non-Windows OS

Bash and perl are required for installation of all non-Windows Agents, with the exception of the Agent for Android which is available from the Google Playstore.

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.

Constraints of Legacy OS

Support

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 Server 2003
  • Windows Server 2008
  • Windows Server 2008 R2
  • Windows Server 2012
  • Windows Server 2012 R2

Please contact 1E if you require support for these legacy OS. If you experience an issue on these OS, then please try replicating the issue on a supported OS.

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

PowerShell limitations

Some Tachyon instructions use PowerShell and some of those expect PowerShell version 3.0, which is not supported by the legacy OS listed above. However, PowerShell 2.0 is supported on the following OS versions:

  • Windows XP SP3
  • Vista SP1 & SP2
  • Windows Server 2003 R2 & SP2

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.

	IF_ENFORCEENCRYPTICERTREQUEST -- 200 (512)

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 - SHA2

When installing Tachyon Agent on Windows XP and Server 2003 you may also require a hotfix as described in KB968730. This hotfix is required if your PKI has CAs configured to use SHA2 256 or higher encryption.

Certificate limitations - expired root certificates

Ensure that your Root Certificates are up-to-date. The Update Root Certificates feature is enabled by default on these OS but its configuration may have been changed or restricted by Group Policy. You may see DisableRootAutoUpdate = 1 (dword) in HKLM\Software\Policies\Microsoft\SystemCertificates\AuthRoot.

Certificate limitations - signing certificates missing

As described in Requirements: Digital Signing Certificates the root VeriSign Class 3 Public Primary Certification Authority - G5 certificate must exist in the Third-Party Root Certification Authorities store (which is replicated in the Trusted Root Certification Authorities store). This root certificate is normally automatically provided by Microsoft's Update Root Certificates feature, however this may not be present for legacy OS. To verify if you affected by this issue see Implementation issues: 1E Digital Signing Certificate.