Skip to main content

1E 23.11 (SaaS)

Guaranteed State Concepts

Concepts used by the Guaranteed State application, which ensures device compliance with enterprise IT policies.


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.


Before using Guaranteed State you need to configure it and upload some policies (with their rules, triggers and preconditions), please refer to:

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

  • Registry keys

  • Services

  • Config Manager metrics such as client cache usage

  • Disk free space

  • WMI namespaces and classes.

Integrated Product Packs

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.






xml files, each containing the definition of a check fragment


xml files, each containing the definition of a fix fragment


xml files, each containing the definition of a precondition fragment


<Instruction Set Name>

xml files, each containing the definition of an instruction


xml files, each containing the definition of a policy (a list of rules)


xml files, each containing the definition of a rule (a list of fragments, triggers, and their parameter values)


xml files, each containing the definition of a trigger template and its available parameters


xml file containing name, description and version details that are only used for display by the Product Pack Deployment tool

The presence of this file indicates the zip file is an Integrated Product Pack.


icon file that is referenced in the manifest.xml (Not currently used).

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.

Policies and Rules

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:




Allow you to verify that a device has a particular state, such as a registry key having a specific value. You can then view summary and detail reports which show devices that are compliant and not compliant with the check rules.


Allow you to define a desired state for the device and then enforce that state. For example, you could mandate that a registry key exists and contains a specific value. Again, you can report on the application of these fix rules to devices.

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.


A precondition is not required. If you do not specify a precondition, then the rule is always evaluated when the trigger fires.

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


Check rules require a:

  • Trigger

  • Check.

You can also optionally add a precondition.

Fix rules require a:

  • Trigger

  • Check

  • Fix.

You can also optionally add a precondition.


Be sure that you understand the key differences between Check Rules and Checks and Fix Rules and Fixes:

  • A Check Rule defines a Check, including a trigger and optional preconditions

  • A Fix Rule defines a Check and a Fix, including a trigger and optional preconditions. a fix is applied when a check is performed and the check result indicates a compliance failure.

Rule outcomes

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.


Four things you should know about rule outcomes:

  1. A check or fix rule that fails or results in an error causes a device to remain non-compliant from a Guaranteed State perspective.

  2. History entries are only created in Guaranteed State when an overall compliance transition occurs, for example from false to true or true to false.

  3. If the precondition for a rule returns failure on a device when evaluated, then the Guaranteed State subsystem indicates 'not applicable' against the device compliance status for the rule.

  4. Rules that return 'not applicable' do not affect device compliance status. If all rules for a device returned 'not applicable' the device would still be regarded as compliant.