Installing Agents
Deploy an Agent unattended if, for example, you want to deploy it on many computers at once using a command line. When you deploy an Agent unattended, it is not necessary to preconfigure it. Unattended deployments can be scripted, for RIS or BareMetal installations.
- Open the Console and go to Administration > Components.
- Right-click the relevant installation file and choose Save component as:
- Ivanti Automation Agent-x.x.x.x.msi for Agents
- Ivanti Automation Agent+(x64)-x-x-x-x.msi for Agents+ on 64-bit Microsoft Windows versions
- Ivanti Automation Agent+(x86)-x-x-x-x.msi for Agents+ on 32-bit Microsoft Windows versions
- Do not preconfigure the MSI file.
- Save the MSI file to the desired location.
- At the desired location, apply the following public properties to the MSI file in a command line:
Property |
Functionality |
SITELICENSE |
Specifies the Site ID (case-sensitive). You can find this at Setup > Licensing in the Console. |
DISPATCHERLIST |
This property is optional. Use this property to specify the names or GUIDs of Dispatchers to use. Separate multiple entries with a semi-colon (;). |
DISPATCHERGETLIST |
Specifies whether the Agent should extend its list of Dispatchers by getting lists of Dispatchers from the discovered Dispatcher. Set the value:
|
DISPATCHERRECOVERY |
This property is optional. It specifies the action to take when Dispatcher discovery fails.
|
ADDTOTEAM |
This property is optional. To add the Agent as a member of one or more Teams, use this property to specify the names or GUIDs of the Teams. Separate multiple entries with a semi-colon (;). |
INVOKEPROJECT |
This property is optional. To run one or more Modules, Projects or Run Books on the new Agent as soon as it comes online, use this property to specify the GUIDs. You can find these GUIDs at Library > Modules, Projects or Run Books. Separate multiple entries with a semi-colon (;). Separate multiple entries with a semi-colon (;). When specifying a Run Book, make sure the Who fields in the Run Book are not filled in. This ensures the Run Book Jobs are executed on the new Agent. |
Additionally, if a rule-based Team exists at your Ivanti Automation environment and the option Automatically set as primary team for new members is selected for this Team, you can also apply the following public properties, to specify whether the Agent should inherit the Dispatcher detection settings of the primary Team when it is installed:
Property |
Functionality |
ISDEFDL |
Specifies whether the new Agent should use the default/global Dispatcher list when it comes online.
|
ISDEFDLS |
Specifies whether the new Agent should use the default/global Dispatcher location settings when it comes online.
|
ISDEFDR |
Specifies whether the new Agent should use the default/global Dispatcher recovery settings when it comes online.
|
Example
The site license for your Ivanti Automation environment is 'RES-519E-04D1-FCBA-434A-80EE-99F8-FD8D-2E04'. The Agent must connect to two Dispatchers after it has started, 'qa-w7test01' and 'qa-w2k8test10'. The Agent is not allowed to use other Dispatchers. After the Agent gets online, it must be member of the Team 'Exchange Servers', and it must run a Project with the following GUID: '{301620AE-B650-4B87-BA02-05B6114E1F83}'.
To install an Agent unattended, use:
Msiexec /i "C:\Ivanti Automation Agent-[version].msi" SITELICENSE="RES-519E-04D1-FCBA-434A-80EE-99F8-FD8D-2E04" DISPATCHERLIST="w7test01;w2k8test10" DISPATCHERGETLIST="0" ADDTOTEAM="Exchange Servers" INVOKEPROJECT="{301620AE-B650-4B87-BA02-05B6114E1F83}" /qn