Summary

Management groups are containers used to group devices and the software installed on those devices. Management groups are defined using configurable rules that look at various properties of the devices and their installed software, these are then evaluated to determine the group membership. This means that Management group membership adapts to changes to the devices and software in your environment.

Management groups are used by Tachyon to:

  • Determine the targets for questions, actions and reporting.
  • Determine user permissions for targeting on particular devices based on Management group membership.

In terms of permissions for determining how Tachyon users interact with the devices in your network, Management groups work alongside Instruction sets.

The Management groups page lets you add, edit, delete and evaluate management groups.

Management groups have the following properties:

  • Each device known to Tachyon can be assigned to any number of management groups, or be left unassigned. Devices not assigned to any management group will still be accessible, subject to permissions.
  • Roles can be associated with specific management groups, so that users with those roles will only be able to target the devices in their management groups.
  • Management groups can only contain devices, and they are completely independent of any other management group, even if they contain the same devices.
  • Each Management Group must have a unique name which is not case sensitive.

On this page:

Working with management groups

Management groups are defined and maintained in the SettingsPermissions→Management groups page, using device inventory data gathered from data sources by connectors and then use those management groups to control the application of instructions in Tachyon applications.

You need a Tachyon connector

If you want Tachyon applications to use the management groups you create and maintain in Settings you must add a Tachyon Connector. The username and password you provide for the Connector must be a valid Tachyon user and belong to the Management Group Sync Initiators role. Please refer to the Tachyon connector page for more details. You only need to configure the connector, you do not need to schedule or run the Tachyon connector unless you want also collect data from clients.

Configuring management groups

Creating management groups

To create a management group:

  1. Navigate to the Settings→Permissions→Management groups page.
  2. Click the Add button to display the Add management group popup.
  3. Enter a suitable Name for the management group. For example Devices.
  4. Add a Description, it's a good idea to use a description that provides an outline of the rules that are used to populate the management group. For example Device Computer Name Contains ACME.
  5. To add each rule:
    1. Click on the + button. The first one is already added, all you need to do is fill out the parts of the rule.
    2. First you select the rule name using the left dropdown menu. For example, Device Computer Name.
    3. You then select the condition. For example Contains.
    4. To complete the rule you then set the value. For example ACME.
  6. Repeat step 5 for each rule you want to define.
  7. When you have more than one rule added you can:
    1. Use the gripper icon at the right-hand end of the rule to change the order the rules are applied by dragging the rule to a new place in the list.
    2. Change the conjunction operator at the left-hand end of the rule to select between AND and OR.
  8. When you have finished adding the rules you need to decide whether you want the management group membership to be evaluated immediately on adding the management group. If you are just adding one management group it makes sense to check the Evaluate rules immediately checkbox. If you are adding a number of management groups it may be a good idea to leave the checkbox unchecked for all of them except for the last one.
  9. If you check Evaluate rules immediately and there is more than one inventory repository an additional control will be displayed prompting you to select which repository you want to evaluate the management group rules against.
  10. When you've finished making all the settings click the Add button to add the management group definition.

The management group will be added to the Management groups table.

If you selected to evaluate rules immediately the rules you set for the management group will be evaluated against the selected inventory repository.

To check how many devices are in the management group click on the management group name link in the Name column.

The picture opposite shows the details for the Devices management group showing that it contains 11 devices.

Once the management group rules have been evaluated, you should then be able to check the devices in Explorer contained in the group using the Explorer→Devices→Table page. The picture opposite shows the devices table with the Management group filter set to Devices.

Editing management groups

To edit an existing management group:

  1. Navigate to the Settings→Permissions→Management groups page.
  2. In the Management groups table, locate the management group you want to edit and check the checkbox at the left hand end of its row.
  3. Click the Edit button to display the Edit management group popup for the selected management group.
  4. Here you can edit the Name, Description and Rules that define the management group.
  5. When you've finished editing, before you click the Save button you can check the Evaluate rules immediately checkbox, this will enable any modifications you've made to the rules take effect right away. If you don't check the box the rules won's be run and you'll be able to evaluate the management groups later.

Deleting management groups

To delete an existing management group:

  1. Navigate to the Settings→Permissions→Management groups page.
  2. In the Management groups table, locate the management group you want to delete and check the checkbox at the left hand end of its row.
  3. Click the Delete button. This displays the Delete management group popup.
  4. Here you are asked in you want to proceed with the delete process. Click the Yes, delete management group button to confirm the deletion or No to cancel.

Evaluating management group membership

You can select to evaluate the management groups at any time. Doing this will process 

  1. Navigate to the Settings→Permissions→Management groups page.
  2. Click the Evaluate button.
  3. If there is only one inventory repository the evaluation will be queued immediately. If there is more than one inventory repository the Evaluate management groups popup will be displayed and you will need to select a Repository then click the Evaluate button before the evaluation is queued.
  4. When an evaluation is queued you will see a Management Group Evaluation action appear on the Settings→Monitoring→Process log page. From there you can view the progress of the evaluation.
  5. When this action has run then applications will reflect any changes that have been made to the management group memberships.

Management group rules and conditions

Each row in the Rules section is laid out as follows:

ConjunctionRule NameOperandValueDeleteGripper

When there is more than one rule this field determines how it is evaluated with the other rules. This may be one of:

ConjunctionDescription
ANDThis rule must be satisfied as well as any other rules.
OREither this rule must be satisfied or any other rules.

Determines the type of information checked when evaluating the rule. For example selecting Device Computer Name will specify checking the set value against the information held internally for each device's computer name using the selected operand.

Please refer to List of available management group rules for a list of the options.

How the value is compared against the type of information.

This may be one of the following:

OperandDescription
ContainsThe text or number in the value must appear in the device information.
Not ContainsThe text or number in the value must not appear in the device information.
EqualsThe text or number in the value must be exactly equal to the device information.
Not EqualsThe text or number in the value must not be equal to the device information.
Is NullThe device information must be Null.
Not NullThe device information must not be Null.

The value field is either a string or numeric value, depending on the chosen rule name.

This field contains an icon that lets you delete the rule.This field lets you grab the rule and change its order where there is more than one rule.

List of available management group rules

Rules used to create Management Groups, and which connectors that provide the data to support the rules. For details of how to create and use Management Groups, please refer to Management groups page.

The number of rules that a single Management Group can contain is variable because of many factors including SQL Server version, server configuration and rule type used. 1E recommends not exceeding 10,000 rules per rule-based Management Group.

Rule nameDescriptionSCCMServiceNowTachyonOracleLMSBigFixBigFixInvIntunevCenterWSUS
Device ADSite NameAD Site the device is connected to.(tick)(tick)






Device Assigned Cores

Maximum number of assigned cores for the device.

Derived from 

(tick)(tick)(tick)(tick)(tick)

(tick)
Device Classification

Classification of the device. For example, Test, Production or Development.

Production is the default.
(tick)(tick)
(tick)




Device Computer NameHostname of the computer.(tick)(tick)(tick)(tick)(tick)(tick)(tick)(tick)(tick)
Device Criticality (New in 5.1)

By default, Device Criticality is set as one of the following, as described in Using Device Criticality.

  • Undefined
  • Non-critical
  • Low
  • Medium
  • High
  • Critical.
(tick)(tick)(tick)(tick)(tick)(tick)(tick)(tick)(tick)
Device Domain NameDomain the device is installed on.(tick)(tick)(tick)

(tick)


Device Inventory dateDate that the device was last updated.(tick)(tick)(tick)(tick)

(tick)(tick)(tick)
Device Matched Device Type (New in 5.1)Normalized device type based on chassis type. For example Desktop.(tick)(tick)(tick)(tick)(tick)
(tick)(tick)(tick)
Device Matched FamilyNormalized family of the device. For example, Aspire.(tick)(tick)(tick)(tick)(tick)

(tick)
Device Matched ModelNormalized model of the device. For example, A30.(tick)(tick)(tick)(tick)(tick)
(tick)(tick)(tick)
Device Matched Socket countNormalized socket count of the device. For example, 1.(tick)(tick)(tick)(tick)(tick)
(tick)(tick)(tick)
Device Matched VendorNormalized vendor name of the device. For example, Acer Inc..(tick)(tick)(tick)(tick)(tick)
(tick)(tick)(tick)
Device Netbios Domain nameNetBIOS version of the device's domain name.(tick)(tick)(tick)





Device Netbios Name

NetBIOS version of the device name.

(tick)(tick)(tick)



(tick)
Device OSThe normalized product title of the OS that is running on the device.(tick)(tick)(tick)
(tick)(tick)
(tick)
Device Purchase dateDate that the device was purchased.(tick)(tick)






Device SerialSerial number of the computer.(tick)(tick)


(tick)(tick)

Device User Primary Username (New in 5.1)

The primary user of the device. 

(tick)
(tick)





OU Name (Deprecated)

Name of the OU that the device is in. For example Sales.

All OUs with the same name will be used, therefore the OU Path rule should be used instead. The OU Name rule is deprecated and should be re-defined using OU Path.

This rule is deprecated, which means it will continue to work until it is removed in a future version of Tachyon.

(tick)(tick)






OU Path

The name or path of the OU location in the AD hierarchy, using pipe | as the delimiter.

For example, to get all the computers in OU=Sales, OU=Workstations, DC=acme, DC=local you can either specify Sales or - if there is more than one OU called Sales in the AD structure - specify the whole path acme.local|Workstations|Sales. Note that the DC and OU parts of a distinguished name are treated differently.

(tick)(tick)






Processor Matched Chip Module CountNormalized chip module count of the processor. For example, 1.(tick)(tick)(tick)(tick)(tick)



Processor Matched Core CountNormalized core count of the processor. For example, 2.(tick)(tick)(tick)(tick)(tick)

(tick)
Processor Matched FamilyNormalized family name of the processor. For example, Athlon 64 X2.(tick)(tick)(tick)(tick)(tick)

(tick)
Processor Matched ModelNormalized model name of the processor. For example, 3250e.(tick)(tick)(tick)(tick)(tick)

(tick)
Processor Matched Processor TypeNormalized type of the processor. For example, Desktop.(tick)(tick)(tick)(tick)(tick)

(tick)
Processor Matched Release DateNormalized release date of the processor. For example, 31-03-2008.(tick)(tick)(tick)(tick)(tick)

(tick)
Processor Matched Speed M HzNormalized speed of the processor. For example, 2.100.(tick)(tick)(tick)(tick)(tick)

(tick)
Processor Matched Threads per CoreNormalized threads per core of the processor. For example, 1.(tick)(tick)(tick)(tick)(tick)

(tick)
Processor Matched VendorNormalized vendor name of the processor. For example, Advanced Micro Devices, Inc.(tick)(tick)(tick)(tick)(tick)

(tick)
Product Catalog Colloquial Version

Software colloquial version contained in the inventory source. For example, 2012.

This will usually be blank.
(tick)(tick)


(tick)(tick)

Product Catalog Edition

Software edition contained in the inventory source. For example, Standard.

This will usually be blank in SCCM unless the relevant MOF extensions have been installed.
(tick)(tick)(tick)

(tick)(tick)

Product Catalog Is Partial Version MatchedFlag that indicates whether the software title was partial matched or not (TRUE/1) or not (FALSE/0).(tick)(tick)(tick)(tick)(tick)(tick)(tick)

Product Catalog Matched Colloquial VersionNormalized software colloquial version. For example, 2016.(tick)(tick)(tick)(tick)(tick)(tick)(tick)

Product Catalog Matched EditionNormalized software edition. For example, Standard.(tick)(tick)(tick)(tick)(tick)(tick)(tick)

Product Catalog Matched End of SupportNormalized software end of support date that of that version. For example, 31-10-2008.(tick)(tick)(tick)(tick)(tick)(tick)(tick)

Product Catalog Matched is BundleFlag indicating whether the normalized software is a bundle (TRUE/1) or not (FALSE/0).(tick)(tick)(tick)(tick)(tick)(tick)(tick)

Product Catalog Matched Is License RequiredFlag indicating whether that normalized software title requires a license (TRUE/1) or not (FALSE/0).(tick)(tick)(tick)(tick)(tick)(tick)(tick)

Product Catalog Matched Release DateNormalized software release date of that version. For example, 31-10-2008.(tick)(tick)(tick)(tick)(tick)(tick)(tick)

Product Catalog Matched TitleNormalized software title. For example, Office.(tick)(tick)(tick)(tick)(tick)(tick)(tick)

Product Catalog Matched VendorNormalized software vendor name. For example, Microsoft Corporation.(tick)(tick)(tick)(tick)(tick)(tick)(tick)

Product Catalog Matched VersionNormalized software version. For example, 10.2.233.(tick)(tick)(tick)(tick)(tick)(tick)(tick)

Product Catalog TitleSoftware title contained in the inventory source. For example, Office Standard en_pack.(tick)(tick)(tick)(tick)(tick)(tick)(tick)

Product Catalog UN Standard Product Service CodeUNSPC code of the normalized software title.(tick)(tick)(tick)(tick)(tick)(tick)(tick)

Product Catalog VendorSoftware vendor name contained in the inventory source. For example, Microsoft.(tick)(tick)(tick)
(tick)(tick)(tick)

Product Catalog VersionSoftware version number contained in the inventory source. For example, 10.2.233.(tick)(tick)(tick)(tick)(tick)(tick)(tick)

Product Install DateDate that software installation was installed according to the inventory source.(tick)
(tick)





Product Instance NameInstance name if used by a product, for example MSSQLSERVER for SQL Server.(tick)(tick)(tick)(tick)(tick)



Product Last Used dateDate that software installation was last run according to the inventory source.(tick)
(tick)





Product Usage CategoryUsage category assigned to a specific installation of a  normalized software title. Potential categories are:
  • Used
  • Unused
  • Rarely used
  • Unreported
(tick)(tick)(tick)(tick)