Documentation Index

Fetch the complete documentation index at: https://support.controlup.com/llms.txt

Use this file to discover all available pages before exploring further.

Assign Dynamic Tags Based On Registry Values

Prev Next
Beta

This feature is in beta. Contact your ControlUp representative for more information.

Computed Tags let Agent ONE read data from the Windows registry and use it as a dynamic targeting conditionfor deployments. This lets you target ControlUp module deployments based on a value that's already set on the device, such as a rollout ring, environment marker, or business unit.

Agent ONE reads the values from the registry when it is first installed, each time it starts, and every 20 minutes while it is running. This means that when the registry data on a device changes, the depoyment on the device will automatically get updated correspondingly.

Step 1 - Define the registry path and values to monitor

Agent ONE doesn't automatically read every value in the reigstry. You must first define a list of registry values to read.

  1. Go to Agents > Computed Tags.
  2. Click Create Rule
  3. Give the rule a name. This is the name that appears when you create a deployment condition based on this rule.
  4. Define the full registry location (hive, path, and value). HKLM and HKCR are currently the only supported hives. For example, given the following registry entry:
    RegistryExample.png
    You would enter:
  • Registry Hive: HKLM
  • Key Path: SYSTEM\CurrentControlSet\Control\ComputerName\ActiveComputerName
  • Value Name: ComputerName

Step 2 - Use the registry path and value in a deployment

  1. When creating a set of conditions in a deployment, select Computed Tags.
  2. Select the name of the rule you created in step 1.
  3. Select a condition (match, not match, contains, does not contain).
  4. Enter the value to compare against the current data in the registry.

Disable, enable, and delete Computed Tag rules

You can disable, enable, or delete Computed Tag rules by going to Computed Tags, and clicking the three-dots menu next to a rule.

Note that to disable or delete a rule, you must first remove it from the conditions in all deployments. When you attempt to disable or delete a rule and it is currently in use, an error message displays the names of the deployments currently using the rule in its conditions.