Glossary

Client features are provided by the 1E Client. The 1E Client includes client features and modules for other 1E products including 1E. 1E enables rapid response to Instructions using the client, which supports the retrieval of information, running actions and device tagging. The client can also be extended to support additional features. The client connects to the Switch and the Background Channel.

1E content is files, such as scripts, associated with a particular Instruction via their which the client will download when it performs that Instruction. Extensibles normally in the form of DLLs on Windows, which the client will download when it self-updates. This allows additional client functionality to be deployed. 1E content is downloaded on demand via the Background Channel.

The 1E Exchange is a community platform and library of automation modules (DEX Packs) for systems management created by 1E. Our goal for this community is to democratize the development and optimization of automation processes to simplify work. You can browse the 1E Exchange but you will need a 1E Support login to download items. Refer to 1E Exchange.

The 1E Portal is the home page for 1E applications.

The 1E Toolkit is a collection of the following tools, which can be installed on a Windows computer for use by a User who has appropriate permissions.

• Configuration Manager Extensions, this can be installed only on a computer that has already installed a supported platform. Refer to Supported Platforms.

• 1E Instruction Management Studio.

• .1E Run Instruction utility.

The toolkit is available from the 1E Support Portal.

A domain account that is authorized to access Endpoint Troubleshooting portal and/or the 1E Administration pages. Authorization is achieved by adding the AD account or group and assigning it to a role.

An Action is a specific type of Instruction that is sent to client devices which can be used to modify the state of the target device. For example, setting a registry key, killing a process, deleting a file. Whereas a Question is an Instruction that requests information from the target device, but does not change its state. Generally an Action needs to undergo an approval process before it is sent.

Agent is the old name for the client. The Agent has been replaced by the 1E Client which provides client features and modules for 1E products including 1E.

The Agent language is an interpretive programming language that is executed by the client in the form of an  Instruction payload. Instructions, and their payload, are based on Instruction definitions which are stored in the TachyonMaster database. Definitions are uploaded into the database from the Administrator console by dragging and dropping one or more Instruction Definition files, a DEX Pack or ZIP file containing Instruction Definition files. The language, called DEXCode, uses Agent modules and methods and is documented in the SDK.

A plug-in component for the 1E Client which communicates with an external component, such as an operating system facility (for example Windows registry) or a service-provider application (for example Content Distribution). 1E Client modules use Providers to get their work done.

Examples:

• WMI provider.

• Registry provider.

• Nomad provider.

• BASH provider.

This is a 1E system role which allows assigned users to approve actions for all Instruction Sets . Users can approve unless the action was requested by themselves.

This is a 1E system role which allows assigned users to ask questions and view responses for all Instruction Sets; use custom properties.

This is a 1E system role which allows assigned users to view Instructions and responses for all Instruction Sets.

The Audit information log page displays audit information related to installation, permissions, Instruction set and consumer related operations carried out using the Endpoint Troubleshooting and Settings applications. Refer to Monitoring.

Auto-curation is a Catalog function and refers to the automated process of creating match rules in 1E Catalog. These match rules are neither created by the customer not by the 1E curation team. The rules are created in the customer's local 1E Catalog copy using automated logic built by 1E.

The Background Channel allows the 1E client to download resources via HTTPS without loading the Switch. This means the client can still receive and process Instructions while downloading. From version 2.0 onwards, the client can use Content Distribution for these downloads. The Background Channel is a web application on the 1E Server Website and offers the following features:

• Stores 1E content from the Consumer API in the Background Channel for clients to retrieve.

• Responds to clients retrieving 1E content from the Background Channel.

This is a client feature, also known as inventory, previously known as Historic Data Capture. This feature captures data from a number of sources on the client device, encrypts and stores in compressed form on the client device. Raw and summarized (aggregated) data is stored and can be queried using Instructions. Refer to 1E Client settings.

A plug-in component for the 1E Client that encapsulates business logic. Modules consist of Methods, which can be invoked by DEXCode. These Modules and their Methods provide a platform-independent API, generally avoiding any platform-specific references such as Windows, Linux, or Android.

Examples:

• FileSystem.

• OperatingSystem.

• Network.

• Software.

Some tables contain a column filter that lets you easily filter the information displayed in the table.

Using column picker Where the column picker control is shown.

Some tables contain column sorts that let you easily re-order the information displayed in the table.

The Configuration Manager Extensions currently include:

• Configuration Manager Agent emergency stop and resume actions.

• Configuration Manager Agent actions.

• Client Health Check.

• 1E Run Instruction utility used by the each of the above right-click actions to request 1E to run an Instruction.

• 1E Instruction Runner, a mini UI version of the 1E Endpoint Troubleshooting.

This feature is included in the 1E Toolkit.

Documentation for installing and using the Configuration Manager Extensions will be available soon.

A Consumer is any application that connects to and uses the Consumer API. An example is the Endpoint Troubleshooting application.

A Consumer sends requests to the Consumer API.

The Coordinator Instrumentation module is part of the Coordinator Service on the 1E Server which processes instrumentation data from the following components:

• Core.

• Coordinator Workflow module.

• Switch.

And responds to requests for instrumentation data from the Consumer API.

The Coordinator Service has two modules:

• Instrumentation module.

• Workflow module.

The Coordinator Workflow module is part of the Coordinator Service on the 1E Server that provides the following:

• Forwards workflow commands from the Consumer API to the Core.

• Stores workflow in SQL.

• Connects to remote SMTP to send emails used in the approval process for actions.

The Core is a 1E Server web component that does the following:

• Forwards workflow commands from the Coordinator workflow module to the Switch.

• Forwards responses from the Switch to the Responses database. This task requires high throughput.

• Generates and sends instrumentation data to the Instrumentation service.

Core Internal is the part of the Core which allows fast internal communication with the Switch using HTTP instead of HTTPS, restricted to the Switch server's local IP Address only.

Full Administrator can manage the custom properties using the Properties page in Endpoint Troubleshooting. The only custom property type available after installing the 1E server is Coverage tags, further types may be added during installation of other Consumers.

1E roles that define which Users have access to which Instruction Set.

These roles can be modified in the Administration pages by users assigned to the Full Administrator role.

Device tags can be used when setting the coverage for a particular question so that only client devices with a particular tag name and value get the question. The names and values of Device tags must be pre-configured by a Full Administrator before setting them on a client device using Device tag actions.

• Device tags can also be queried directly by Device tag questions.

• Device tags were previously known as Coverage tags. In 1E Client log files, Device tags are also referenced as scopable tags.

Refer to Tagging client devices.

The Agent Language.

DEX Packs contain Instructions or other things which extend the capabilities of 1E. DEX Packs which are required to support 1E features out-of-the-box are provided in the 1E Platform zip. The 1E Platform zip can be downloaded from the 1E Support Portal. Additional DEX Packs are available from 1E Exchange.

Defined as a product that has at least one edition for a specific major version.

Endpoint Automation application is used to ensure endpoint compliance to enterprise IT policies. It is an example of a Consumer application.

The Endpoint Troubleshooting application is the web portal used by users and administrators. It is an example of a Consumer application. It is a web application on the 1E Server Website and provides the following:

• Browser connection providing the Endpoint Troubleshooting and Administration pages.

• Sends consumer requests to the Consumer API.

A type of Instruction that can be sent to the client. An Event Subscription tells the client to monitor an arbitrary event source for a period of time (defined by the Instruction's TTL), to capture events as they occur and to report them back using the Switch.

Is when source VTV matches exactly a catalog VTV. If its an edition based product then it’s the source VTVE matches exactly catalog VTVE.

There are two kinds of filter. Question filters are used to reduce the responses from the clients; View filters reduce the information displayed in Endpoint Troubleshooting on the Responses page.

Fully Qualified Domain Name. This is the complete domain name for a specific IP-connected device, and is unique within the network and unambiguous. The FQDN consists of two parts: the hostname and the domain name. For example tachyon.acme.com.

Freeform tags may be used to set properties on client devices that can subsequently be used in Freeform tag questions. They cannot be used when defining the coverage for a question. Freeform tags can be set with arbitrary names and values that are defined only when running a Freeform tag action.

Refer to Device tags.

This is a 1E system role which has the combined rights of all the other system roles.

Is when the source VTV does not match a catalog VTV directly, but matches the source VTV via a match rule. If its an edition based product that the source VTV or VTVE matches a catalog VTVE via a match rule.

This is a 1E system role which allows assigned users to create, modify and delete Management groups and modify their membership.

The old name for Client Activity Record.

Instruction is the generic term used to describe Questions and Actions. An Instruction is sent to one or more clients, and will yield one or more responses.

Instruction Definitions are retrieved from the Core by the Switch. They define the type and functionality of the Instructions and are used to control the clients to respond in the appropriate way.

Instruction Definition files are XML format files that contain definitions for Instructions and any associated resources.

This feature is the graphical user interface part of the Configuration Manager Extensions which is included in the 1E Toolkit. It is a mini UI version of Endpoint Troubleshooting. It is an example of a 1E Consumer. It should not to be confused with the 1E Run Instruction utility available in the 1E Toolkit.

Instruction Sets provide a way of organizing Instructions and setting permissions on those Instructions. They can be created, modified and deleted from the 1E Administration console.

Each of the 1E components creates instrumentation data that can be used to display how the 1E system is performing.

This is an internal provider within the 1E agent library, used to deserialize and return a JSON string as a data table. Analogous to the Windows specific PowerShell Provider.

In this documentation, Windows XP, Vista and Windows Server 2003 are referred to as legacy OS.

Microsoft has withdrawn support for Windows XP and Windows Server 2003, but 1E includes Vista in this list because it is not significantly used by business organizations. For details of limitations and additional considerations for these OS, please see Supported Platforms.

Left hand side of match rule , i.e. the source VTVCE of the match rule.

The License Service is hosted in the cloud by 1E.

Methods are documented in the SDK.

Normalization is a Platform function that refers to the process of finding (or not finding) a match rule in 1E Catalog, then deduplicating and rationalizing the information using Platform logic, and publishing the information on the 1E Catalog UI. Partial Matching for example does not have a match rule in 1E Catalog but it’s still normalized and published on the UI using Platform logic.

How many different parts of the version number there are – e.g. 1.2.3 , number of version parts is 3.

The source Vendor and Title match the Catalog Vendor and Title.

the conditions are fulfilled (see below) whereby the lowest version number for a specific major.minor is returned as a match

Patch Insights application is used to report on and ensure successful patching of your enterprise.

How the Role-Based Access Control feature assigns Users to Roles, providing access to Instruction Sets and Administration pages.

The client stores information in Persistent Storage which it needs each time it starts. For example the last processed Instruction. A hash value of each item of information is stored in the registry, which the client uses to ensure it trusts each item. Persistent storage includes a local database that is compressed and encrypted in a way that ensures a very low impact on device performance and security. This database is used to store data for the Client Activity Record feature.

This is a Windows specific internal provider within the 1E agent library. It provides functionality to execute powershell.exe from a fixed location System32\WindowsPowerShell\v1.0 on a PowerShell .sp1 script and return the result. Some earlier versions of Windows (such as Windows XP) do not support PowerShell.

A tool for uploading DEX Packs, refer to 1E Product Pack Deployment Tool (PPDT).

Providers can be used by applications to leverage external tools to perform specific operations. For example the reclaim provider enables software to be uninstalled, thereby extending the functionality of the platform to include uninstallation.

In 1E a Question is a specific type of Instruction that requests information from client devices. The information is returned to 1E as responses.

The data resulting from a client executing an Instruction.

1E roles are used to implement Role-base access control (RBAC) and assign permissions to users and restrict access to areas of Endpoint Troubleshooting and ability to use Instructions in Instruction Sets .The roles may be system roles or custom roles related to specific Instruction Sets .

Also known as RBAC. This is a general term for assigning users to roles which allow them access specific features of 1E. Roles can be assigned to AD users and groups added in the Administration Security page. A role can be either of the following:

• System role.

• Custom role.

This command-line utility is included in the 1E Toolkit and is targeted at third party integration, and can be used by scripts. It is an example of a 1E Consumer.

It is used by the Configuration Manager Extensions which is also available in the 1E Toolkit.

The 1E SDK describes the following and is available here: Writing Instructions

• Agent Language (DEXCode).

• Agent modules and methods.

Refers to an item that may be secured by 1E using RBAC.

Settings application is used to configure 1E system and application settings. It is an example of a 1E Consumer application.

A system principal is a 1E user which cannot be modified in the Administration pages, and is assigned to a system role.

1E roles which cannot be modified in the Administration pages. 1E users can be assigned to these roles. For more information about System and Custom roles. Refer to Roles and Securables.

There are two types of tag: coverage tags and freeform tags.

This feature is included in the 1E Toolkit. TIMS provides a user interface for developing and testing Instructions using DEXCode. It includes an isolated copy of the 1E Client so that you can develop Instructions for that client version, independent of the 1E Client version that may be installed on your computer.

By default TIMS and its 1E client run under the security context of the user that started it. To use the context of Local System, as used by a normal 1E client, you can start TIMS using PSexec. TIMS should be used to edit and save Instruction Definition files.

Also known as 2FA. See Two-factor authentication.

Vendor and Title only.

Vendor, Title, Version, Colloquial version, Edition.