Introduction
On-premise systems (both source and target) use the Provisioning service of the HelloID Agent to communicate with your organization's network and run tasks.
If you have multiple Agents installed in your network, you can specify which one(s) can be used by a given on-premise source or target system. This article will demonstrate how to do so.
Before proceeding, you must have at least one of the following set up:
Select an Agent
For a PowerShell source system
To select an Agent for a PowerShell source system, go to Source Systems and select the wrench button for the relevant source system:
Select the System tab, and then select the wrench button for Agent Configuration:
For a PowerShell or Active Directory target system
To select an Agent for a PowerShell or Active Directory target system, go to Target Systems and select the wrench button for the relevant target system:
On the General tab, select the wrench button for Agent Configuration:
Select an Agent
After selecting a wrench button, the Agent selection screen appears. It is the same regardless of the system type:
Agent tag selection
Here, you can apply one or more tags to the current system. When no tags are applied, the system can use all listed Agents. However, if one or more tags have been applied, only Agent(s) with at least one matching tag can be used.
You may define custom tags (see below), or select from a variety of pre-defined tags which correspond to the columns in the Agents list:
For example, in the above screenshot, the following pre-defined tags are available:
- >_ 5.1.17763.1
This tag represents a version of PowerShell. You will have a tag like this for each installed Agent running a unique version of PowerShell. This tag means that the current system can only use Agent(s) with this PowerShell version or higher. In other words, the version number is the minimum PowerShell version an Agent must be running to qualify for use by this system. - DEV159
This tag represents a single Agent (labeled by the name of the server it's installed on). It corresponds to the Computer name column in the Agents table (2). This tag means that the current system can use the specific associated Agent. - Default Pool
This tag represents an entire Agent Pool, which may contain one or more Agents. It corresponds to the Agent Pool column in the Agents table (2). This tag means that the current system can use any and all Agents in the associated Agent Pool. - T4EDEV.local
This tag represents a domain in your network, which may contain one or more Agents and/or Agent Pools. It corresponds to the Domain column in the Agents table (2). This tag means that the current system can use all Agents and/or Agent Pools running in the associated domain.
Agents
This list contains all Agents installed in your organization's network which are currently connected to your HelloID environment. You can qualify certain Agent(s) for use with the current system using tags, as described above.
Select an Agent's row in the list to add custom tags to it.
Note that when multiple Agents qualify for a system (as per their tags), HelloID Provisioning will load balance by selecting idle Agents before busy Agents.
To install or remove Agents from your HelloID environment, see Agents - Overview.
Agent details
This area contains information about the currently selected Agent in the Agents list.
Custom tags
Here, you can create custom tags to use in the Agent tag selection drop down, as described above. Custom tags are useful if the pre-defined tags are not specific enough to create the combination of Agents you want the current system to use.
Agent status
Each on-premise system displays current Agent availability next to the wrench button for Agent Configuration. For example:
The green dot indicates the number of installed Agents which are currently active, and the yellow dot indicates the number which have been inactive for more than two minutes.
When no Agents are available, a warning is shown:
In particular, this may happen when you have more than four Agents installed and you have Microsoft Exchange integration enabled for Active Directory (due to Exchange session limits).