Command-line options
You can perform the following Console actions from a command line:
- Adding or editing a Resource
- Changing Agent connection settings
- Changing Dispatcher connection settings
- Creating a Building Block for a Run Book
- Exporting Job Results
- Exporting licenses
- Importing Building Blocks
- Installing Agents
- Installing Consoles
- Installing Dispatchers
- Installing Ivanti Automation
- Scheduling Jobs
- Solving a Console lockout
Return Code
When you execute an action in the Console from the command line, you get a return code reflecting the status.
The execution of actions from the command line include:
- Job Scheduling
- Importing Building Blocks
- Creating Building Blocks for a Run Book
- Exporting Job Results
- Adding or Editing a Resource
The status return is given when started from a Microsoft Windows Batch/PowerShell script and when started from a Ivanti Automation Task Command Execute.
Overview of return codes:
Code |
Explanation |
Applicable action |
0 |
Success |
general |
1 |
Failed |
general |
2 |
Aborted |
general |
3 |
Canceled |
general |
4 |
Completed with errors |
general |
5 |
Failed to login. This code will be returned if the global Password Security Policy has not been met. |
general |
6 |
Source not found or entered. |
newresource / editresource |
7 |
Folder not found or incorrect value. |
newresource |
8 |
Target type not correct. |
newresource / editresource |
9 |
The security role entered for "/user" has no modify access to the resources node. |
newresource / editresource |
10 |
The special parameter value was not recognized. |
newresource |
11 |
Edit Resource Failed: when saving changes to the Datastore. |
editresource |
12 |
New Resource Failed: when saving the new resource to the Datastore. |
newresource |
13 |
The GUID for the target resource to edit is invalid or not found. |
editresource |
14 |
Object type does not exist. |
createbb |
15 |
Object GUID does not exist or is invalid. |
createbb |
16 |
Invalid destination file. |
createbb |