Team Members tab
At Topology > Teams, you can set up and manage Teams. When adding or editing a Team, use the Members tab to manage Team membership. Membership of a Team can be explicit (that is, Agents or Teams that have been added manually) or rule-based. Explicit members take precedence over rule-based members.
- To add Agents to a Team automatically, click Rules to set up Team rules. Team rules are based on the specification of the computer on which the Agent runs. They are evaluated by the Dispatcher each time the Agent comes online or when network IP address changes are made. IPv4 and IPv6 addresses are supported. If an Agent meets the rules of a Team, it will automatically be added to the Team. If it no longer meets the rules of a Team, it will be removed from the Team. The Rules button also shows the number of configured Team rules.
- Teams can also be a member of other Teams. These so called "nested Teams" are useful if you regularly execute Jobs on the same group of Teams. For example, the Team "Windows 7 laptops" and the Team "Windows 8 laptops" can both be member of the Team "Laptops".
Order of Job execution in embedded Teams
Suppose Team 1 is embedded in Team 2, which is embedded in Team 3, which is embedded in Team 1 again. The order in which the Job will be executed will be ascending according to Team names.
- To set a Team as a primary Team for one or more Agents, select the Agent(s) and click Set current team as primary. Agents that use the Team as their primary Team will inherit its Team settings and Trusts. An Agent can only inherit Team settings and trusts from a primary Team: as an Agent can have only one primary Team at a time, it does not inherit settings and trusts from any other Team which it is a member of:
- Team settings (unless Agent-specific settings are used). Because these settings can deviate from the Global Settings, it becomes much easier to apply the same settings on groups of Agents. You can set up Team settings on the Team Settings tab.
- Trusts (unless Agent-specific Trusts are used). Agents that use a Team as their primary Team not only inherit its Trusts (Security settings), but also its Team settings (Topology settings). It is therefore recommended to consider the consequences before assigning an Agent to a different primary Team, as this may have a severe impact on the performance of the Agent.
Best practice: Create a Team folder, configure Trusts on this folder and add the two primary Teams to the Team folder. In this way, it is not necessary to change Team settings or Trusts for each primary Team: the Agent will still inherit the correct settings from its primary Team. See Trusts.
- To view the settings of the Agents in the Team, right-click and choose Settings overview. The settings overview does not resolve nested Teams to show the settings of the underlying Agents.
- To change the settings of the Agents in the Team, right-click and choose Change settings of selected Agents. You can also change Agent settings from the Settings overview. It is not possible to change the settings from nested Teams.
- Use the Automatic Job Scheduling options to schedule Jobs that run automatically when members are added to a Team or removed from a Team. For example, you can configure the Job "Install Ivanti Automation Dispatcher" to run automatically on Agents that are made member of the Team "Dispatchers"; and the Job "Remove Ivanti Automation Dispatcher" on Agents that are removed from that Team. Any Automatic Job Scheduling applies to both explicit Team members and rule-based members, and applies to members of nested Teams as well as direct members.
- The Members column shows the number of unique Agents that are member of each nested Team (if any and if enabled). The Member count field shows the total number of unique Agents that are member of the Team. These numbers are not updated during any Team member changes, but first (re)calculated when the changes to the Team are saved.
In version 2020.3, three new rules were added to the automatic agent to team membership (Members tab, Rules button). If the agent is part of a particular AD Group, Organizational Unit (OU), or has defined a specific system Environment Variable, the agent will automatically join the team. These rules will be evaluated once each 24 hours to better reflect the AD computer state in AD.
The AD Group rule uses the group name as the Value, such as Test_Group_1. The Environment Variable rule uses the environment variable name as the Value, such as env var value 1. The Organizational Unit (OU) rule requires a distinguished name sequence as the Value, such as CN=James Smith,OU=Sales,DC=Ivantosi,DC=COM. Individual OU names are not unique in AD so they do not work here.
Automatic Job Scheduling
With Automatic Job scheduling you can schedule a Project or a single Module for automatic execution when new Agents are added to a Team or when Agents are removed from a Team. This is supported for explicit Team members, as well as rule based Team members. Jobs for new Team members are typically used to add new functionality to a computer. Jobs for removed Team members are typically used to remove old functionality from a computer.
For example, you can configure a Job Install Dispatcher to run automatically on Agents that are made member of the Team Dispatchers, and a Job Remove Dispatcher on Agents that are removed from that Team. Any automatic Job Scheduling applies to both directly assigned memberships and rule-based memberships, and applies to members of nested Teams as well as direct members.
- When configuring Team rules:
- You can specify multiple IP addresses or MAC addresses. Separate multiple entries with a semi-colon (;).
- Each IP address must be validated against all Team rules based on IP address.
- For AND rules: one of the Agent's IP addresses must apply to ALL IP address rules.
- For OR rules: one of the Agent's IP addresses must apply to at least 1 IP address rule.
- MAC addresses must be specified in this hexadecimal format: XX:XX:XX:XX:XX:XX.
For example: 00:0C:29:23:51:A3
- You can use pattern matching when defining a Team rule based on IP address. For example, suppose you want to configure a Team for any Agent whose IP address starts with a specific set of numbers. Instead of specifying the IP addresses of each individual Agent, you can use a pattern. This not only applies the rule to all existing Agents whose IP address match the specified pattern, but also to new Agents:
Suppose you want to configure a Team for any Agent whose IP address starts with a specific set of numbers. Instead of specifying the IP addresses of each individual Agent, you can use a pattern. This not only applies the rule to all existing Agents whose IP address match the specified pattern, but also to new Agents:
Starting with 10.1.7
Applies to any Agent whose IP address starts with 10.1.7
Starting with 10.1
Applies to any Agent whose IP address starts with 10.1, followed by a single digit and then any number
- If membership of a Team is determined by a Team rule based on IP address, you can verify the IP addresses of the Agents that have been added to the Team by scheduling a Task Query TCP/IP Properties.
- A Team rule based on IP address in combination with SUBNET (or network prefix), is not supported for IPv6 addresses.
- On the Properties tab, select Do not allow add to team outside console to prevent Agents from being added to a Team from outside the Console, for example through an MSI property or a registry value.