Ivanti Automation release notes

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

To see release notes for earlier releases, visit these pages:

https://help.ivanti.com/res/help/en_US/IA/2019/Admin/Default.htm#cshid=relnotes

https://help.ivanti.com/res/help/en_US/IA/2018/Admin/Default.htm#cshid=relnotes

 

Ivanti Automation 2020.0 release notes

Known issues

None.

Resolved issues

Ivanti Automation Console has no option for force protocol encryption with certificate validation

More information

Enhancement: The information about the Automation database size is better specified

More information

Installing a Dispatcher on a machine fails from a Console with Protocol Encryption enabled

More information

Removing Job History with the build-in task Delete Automation Jobs will not delete jobs scheduled via an external tool

More information

Running a PowerShell command via Ivanti Automation to get the windows build numbers returns wrong information

More information

Passwords are visible during scheduling when used in the Execute Command line

More information

Unix/Linux Automation Agents goes offline in the Ivanti Automation Console

More information

Ivanti Automation Linux Agent 10.9.* uses sudo to execute shell /command scripts

More information

Already finished Job stays active in the Automation Console for several minutes

More information

The Query Database Statement task is not executed when the password is filled in by using a Parameter or Variable

More information

Download Unix/Linux resource fails while downloading a large resource to an Ivanti Automation 2019 or higher Unix/Linux Agent

More information

The Automation Console can't be started if it's installed via the Deploy Automation Component task

More information

Resizing the Ivanti Automation console changes the number of active agents

More information

Ivanti Automation Linux agent appears offline when downloading a large resource

More information

Sorting the scheduled jobs on Tags in the Management Portal results in the error: 'Object reference not set to an instance of an object'

More information

What's new

MSOLEDBSQL driver support for Protocol Encryption

As per Microsoft’s statement, support for Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL) was introduced in 2020.0. Stating with this version, this will be the prerequisite for being able to use the Force Protocol Encryption feature.

Having only Microsoft SQL Native Client on the machines running the Consoles and Dispatchers will keep the feature functional, but not configurable.

Starting with 2020.0, the Management Portal can also be configure to use Protocol Encryption.

View trace content in Console

Starting with 2020.0, agent traces can be activated, obtained, and deactivated from Console. This feature is available for windows agents having version 2020.0 or higher.

To use the feature, open the Agent properties, select the new tab called “Traces” and click on the “Enable” button. This will enable tracing on the selected agent. Press F5 to refresh the list of gathered trace files from the agent.

New command line option for unix/linux agent (--help or -h and –version)

In 2020.0 we have introduced a new command line option for the Unix/Linux agent.

Use “./resamad --help” or “./resamad -h” to get the help content. Use “./resamad –version” to see the agent version.

New task for changing team membership for agents

In 2020.0, a new task was introduced to change team membership for the configured agent(s). Input fields: Agent Name, Action (Add/Remove), Team(s) Name, Primary Team (Yes/No). Agent Name and Team(s) Name supports a text parameter. The parameter must be a GUID that corresponds to the Agent or Team.

New task to query team membership

In 2020.0, a new task was introduced to query the agents that are members of the specified team(s). Input fields: Team Name, Show offline agents. Output: a table with Team Name, Team GUID, Agent Name, Agent GUID, Agent State. Team Name input field supports a text parameter. The parameter must have a value of a Team GUID.

Changed default options for the command execute task

Starting with 2020.0, any new “Execute command” task will have the options “Execute command using the Windows command interpreter”, “Redirect standard output and standard error to logfiles”, and “Fail task if error log is generated” enabled by default.

Enhanced the Dispatcher WebAPI functionality (remove an agent from environment, change team membership, retrieve output parameters for a job)

Use the “removeagent” POST method to remove an agent from the environment (with or without its job history). More info can be found on the help page of the Dispatcher: http(s)://<dispatcher_address>/Dispatcher/SchedulingService/help/operations/RemoveAgent

Use the “agentmembership” POST method to change the team membership for agents. More info can be found on the help page of the Dispatcher: http(s)://<dispatcher_address>/Dispatcher/SchedulingService/ help/operations/AgentMembership

Use the “teammembership” POST method to change the agent members for a the specified team(s). More info can be found on the help page of the Dispatcher: http(s)://<dispatcher_address>/Dispatcher/SchedulingService/ help/operations/TeamMembership

Use the “outputparameters” GET method to get the output parameters for a specific job. More info can be found on the help page of the Dispatcher: http(s)://<dispatcher_address>/Dispatcher/SchedulingService/help/operations/GetOutputParms