Product integration requirements
An overview of how Tachyon connects to third-party systems, and how it integrates with its companion 1E products.
More detailed information about how to configure Tachyon is provided in Using Settings.
1E companion products
The following tables show the 1E products that combine to support particular features.
Supported versions of 1E companion products with features that depend on Tachyon .
(For products that depend on the 1E Client, please refer to ???)
Products and features that depend on Tachyon platform | Supported versions of companion products | |
|---|---|---|
AppClarity | AppClarity is a consumer application of the Tachyon platform and requires a full Tachyon infrastructure. |
|
Application Migration | Application Migration is a consumer application of the Tachyon platform and requires a full Tachyon infrastructure. |
|
Guaranteed State | Guaranteed State is a consumer application of the Tachyon platform and requires a full Tachyon infrastructure. |
|
NightWatchman | Console live status of NightWatchman clients is an optional feature of NightWatchman and requires a full Tachyon infrastructure. NightWatchman is not a Tachyon platform application and requires its own server(s). |
|
Nomad | Nomad is a consumer application of the Tachyon platform and requires a full Tachyon infrastructure. It includes the Content Distribution feature that replaces the legacy ActiveEfficiency Server and its features. |
|
Patch Success | Patch Success is a consumer application of the Tachyon platform and requires a full Tachyon infrastructure. It also requires 1E SLA Platform Business Intelligence to be installed and a SQL Server Analysis Server (SSAS) instance. |
|
Shopping | Shopping uses Tachyon platform and 1E Client for its client-side order notifications, and to allow end-users to shop for Tachyon instructions. Shopping is not a Tachyon platform application, and requires its own server(s). |
|
Experience | Experience is a consumer application of the Tachyon platform and requires a full Tachyon infrastructure. |
|
Explorer | Explorer is a consumer application of the Tachyon platform and requires a full Tachyon infrastructure. |
|
Note
In addition to the consumer applications listed above, Tachyon Setup is also used to install the Inventory and Settings applications.
Supported versions of 1E companion products that Tachyon platform features depend on.
Products and features that Tachyon platform depends on | Supported versions of companion products | |
|---|---|---|
1E Client | Tachyon requires the 1E Client to be installed on all client computers. Client features:
# not supported on non-Windows, ## partially supported on non-Windows Platform clients can optionally use the Nomad client module of 1E Client to more efficiently download content. |
|
Nomad | Clients can optionally use Nomad (1E Client with Nomad client features enabled) to provide more efficient downloading of content. |
|
Connectors
Connectors are used to connect to other 1E and third party systems, retrieve their data and populate repositories. Tachyon provides the following inventory connectors to populate the Inventory repositories, for details refer to Repositories page:
Use the links above to find more information about each type of connector. Please refer to Introducing Inventory for more information about viewing and exporting inventory repositories.
Additional connectors may exist for add-on Consumer applications that have been installed. For example, Connectors page has the following connectors to populate its entitlement repository:
AppClarity v5.2 connector — Exports entitlements from an AppClarity 5.2 database into a TSV file, which can then be reviewed and imported into.
Entitlement .tsv connector — Uploads entitlements from a folder containing one or more tab or comma-separated value file(s).
Please refer to the relevant connector page to identify security and other requirements for a specific connector.
Patch Success needs to get meta-data for patches. Ensure you add a connector for whichever one of the following sources that you use to approve patches:
Configuration Manager (SCCM) if it is configured to manage WSUS
Windows Server Update Services (WSUS).
If you are using Configuration Manager then you must add a System Center Configuration Manager connector.
If you are using WSUS then you must add a Windows Server Update Services connector.
Patch Success also requires a Tachyon connector.
Product Pack and Security Roles
Classic Product Packs:
Include instructions
Are uploaded using either of the following methods:
Tachyon Product Pack Deployment Tool as described in Tachyon Product Pack Deployment Tool
Upload button on the Settings - Instructions sets page, as described in Instruction sets page
Once the instructions are uploaded you must organize them manually into Instruction Sets, although the Tool will use the name of the zip file as the basis for the Instruction set name
Instruction Sets are the basis for assigning custom roles that determine who can do what with the instructions in each Set.
Integrated Product Packs:
Include policies and/or instructions
Are uploaded using the Tachyon Product Pack Deployment Tool as described in Uploading Integrated Product Packs
If the pack contains instructions, each one is automatically uploaded into an Instruction Set using the folder name as the basis for the Instruction set name
Policies are uploaded into Guaranteed State.
The Integrated Product Packs provided by 1E include ready-made Policies, and any instructions included in the packs are intended to augment the policies, but can be used independently.
You may want to create AD security groups to use custom roles to control access to:
Instructions Sets - you should think about groups of people who will need to view, question, action, and approve instructions
Policies - you must decide who needs access to Guaranteed State - in this version, you cannot grant access to individual Policies.
Nomad integration
Nomad integration is available on Windows PC devices and is enabled by default (NomadContentDownloadEnabled=true), and can be disabled during or after installation of the 1E Client.
With the integration feature enabled, Tachyon will detect if the Nomad client module of the 1E Client is enabled, or if Nomad v6.0.100 or later version is running on the device. Nomad then automatically downloads content from Tachyon Background Channel servers, and any other HTTP/S content source that the client may use.
Tachyon use of Nomad works irrespective of whether Nomad is integrated with Configuration Manager or using advanced Nomad features that use ContentDistribution.
Configuration Manager is not a prerequisite for Nomad integration with Tachyon, but you will need to consider the following:
Configuration Manager present
You do not need to make any configuration changes to Nomad for it to integrate with Tachyon. Please refer Introducing Nomad for guidance on designing and deploying Nomad.
Configuration Manager not present
You can deploy Nomad to Windows devices where the Configuration Manager client is not present. You will need to enable the following bits in relevant installer properties:
CompatibilityFlags bit 1 - enable long hashes
SpecialNetShare bit 13 - enable HTTP(S)
These are enabled by default in the Nomad client module of the 1E Client.
Configuration Manager integration
Tachyon is able to integrate into the Configuration Manager console to provide a right-click context menu that can be invoked from Configuration Manager computer collections. Tachyon can then use the members of the computer collections as the coverage for any instruction selected from the menu. The Configuration Manager extensions are part of the 1E PowerShell Toolkit. For more details, please refer to Preparing for the Tachyon extensions for the Configuration Manager Console..