Defining a Structure Tag in UMS

The information in this document depends on the UMS version you use. You can find out your version by looking at Help > Info in the UMS main menu.

From UMS Version 5.03.100:

In UMS Version 5.03.100 the handling of the Structure Tag has been simplified. You can now use it like any other criterion in your Default Directory Rules under UMS Administration > Global Configuration > Default Directory Rules.

Learn more in this UMS Manual section.

Prior to UMS Version 5.03.100:

  1. Open the UMS console.
  2. Click Misc > Default Directories to open the configuration window.

    Default Directories

  3. Click the (+) symbol.
  4. Select a default directory for any thin clients which do not provide a tag.
  5. Define if this rule is to override the existing directory membership and whether it is to be executed once (on first registration) or on every boot of the client.

    Define Default Directory Rule

    All thin clients with a structure tag that is not assigned to another directory will be sorted into this default directory.

  6. Click Next.
  7. Choose Structure Tag as the criterion and click Next.

    Create Driectory Rule

  8. Define a Value (tag) for the relevant folders.
  9. Click Next and Finish.
  10. Sort the default directory rules by marking a rule and clicking the up and down arrows.

    The order of the structure tag rules is important, because they will be executed in a hierarchical way, just like all the other rules. It may be useful to move a structure tag rule to the bottom of the list so that it will be executed only if no other rule takes effect

  11. Decide whether you want to Apply rules now ... or to Save the default directory rules.

    If you want to apply the rules, you have to specify the default directory for thin clients not matching a rule:

    Apply Default Directory Rules

General Note on Directory Rules

UMS executes the rules in the predefined order. As soon as one rule is fulfilled, no other rule will be executed. The option Leave in Actual Directory means that the UMS thinks a rule is fulfilled if a thin client is situated in the target directory or in its subdirectory. No other rule will then be executed, and the thin client will remain in the current directory.

If you enable Overrides all existing directory Memberships you can control if the directory holds only thin clients that are not members of a certain directory or if it houses all thin clients. Both options make sense only if you have enabled Apply rule when TC is booting or if you apply the rules manually.