Ivanti Automation Component (Deploy, Repair, Remove, Update)
- Use the Tasks Deploy, Repair and Remove Ivanti Automation Component to use an Agent as a proxy to deploy, repair or remove Consoles, Dispatchers and Agents.
- Use the Task Update Ivanti Automation Agent to force all Agents to update to the latest version, irrespective of the global setting Auto Update Agents.
- Tasks Deploy, Repair and Remove Ivanti Automation Component:
- As target computer, you can also type the host name, the fully-qualified domain name (FQDN) or the IP (IPv4 or IPv6) address of the target computer(s). The Scan Computers function does not support IPv6 address ranges. For legacy Agents, IPv6 is not supported.
- These Tasks require administrator credentials to connect to the target computer(s).
- It is not possible to deploy, repair or remove Agents for Unix/Linux or Agents for Mac OS X with this Tasks.
- Task Update Ivanti Automation Agents will force the executing Agent(s) to update to the latest version. If a new version of Ivanti Automation is available for the Agent, a Dispatcher will download all necessary data from the Datastore and store it. In its turn, the Agent will download all necessary data from the Dispatcher and update to the latest version. This may lead to issues in large environments with many Agents that all update at the same time. This behavior can be managed with the global setting Auto Update Agents. By executing a Task Update Ivanti Automation Agent, you can force Agents to update to the latest version, irrespective of this global setting.
- When repairing, removing or updating an Agent, the Agent that executes the Task must be different Agent than the target Agent: if the Task would be executed by an Agent that is also target computer, the Agent that executes the Task will also go offline and the Job will never finish.
- When repairing or removing a Dispatcher, your Ivanti Automation environment needs to contain at least two Dispatchers: one that is repaired or removed and one that remains. During the execution of the Task, the Dispatcher service will be stopped. If the Dispatcher is the only Dispatcher in your Ivanti Automation environment, this means that the Agent that executes the Task will also go offline and the Job will never finish.