1E 8.1 (on-premises)

Guaranteed State allows you to easily check and enforce device state. Device state can represent just about anything you'd like to be set in a certain way for a collection of devices.

Once you have imported an Integrated Product Pack you can configure and deploy policies to manage various device attributes. For example:

Integrated Product Packs are Zip files containing Guaranteed State policies, but can also contain instructions (as an alternative to classic Product Packs which can only contain instructions). They have a folder structure and files as shown in the following table (except for manifest.xml) all folders and files are optional.

You can upload these Zip files into Tachyon using the Tachyon Product Pack deployment tool, please refer to Uploading Integrated Product Packs for details.

1E provide a number of ready-made policies which are described in the Integrated Product Packs pages:

These pages include lists of instructions, policies, rules, fragments (preconditions, checks and fixes) and trigger templates. The lists have links to more detailed information about each pack in the Tachyon Product Packs reference.

You can also create your own policies using rules, fragments and triggers from other Integrated Product Packs, for example, the Tachyon Core Integrated Product Pack.

Guaranteed State is enforced by the Tachyon client at each device using one or more policies that are deployed to devices according to their management group memberships.

A policy consists of one or more rules, which fall into two primary categories:

Management groups use rules to determine device membership, enabling the devices to be administered as a group. For example, you can select devices based on their Active Directory Organizational Unit, or their operating system version, or any other criteria available to the management group rules. Please refer to Management Groups page page for details.

You can also create your own policies using rules, fragments and trigger templates from any Integrated Product Pack that you have uploaded, which are fully configurable, please refer to Defining your own policy for details.

The following are examples of check and fix rules provided by the Tachyon Core Integrated Product Pack:

Fragments is a collective term for Rules, Trigger templates and Preconditions which are written in the Tachyon instruction language SCALE.

Triggers define the conditions which will cause a rule to be evaluated. Each check rule and fix rule must have a rule trigger defined using a trigger template.

The following are examples of trigger templates provided by the Tachyon Core Integrated Product Pack:

Both check rules and fix rules may have optional preconditions defined.Preconditions allow you to define a conditional test that must be met before the rule is evaluated.

The following are examples of preconditions provided by the Tachyon Core Integrated Product Pack:

Check rules require a:

You can also optionally add a precondition.

Fix rules require a:

You can also optionally add a precondition.

A rule always returns two items to the Tachyon subsystem. One is a Pass/Fail value and the second is an arbitrary data item. A rule can also return an error status to the subsystem. This can occur if the rule logic terminates unexpectedly, for example, because a file could not be found etc.

Guaranteed State history will show the result of rule evaluation. It will clearly indicate whether a check rule returned a success (compliance), failure, or error. It will also show whether a fix rule (if applicable) indicated success, failure, or returned an error.