In this article I will describe a way of getting a better overview on which Dispatcher(s) can be contacted by the Agents, when using different configuration options.


It is necessary to understand the different settings that can be configured in the Dispatcher settings. Here are some basics which should be clear:


Dispatcher Discovery:

  • Autodetect (Multicast)
  • Use Dispatcher Address List (optional: First try Autodetect) (Unicast)


Dispatcher Location:

  • Retrieve complete Dispatcher list after discovery (All known Dispatchers will be used by the Agent)
  • Only use discovered Dispatchers (Only the defined Dispatchers can be used by the Agent)



The FIRST METHOD to get a better view on which Dispatcher can be contacted by a single Agent.


For this we have to start the Agent interactively. This can be done by executing the agent.exe with the /interactive switch.Logon to the computer which has the Agent+ software installed. When a default installation is used, you should use the following command line:

"C:\Program Files\RES\Automation\Agent\agent.exe" /interactive


A new Window will pop up when the RES Automation Agent service is already active.



Although it's not necessary to stop the already running 'RES Automation Agent+ Service' , it's highly advisable for a reliable test. When the Agent+ is started interactively, a new Agent.exe process will be started with the credentials of the currently logged in user. If you don’t stop the already running service, 2 Agent.exe processes will be running. This can lead to unpredictable results.


Click [Yes] and stop the Agent+ service.


In the following screen the RES ONE Automation environment which is used should be shown. Here you can also configure the Dispatcher Location and Dispatcher Discovery settings.

The RES ONE Automation Environment will be retrieved and shown. If no RES ONE Automation Environment is shown, first try the [Refresh] button. If this isn’t helpful, you can try configuring a Dispatcher in the ‘Optional Dispatcher Address List’.

Again click the [Refresh] button.


Bare in mind that 'First try autodetect' will use Multicast to communicate to the Dispatchers. If this kind of traffic is blocked, no Automation environment will be retrieved.


When no Ivanti Automation Environment is retrieved at all, please check if the Dispatcher services are running and are able to accept connections and can communicate with the database. Otherwise this tool can’t be used. The [OK] button will stay greyed-out. When multiple environments are detected, these will be shown. Select the Ivanti Automation Environment which needs to be used.

Click [OK].



The configuration as defined in the Ivanti Automation Console for this Agent+, will be configured in registry settings in the Agents registry. These settings will automatically be configured when this tool is started, as shown in the next screenshot. In here you are able to see which Dispatcher(s) can be contacted and which traffic is communicated.


If there is active communication visible, the Agent is able to connect to the Dispatcher and the selected environment.




By starting the Agent interactively, it's possible to view which Dispatcher(s) can be contacted. This is useful when you want to check the connection on one Agent.



  • The above can also be used to troubleshoot a module which doesn't execute properly if the Agent is started by the service.
    • If the Agent is started by the service, it will run under the SYSTEM credentials
    • If the Agent is started interactively, it will run under the credentials of the currently logged in user.
      This can make a difference in executing some tasks.
  • The described method can be used for Agent+ installations and also for the legacy Agent.




The SECOND METHOD to get a better view on which Dispatcher can be contacted by a single or by multiple  Agents.


When you want to test the results of a change in configuration or when you want to check the Dispatcher connections of multiple Agents, It´s easier to use the "RES Automation Manager Dispatchers (Discover)" task, instead of logging on to each computer separately.

With this task you are able to test different setting and view which Dispatcher(s) can be reached.


No configuration changes will be made to the Agents when using this task!


Create a new Module and add the "RES ONE Automation Dispatchers (Discover)" task.



You can use the current Agent settings or use custom settings by configuring the desired Dispatcher discovery, location and recovery settings.



Schedule the Module as a job to a single or to multiple Agents.



After the job has finished, open the Job results, select the [Tasks] tab and click [Details...]



The results of the task is shown in an overview. In the screenshot above, both Dispatchers are available for all Agents with the settings as configured in the task.


Keep in mind that no changes are made to the Agents now. To make Dispatcher Discovery changes to one or more Agents, these can be changed on a Global level, Team level or per Agent.