Ivanti Automation powered by RES


Ivanti Automation release notes

Release notes for the following Ivanti Automation versions are available in this topic:

Ivanti Automation 2018.3 release notes

Known issues

There are currently no known issues with the 2018.3 release.

Resolved issues

A network connectivity loss could cause jobs to disappear from the Activity node in the Automation Console


This issue was also fixed in RES ONE Automation

In rare cases, scheduled jobs wouldn't move from the Scheduling node to the Activity node in the Automation Console


This issue was also fixed in RES ONE Automation

Offline Agent: Codepage 852 is being configured on the system


It isn't possible to log in to the Automation console through the group membership on another domain

Note that this fix can cause slow console log in times if user is part of many groups.

It isn't possible to download a resource that is stored in the Automation database


Dispatcher+ error: "Only one usage of each socket address (protocol/network address/port) is normally permitted"


This issue was also fixed in RES ONE Automation 10.2.200.

Wake On LAN not working in many instances


Using percentiles greater than 9% for comparing free disk space returns unexpected results

What's new

Add tags to a scheduled Run Book

When scheduling a Run Book from the Management Portal, you can add descriptive tags to the job. This extra information displays in a column in the main Job History view, without needing to drill into each Run Book detail.

New Automation Console task, Prepare for Image

This task launches the Prepare for Image wizard that is available inside Agent Properties. This wizard prepares the selected Agents for use in a computer image.

Run Book parameters are now presented in the order of execution/usage, instead of alphabetical order
Agent details are available in the Topology node in Management Portal
New tasks are available in the Management Portal

The following tasks are now available in the Management Portal:

  • Active Directory Group ( Create | Delete | Query )
  • Active Directory User ( Create | Delete )
  • Resource ( Download )
  • Microsoft Exchange Mailbox ( Create | Export | Disable )
  • Command ( Execute )
  • Database Statement ( Execute | Query )
  • Secure Shell (SSH) Commands ( Execute )
  • REST Request ( Execute )
  • Automation Component ( Deploy Agent | Remove Agent )
  • Unix/Linux Command ( Execute )
  • User Management ( Create | Query | Change Password | Delete | Unlock | Lock )
Ivanti Automation connectors can now be installed from the Management Portal

Under Setup > Addons, you can now install Automation connectors that are available from the Ivanti Marketplace.

The Automation 2018.3 upgrade pack "Select installed certificate" option has been removed

The upgrade pack's "Configure Secure Binding" page used to have a "Select installed certificate" option. This was removed because it only allowed you to select an existing self-signed certificate and it wasn't possible to select a real certificate.

Also, if your Automation installation is currently using a certificate and you use the "Generate self-signed certificate" option on that same page, all agents will need to be repaired so that they can get the new certificate information. We plan on resolving this repair issue in the next release.


Ivanti Automation 2018.2.1 release notes

Resolved issues

Urgent fix for Dispatcher API authentication issue



Ivanti Automation 2018.2 release notes

Known issues

There are currently no known issues with the 2018.2 release.

Resolved issues

Invalid object name 'sysdatabases' when opening the dashboard on the web portal


Skipped task by condition let the module be treated as failed


Error on copying Separators between Ivanti Automation modules


What's new

New task added – REST (execute)

Use the REST task to send API requests just like any other application would do (for example, Postman, available from https://www.getpostman.com). Construct the request with a third-party tool, like Postman, and get the request code pasted in the Request field.

Password Policy enforcement implemented in Ivanti Automation Management Portal.

Users will experience the same behavior in Password Security Policy configuration as in the desktop console.

Components page added in Ivanti Automation Management Portal under the Administration menu

The Components functionality from the desktop Console was ported into the Management Portal. Users can now download the Ivanti Automation Components from there.

Security page added into Ivanti Automation Management Portal in the top level menu

The Security functionality from the desktop Console was ported into the Management Portal. Users can now create logins, create administrative roles, and assign administrative roles to logins from there.

Topology page added in Ivanti Automation Management Portal in the top level menu

Users can get a list of the environment components in the Topology page. Note that it is only the list that is also present in Console at the Topology node. Component-specific actions, like add, repair, remove, etc., are not yet ported to the Management Portal.

Audit Trail placed in the top level menu of Ivanti Automation Management Portal

The Audit Trail button was placed in the top level menu. It used to be located under the Administration menu.

New entry added in the Audit Trail when an agent/dispatcher/console is added/repaired/removed

There's a new audit trail entry when an agent, dispatcher, or console is added, repaired, or removed.

Information section added in Ivanti Automation Management Portal

The Information section that is found in the desktop Console at Administration>Information was added in the Management Portal. Users can see information about the database connection, properties of the database, and sizes of the tables within the database

Global Variables now restricted from use based on administrative role permissions in Ivanti Automation Management Portal

Global Variables can be used in modules, projects, and Run Books only if the administrative role permission is set to allow or read-only. If a variable is configured with denied access, users can't add it in modules, projects, and Run Books.

Add-ons list and usage available in Ivanti Automation Management Portal

The Add-ons section was added. Users can see that Add-ons are available in the environment and can see their usage. Removal of the Add-ons isn't supported.

Database statement query output can be saved within a parameter

Users can now get the SQL query result into an Ivanti Automation parameter that can be further used/processed in other tasks within the same module.


Ivanti Automation 2018.1.1 release notes

Known issues

When the agent is removed or the certificate is changed in the environment, the certificate on the agent/dispatcher isn't removed

To resolve this, when changing a certificate use the "Certificate" task and remove the previously configured certificate.

Resolved issues

No communication between Ivanti Automation agent and Ivanti Automation dispatcher with a self-signed certificate


2018.1 Agent+ not in console after deployment with Prepare for Image


Last console user isn't being updated since the upgrade to the Agent+
RES ONE Resource Package is missing files
Agent resource download is limited to 4 MB
& value in the module parameter causes a PowerShell script to fail even if it ran successfully
Parameter not resolved in Manage AD User task

What's new

Added support for Subject Alternative Name to the certificate used to secure the communication between dispatchers and agents

When Subject Alternative Name is needed, customers can add the required values for this certificate field. This applies to both new installations and upgrades. Also, customers can use their own certificate that contains Subject Alternative Name values.

For example, Subject Alternative Name is needed when agent is connecting to the dispatcher using a DNS name different then the dispatcher's FQDN.

Agent repair is no longer necessary after changing the certificate

In 2018.1, when the certificate was changed, customers had to repair all agents in order the have the latest certificate for dispatcher/agent communication, even if the certificate was already placed in the proper location on the agent machine.

In 2018.1.1, after an upgrade or fresh install, deploy the new certificate to agent machines (you can do this with the "Certificate" task) and then just run the Upgrade Pack to reference the newly deployed certificate.

NOTE: Customers will still need to do an agent repair if they change the current certificate to an Ivanti self-signed one, since the customer has no means to deliver the certificate upfront to the agent machines (this certificate is generated on the fly during the Upgrade Pack Wizard).

Ivanti self-signed certificate is valid for 30 years

In 2018.1.1 the Ivanti self-signed certificate is valid for 30 years, while in 2018.1 the same type of certificate was valid for only two years

Startup message for Console and Management Portal

In 2018.1.1 customers can configure a message that will be displayed to any user launching the Ivanti Automation Console or browsing to the Ivanti Automation Management Portal.

Configure this message in the Global Settings > Others section > Startup message box.

Ivanti patent info in the user interface

In 2018.1.1, some user interface elements, such as the Console startup splash screen, contain references and links to Ivanti patent information.


Ivanti Automation 2018.1 release notes

These release notes are for Ivanti Automation 2018.1. Release notes for prior versions are in the PDF available here:

https://help.ivanti.com/res/help/en_US/ia/10.2/RES ONE Automation%20Release Notes

Known issues

Certificate management

When the agent is removed or the certificate is changed in the environment, the certificate on the agent/dispatcher isn't removed.

When the certificate is changed, the agents are not able to detect this and they will have to be repaired.

No support for Legacy Agent

Legacy Agents will not be upgraded to 2018.1 in existing environments or deployable in new environments. Support for Legacy Agents has been discontinued.

Resolved issues

After restarting the Ivanti Automation Dispatcher+, a Wake-on-LAN will be send to all agents with an active task


SSL is enabled by default in the 'Send mail message' option for Job notifications


After the upgrade to ROA v10.2, an error is shown when opening the licenses section


Unable to use the WebAPI base address with a “-“ character in its name in Ivanti Automation


Jobs are not always executed with ROA Agent+ (DSI 251543)


Checkbox for Advanced Properties on AD task shows Automation error: Server not operational (DSI 251594)
Parameter link after 10.2 upgrade (DSI 2551599)
Can't enable mail notification (DSI 251551)
Parameter doesn't resolve on apply registry task setting for REG_SZ or REG_MULTI_SZ (DSI 251552)

What's new

New (secure) communication model using port 3165 and certificates to validate communication between dispatchers and agents.

After upgrading to version 2018.1, agents and dispatchers will communicate via port 3165 (opened on dispatcher) and all communication will be validated using a certificate. When creating a new environment or when using the Upgrade Pack, you will be prompted to either use a self-signed certificate created by Ivanti Automation (CN = Ivanti Self Signed Root), or to use your own certificate that meets these requirements:

  • "Certificate signing” on Key Usage
  • Placed in the Local Computer/Personal/Certificates container
  • Must be exportable and have a private key

At any time you can change the certificate by using the Upgrade Pack and selecting the appropriate option. When using a custom certificate, you must run the Upgrade Pack as an elevated user to have access to the Local Computer/Personal/Certificates container where your certificate should be placed. If you don't run elevated, your certificate won't appear in the available certificates list.

NOTE: On the dispatcher, the certificate is placed in the Local Computer/Personal/Certificates container, while on the agent it's placed in the Local Computer/Trusted Root Certification Authorities/Certificates container.

Rebranded products

RES ONE Automation is now Ivanti Automation.

New (external) version

The Ivanti Automation product version number for this release is 2018.1. Internally, version 2018.1 is, and you may see version 10.3.x.x in some parts of the Automation user interface.

New recurrent scheduling option in Management Portal - CRON

In the Management Portal, support was added for CRON to schedule recurrent jobs.

New variable usage information in Management Portal

When editing an existing variable in the Management Portal, there's a new Usage view that shows a list of modules, projects, and runbooks using that variable.

New support for multiple returns when using the “Execute Windows PowerShell Script” task

Now you can define multiple parameters for the module containing the PowerShell task and reference them as “$global:<param_name>= <something>”. This allows you to get values for multiple parameters within the same task.

Dispatcher discovery default option changed

For new installs dispatcher discovery is no longer set to "Autodetect". It is set to "Use Dispatcher address list", and the list is empty. If any dispatchers are already deployed, add those here according to your needs.

Oracle case-sensitive login support

In 2018.1, support for case-sensitive logins when using Oracle databases was added. This is valid for new installations only. During the database creation wizard, make sure to use the Case-sensitive login checkbox accordingly. For example, if the "system" credentials are used when connecting to the Oracle server, this checkbox shouldn't be used. When creating the credentials for the new database, the checkbox should be used.

Also, if the certificate needs to be changed, use the Upgrade Pack. When connecting to the Oracle server, the case-sensitive login checkbox isn't available. Just input the username between double quotes(""), for example "UseR1".

Audit trail new entry when force-removing a component from topology

When a component is removed from a machine that isn't accessible, the user is prompted to remove the component only from the database. If YES is selected, a new Audit Trail entry is generated to reflect this.

Action: delete; Category: agent; Object: <agent GUID>; Description: Removed from database only

Support for SQL 2017

Added support for SQL 2017.

Ivanti Automation release notes

Resolved issues

Dispatcher+ error: "Only one usage of each socket address (protocol/network address/port) is normally permitted"


Urgent fix for Dispatcher API authentication issue



Was this article useful?    

The topic was:



Not what I expected