Contents
Tachyon Server components
| Category | Product | Notes |
|---|---|---|
Server OS |
| 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:
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) |
| 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:
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:
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:
All SQL Server instances must be configured with the following:
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:
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:
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 |
| See Preparation: Windows Server roles and features for details about required Web Server roles and features. |
Other Software |
| 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.
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:
| 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 browsersSupport 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. |
Tachyon Portal
| Category | Product | Notes |
|---|---|---|
Browsers | Latest version of:
| These browsers are supported on all OS platforms which the browser vendor supports. Please review Known issues: Using Tachyon. Microsoft legacy browsersSupport 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. |
Tachyon Toolkit
Tachyon Configuration Manager Console extensions
| Category | Product | Notes |
|---|---|---|
Client OS |
| For OS supported by Configuration Manager Current Branch (CB) see Supported configurations for System Center Configuration Manager (Microsoft). |
Microsoft System Center Configuration Manager console |
| These are the versions of Configuration Manager that 1E has tested and therefore support, but later versions are assumed to work also. Please see Preparing for the Tachyon Configuration Manager Console extensions. |
TIMS (Tachyon Instruction Management Studio)
| Category | Product | Notes |
|---|---|---|
Windows OS |
| 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 |
| 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.
| Connector | Product | Notes |
|---|---|---|
ServiceNow |
| Please refer to the ServiceNow connector page for prerequisites. |
SCCM (Microsoft System Center Configuration Manager) |
| Please refer to the System Center Configuration Manager connector page for prerequisites. |
Tachyon |
| Please refer to the Tachyon connector page for prerequisites. |
vCenter |
| 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. |
Tachyon client in 1E Client
1E Client has replaced the Tachyon Agent, and includes clients for Tachyon, Nomad, Shopping and WakeUp products. For more information about the 1E Client, please refer to 1E Client 5.1.
| Category | Product | Notes |
|---|---|---|
Windows OS |
| 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:
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:
|
Runtime libraries
|
| .NET Framework is required only for the following features of 1E Client:
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 - 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 Migration. The 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
Linux
Solaris
| 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:
Also included in the download are 1E Client packages for the following legacy Linux distributions:
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:
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 and perl are required for installation of 1E Client on all non-Windows OS. 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 |
| The following client features work with these versions of Configuration Manager on Windows computers:
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.) |
Running Tachyon instructions on devices
You must ensure the appropriate scripting environment is present on Tachyon client devices. Tachyon SCALE - Simple Cross-platform Agent Language for Extensibility - supports running native PowerShell on Windows OS and bash on non-Windows OS devices, which can be script files downloaded when an instruction runs, or command text. You will very probably want to use these native scripting features in instructions you download from 1E or ones you develop yourself using TIMS.
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.
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.
To determine the version of PowerShell on a computer, start PowerShell (command prompt or ISE) and enter one of the following commands: $PSVersionTable.PSVersion or $PSVersionTable for more detail.
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 Version | PowerShell Version | Notes | |||||
|---|---|---|---|---|---|---|---|
| 1.0 | 2.0 (Note 3) | 3.0 | 4.0 | 5.0 | 5.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 & SP1 | R2 & SP2 | Notes 1, 2 | ||||
| Windows Vista * | RTM | SP1 & SP2 | Notes 1, 2 | ||||
| Windows XP * | RTM, SP1 & SP2 | SP3 | Notes 1, 2 | ||||
* These OS are regarded as legacy OS:
- PowerShell is not built-in for these OS. These OS do not support 3.0 or later. See Constraints of Legacy OS
- If PowerShell 1.0 is installed it must be removed in order to install a later version.
- Support for PowerShell 2.0 is included in PowerShell 3.0 and later.
- PowerShell is not installed by default on these OS but is an optional feature that should be enabled using Server Manager.
- PowerShell 2.0 is part of WMF Core package (KB968930) with prerequisite of .NET Framework 3.51 (which includes .NET 2.0 SP1).
- 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
- 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
- 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
- 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
- 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
- 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
- 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
- In these Server OS, PowerShell 5.1 is referred to as the Desktop Experience. You can use the PowerShell Core version if you prefer.
Microsoft ended support for .NET Framework 4, 4.5, and 4.5.1 on January 12, 2016. Please refer to https://support.microsoft.com/en-gb/help/17455/lifecycle-faq-net-framework.
Bash on non-Windows OS
Bash and perl are required for installation of all non-Windows 1E Clients.
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 the Scripting.Run method. 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.
ActiveEfficiency Server and the ActiveEfficiency Scout
| Category | Product | Notes |
|---|---|---|
OS |
| ActiveEfficiency and the Scout will install on systems running these OS. |
Database servers |
|
|
Configuration Manager |
|
|
Web servers |
|
You can download the SQL Server Native Client 11.0 installer ( |
Runtime libraries |
|
|
Browsers |
| |
Others |
| ActiveEfficiency Server must be running on your network before you install the ActiveEfficiency Scout. |
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.
|
|
For Microsoft product lifecycle details, please refer to https://support.microsoft.com/en-us/lifecycle/search.
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.
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 - 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.
2020 | Signing certificate | Timestamping certificates |
|---|---|---|
Certificate | 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.