Tachyon applications and tools are consumers, and all consumers connect to the Tachyon Consumer API.
|Inventory 5.1||View and export inventory, and manage associations.||Inventory, configuration|
|Settings 1.3||Configure and monitor platform features.||Configuration|
|AppClarity 7.1||Manage software license compliance, License Demand Calculations, license entitlements, and for reclaiming unused software.||Inventory|
|Application Migration 3.1||Intelligently automate the migration of applications during a Configuration Manager OS deployment.||Inventory|
|Experience 1.2||Measure performance, stability and responsiveness for applications and devices to assess user experience across your enterprise.||Client|
|Explorer 5.1||Investigate, remediate issues and manage operations across all your endpoints in real-time.||Client|
|Guaranteed State 1.4||Ensure endpoint compliance to enterprise IT policies.||Client|
|Patch Success 1.2.104|
Reports on and ensures successful patching of your enterprise.
Requires SLA Business Intelligence to be installed by Tachyon Setup, as described in Business Intelligence. It also needs connectors to get meta-data for patches from whichever of the following that you use to approve patches:
The following types of application require 1E Client (with Tachyon features enabled) to be deployed to all in-scope devices.
- All Client applications
- Inventory applications if you intend using the Tachyon connector to populate your inventory, because this depends on the Tachyon client features of the 1E Client.
The AI Powered Auto-curation feature is optionally used by Inventory applications to provide automatic curation of new products. This avoids having to manually add products to the 1E Catalog, or wait for it be updated. This optional feature requires additional memory on the Tachyon Server (Master Stack). Please refer to AI Powered Auto-curation: Memory requirements for details.
Some benefits of using AI Powered Auto-curation are that you can:
- Achieve significantly more normalized software from the first sync
- Reduce the manual effort required to normalize software
- Get an expanded SAM offering as more data is available for AppClarity
- Get additional coverage for Application Migration
- Identify more software to review for security threats.
The following are tools included in Tachyon Platform. These tools are not installed using Tachyon Setup. They have either their own installers or are included in download zips.
- Tachyon Configuration Manager UI extensions - installed as part of the Tachyon Toolkit, this is a right-click extension for the Microsoft System Center Configuration Manager console that provides a graphical user interface for the user to browse and run an instruction on devices in a specified Collection
- Tachyon Run Instruction command-line tool - installed as part of the Tachyon Toolkit, it is used for sending instructions to the Tachyon server from a script or from a command prompt
- Tachyon Product Pack Deployment Tool - included in the Tachyon Platform zip ProductPacks folder
- Tachyon Instruction Management Studio) - used for development of Tachyon instructions using the Tachyon SDK.
A typical Tachyon license allows use of all these tools.
Tachyon Multi-Stack system
The picture opposite shows a Tachyon Multi-Stack System. Here the Tachyon Master Stack communicates with one or more Tachyon Response Stacks. A local Response Stack is not mandatory. Components colored green are optional in a Tachyon system.
As with a single-server system, the databases are optionally installed locally or on remote SQL Server instances(s).
Let's take a look at each of the Tachyon components in slightly more detail.
The following components are IIS Web Applications that reside on a single-server. Other configurations - such as Response Stack and DMZ Server - have a subset of these.
Under the Tachyon website:
* These applications are installed under the Default Web Site and then relocated by Tachyon Setup to support both HTTP and HTTPS.
The Core is a Tachyon Response Stack component which provides internal API and data processing.
Core does the following:
The Background Channel is a Tachyon Response Stack component which provides a means for the Tachyon clients to retrieve large data items from Tachyon without loading the Tachyon Switch:
The Switch is a Tachyon Response Stack component which provides the following:
The Switch Host service is responsible for starting local Switches.
Tachyon Portal UI
Tachyon users browse to the Tachyon Portal to access Tachyon applications.
Applications that are Tachyon built-in applications:
Applications that are optional:
Tachyon Consumer API
The Tachyon Consumer API provides the following:
The Coordinator service is the coordinating service used by Tachyon components. It has two modules, Workflow and Instrumentation.
The Workflow module provides the following:
The Instrumentation module processes instrumentation data from the following components:
Supports the two-factor authentication feature, with email.
For Tachyon 4.1 onward Tachyon Setup supports optional installation of ActiveEfficiency Server to support Nomad.
ActiveEfficiency can be installed on the Tachyon server for systems supporting up to 50,000 clients. Larger systems require separation of incoming client network traffic from Nomad and Tachyon. Therefore, either ActiveEfficiency or the Response Stack is installed on a separate server, or if both are installed on the same server there are additional networking and DNS requirements. There is no integration between ActiveEfficiency Server and Tachyon. ActiveEfficiency is installed by Tachyon Setup in order to provide support for both HTTP and HTTPS.
Nomad 7.0.200 uses the ActiveEfficiency Server for the following features. Please click on the links below to learn more about configuring Nomad features and their prerequisites, which can be configured after installing ActiveEfficiency Server:
ActiveEfficiency Server is also used as an inventory repository by the following 1E solutions, which also require the ActiveEfficiency Scout as a connector to capture the data from Configuration Manager. Tachyon Setup does not install or configure the Scout.
The Catalog website used to view and interact with the Catalog.Tachyon Setup supports installation of 1E Catalog on the Tachyon Master Stack server. For customers that want to continue using an existing installation of 1E Catalog 2.0 then Tachyon Setup supports using a remote Catalog server as a custom setup option. Please contact 1E for details of how to use custom setup options.
Catalog Update Service
|Service used to connect to the 1E Cloud Catalog in order to download the latest catalog entries.|
|Consumer API used to manage and update the 1E Catalog.|
|Internal API used to manage SLA components.|
SLA Platform UI
|The website used to view and interact with the Inventory.|
|The Engine service is the coordinating service used by SLA components. This includes processing of Management Groups.|
SLA Integrate Services
The SLA Integrate Agent sevice performs Connector functions by connecting to data sources and importing data into repositories.
The SLA Integrate Manager service manages Agent operations including repository action schedules.
|The inventory repositories. Each instance of a repository is stored in SLA-Data database, and is based on a template defined in the SLA-Data database.|
SLA Operations Provider API
|Consumer API and functions used by SLA clients, including Application Migration task sequence steps and AppClarity Software Reclaimer.|
Internal API used by Patch Success application.Business Intelligence is an optional component installed by Tachyon Setup on the Master Stack, and requires SQL Server Analysis Services (SSAS). Business Intelligence is a prerequisite for the Patch Success application to support efficient presentation of visualizations on a large scale.
Tachyon Consumer applications are:
Other Tachyon Consumers are Tachyon Configuration Manager extensions, and other 1E Tachyon Toolkit features.
SQL Server (Database Engine and Analysis Services)
Tachyon has two databases:
Experience has two databases:
Catalog has one database:
SLA has three databases:
SLA BI has two databases:
Nomad has one database:
Tachyon client runs on the devices you want to include in your Tachyon managed estate. Tachyon clients communicate with the Tachyon Switches and the Background Channel to provide responses to instructions (questions and actions).
Tachyon client and its features are part of the 1E Client, which replaces the Tachyon Agent. 1E Client also includes: Nomad client, PXE Everywhere Agent, Shopping/WSA client, and WakeUp client.
Tachyon architecture for Internet-facing devices
Enabling Tachyon to support devices that are external to your company network is done by slightly extending the default single-server architecture.
The Responses Stack handles communications between the Master Stack and the Tachyon clients. The Background Channel and Switches components handle the direct communication with the Tachyon clients, the Core processes the information in both directions between the Master Stack and the Switches.
To enable external Tachyon client devices to interact with Tachyon, you need to put the Background Channel and at least one Switch into the DMZ.
First, you need a working Tachyon system with a Response Stack that will provide the Core for the DMZ Server. The picture opposite shows a Response Stack and Master Stack on the same server, located on the internal network. This serves clients when they are connected to the internal network.
Then configure the internal firewall to allow two-way communication between each of the following:
- The Core on the Internal Response Stack and the Switch(es) in the DMZ
- The Coordinator on the internal Response Stack and the Switch(es) in the DMZ
- The Consumer API on the internal Master Stack and the Background Channel in the DMZ
Configure the external firewall to allow incoming connections for:
- The external Tachyon clients and the Background Channel in the DMZ
- The external Tachyon clients and the Switch(es) in the DMZ
After you have installed the DMZ Server in the DMZ, you need to make the following changes in the existing Tachyon system:
- The Tachyon Master database would need to be modified to enable Tachyon to recognize and additionally use the DMZ Background Channel and Switch(es) and raise the security level of the Core and Switch communications to use HTTPS.
- The configuration files for the Switch Host on the Internal Tachyon Server and on the Tachyon Server in the DMZ would need to be changed to enable the Switch(es) to communicate with the Core.
- The configuration file for the Background Channel on the DMZ would need to be changed to enable the Background Channel to communicate with the Consumer API.
Detailed steps for the above process can be found on the Implementing a Tachyon DMZ Server page.
The DMZ picture shows a dual firewall design, but single firewall is also supported.
In the picture, components colored green are optional in a Tachyon system.