Ivanti Automation powered by RES

Home 

Ivanti Automation release notes

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

To see release notes for earlier releases, visit this page:

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

 

Ivanti Automation 2019.2 release notes

Known issues

Content of Tasks in a Recurring Job cannot be opened in the Ivanti Automation Console

Note: This was resolved in 2019.0, but it introduced a more relevant issue. This known issue will be resolved in the next release.

More information

No “Configure Secure Binding” screen available when connecting to an empty Ivanti Automation database

This issue was found in 2019.0.1 and is still unresolved.

More information

Resolved issues

Changing the account of a Service with Ivanti Automation fails with Error 1069

More information

Status and Duration of tasks in a 'Timed out' Ivanti Automation Job are incorrect

More information

The Reboot Computer task fails but is executed and shows the result: 'A timeout has occurred'

More information

Condition based on an Environment Variable fails after a reboot task

More information

The 'Install Microsoft Updates' task fails to install bundled updates

More information

The Ivanti Automation Agent+ service is not always started after the start of the system

More information

Error: Failed to import Building Blocks when importing an Ivanti Automation Building block

More information

Multiple environment variables are not appended correctly

More information

Ivanti Automation Agent goes offline due to a task Query Active Directory

More information

The activation email address is incorrect in Ivanti Automation

More information

Parameter values are not correctly overwritten when used from a custom .ini file

More information

Teams are showing all agents instead of only team agents

More information

The Query Active Directory task can make the Agent go offline

More information

Parameters are overwritten by PowerShell variables

More information

Perform File Operations with action Edit/Create INI does not work correctly with Variables

More information

Web Service Invoke task fails when testing the WSDL link

More information

What's new

Auto-update for the Unix/Linux/Mac OS X agents

The Unix/Linux/Mac OS X agents now auto-update. The agent packages are now part of the Upgrade Pack and present in the Components node of the Administration section in the Console. In the future, Automation releases that include new Unix/Linux/Mac OS X agents will auto-update themselves.

IMPORTANT NOTE: The Unix/Linux/Mac OS X agents in this release don't work with older dispatcher versions.

CentOS Linux 6 and 7 support

CentOS is now a supported Linux version. Team rules or tasks conditions can be configured based on the CentOS Unix/Linux operating system version.

Restart Windows agents from the Console

You can now restart the Windows agent from the Console. Console users can select a Windows agent from the Topology node and either click the toolbar's Recycle button or right-click and click Recycle. This will restart the agent service on the selected agent machine. The Management Portal also supports this feature.

Remove duplicate agents while preserving job history

This release introduces the ability to remove duplicate agents from your environment while keeping the job history attached to the “new – online” agent. For various reasons, duplicate agents can be present in any environment, one online agent and one offline agent. For example, this could happen when a machine is transferred from domain A to domain B while having the identification method configured with “Computer domain name & NetBIOS name”. Jobs were executed on the "old – offline" agent but also on the "new – online" agent.

Prior to version 2019.2, if the "old – offline" agent was removed without removing its job history, that job history remained disconnected from any agent. Using this new option, you can select two agents that have the same name in the Topology node, one online and one offline. Then, click the toolbar's Remove duplicate button or right-click and click Remove duplicate. The "old – offline" agent will be removed from the environment and its job history will be transferred to the "new – online" agent.

 

Ivanti Automation 2019.1 release notes

Known issues

Content of Tasks in a Recurring Job cannot be opened in the Ivanti Automation Console

Note: This was resolved in 2019.0, but it introduced a more relevant issue. This known issue will be resolved in the next release.

More information

No “Configure Secure Binding” screen available when connecting to an empty Ivanti Automation database

This issue was found in 2019.0.1 and is still unresolved.

More information

Resolved issues

Leading backslash is missing resolving a Global Variable or Parameter when used in Apply Registry Setting

More information

Removing the Home Folder property from the Manage AD User task doesn't work

More information

The countdown timer of a Postpone Job task is not available in an active job if started on an Ivanti Automation Agent+

More information

An Ivanti Automation Agent is not executing jobs and the error: 'Object not set to an instance of an object' in the event viewer is logged

More information

Function @FINDINFILE does not work in Ivanti Automation Agent+

More information

Adding multiple parameters/variables to User Properties in the Manage Active Directory User task removes the first parameter/variable

More information

The duration of skipped tasks is incorrect in the Job History of an Ivanti Automation Job

More information

Ivanti Automation Dispatcher does not log all events in the Windows Application eventlog after upgrade to 2018.3 and higher

More information

Re-scheduled Runbook jobs using the Ivanti Automation Management Portal are not executed

More information

The Job results for PowerShell task does not contain console output, error log, or grabbed log file when using Ivanti Automation Management Portal

More information

Re-scheduling or viewing a runbook job result in the Ivanti Automation Management Portal will display an error

More information

What's new

Windows Authentication feature re-designed

When using Windows Authentication to access the Ivanti Automation Console, a single account (designated account) can be used now instead of providing read/write access to all users that need access to the Ivanti Automation Console. More information

SUDO mode for Unix/Linux/macOS agent

The SUDO mode allows the Unix/Linux/macOS agent to run as a non-root account. The only prerequisite is to have that user added as a passwordless user in the sudoers file. More information

Change the trace level for Unix/Linux/macOS agent using resamad.xml

The default trace level for the Unix/Linux/macOS agent can be changed by modifying a node in the resamad.xml file. More information

Removed autodetect switch from the Unix/Linux agent configuration command line

Autodetect is no longer supported for the Unix/Linux agent. We have removed the possibility to configure it to autodetect an Ivanti Automation environment.

GDPR Search and Replace (Microsoft SQL and IBM DB2 database types supported for the moment)

A command line option is available to search and/or to replace information that can be considered as PI in the GDPR context. More information

Added support for IPv6 when having MAC address as identification method

IPv6 enabled network interface cards are now taken into consideration when evaluating the identification method based on MAC address. These NICs are evaluated only if no IPv4 NIC is available/enabled. More information

Added support for Windows Server 2019

Windows Server 2019 is supported in Ivanti Automation 2019.1.

 

Ivanti Automation 2019.0.1 release notes

Known issues

Re-scheduled Runbook jobs using the Ivanti Automation Management Portal are not executed

More information

The Job results for PowerShell task does not contain console output, error log, or grabbed log file when using Ivanti Automation Management Portal

More information

Re-scheduling or viewing a runbook job result in the Ivanti Automation Management Portal will display an error

More information

No “Configure Secure Binding” screen available when connecting to an empty Ivanti Automation database

More information

Resolved issues

When upgrading from Ivanti Automation 2018.3.1 to Automation 2019.0, this error appears: "The Ivanti Automation Management Portal Setup wizard ended prematurely"

More information

No “Configure Secure Binding” screen available when connecting to an empty Ivanti Automation database

More information

Changing "First try autodetect" in the Ivanti Automation global settings does not change the setting on team level

More information

The option to choose an installed certificate is still present in the datastore wizard in Ivanti Automation

More information

HOWTO: Configure the Ivanti Automation Agent check interval

More information

Scheduled jobs via WMC.exe command line API tool are not executed and are shown in the Automation Portal with the status requested

More information

Some security related features are missing in the Standard Edition of Ivanti Automation

More information

Error in frmEditJob.fysnDetermineOrderParam: 13 - Type mismatch when scheduling a runbook after the upgrade to Ivanti Automation 2019.0

More information

Execute command module does not execute the %script%-reference correctly after upgrade to Ivanti Automation 2019.0

More information

Error: The Ivanti Automation Management Portal Setup wizard ended prematurely after the upgrade from Ivanti Automation 2018.3.1 or 2019.0 to a newer version

More information

 

Ivanti Automation 2019.0 release notes

Known issues

When upgrading from Ivanti Automation 2018.3.1 to Automation 2019.0, this error appears: "The Ivanti Automation Management Portal Setup wizard ended prematurely"

More information

No “Configure Secure Binding” screen available when connecting to an empty Ivanti Automation database

More information

Resolved issues

Unix/Linux Automation Agents show as offline in the Ivanti Automation Console

More information

Permissions on a Teams parent folder are not inherited by the Ivanti Automation Agents

More information

Reboot computer task doesn't actually reboot the computer

More information

Push deployment of an Ivanti Automation component to local machine fails on "Remove previous deployment instance"

More information

Current activity in the Ivanti Automation Agent job is empty since the upgrade to Ivanti Automation 2018.x

More information

No file(s) found when sending an attachment with a wildcard via the send e-mail option in Ivanti Automation

More information

Content of Tasks in a Recurring Job cannot be opened in the Ivanti Automation Console

More information

Creating a multi-line REG_MULTI_SZ registry value using Ivanti Automation will corrupt the entry on the Agent

More information

Ivanti Automation module apply registry setting does not work with special characters

More information

Cannot set an unexpanded reference with task "Set Environment Variables"

More information

Using task "Set Environment Variables" for value PATH results in unusable unexpanded references like %SYSTEMROOT%

More information

Unable to read job variables with PowerShell in Ivanti Automation Agent+ if security context is used

More information

No log file is available in the Ivanti Automation job results of a Windows PowerShell Script task

More information

Event ID 1011 with source RESWAS is created every 10 seconds in the Application Event Viewer in combination with Event ID 1013 with source RESWAS

More information

Ivanti Automation Dispatcher+ is not downloading resources from the Master Dispatcher

More information

Automation Agent+ doesn't reconnect after a disconnect

More information

Unable to change the position of the runbook parameters after the upgrade to Ivanti Automation 2018.3

More information

Users from child domain or two-way trust domain in a Domain Local Group are not resolved when logging into the Ivanti Automation Management Portal

More information

Export Job Results parameter for WMC.exe command line no longer works after upgrade to 2018.3

More information

"ERROR in sharedConditions.fysnTakeConditionAction: 5 - Invalid procedure call or argument" appears during the schedule of a job

More information

Project parameters are not read correctly with the Ivanti Automation Agent+

More information

Sorting on duration time in the Ivanti Automation job history does not sort correctly

More information

Ivanti Automation jobs are not scheduled via the Ivanti Automation webapi

More information

What's new

In Automation 2019.0, all autodetect functionality is no longer supported

In Ivanti Automation 2019.0, the dispatcher autodetect functionality that was present in previous versions is no longer supported. It is considered obsolete and not secure. All autodetect configuration from global settings, team, and the agent level needs to be removed in order to successfully upgrade to 2019.0 or later from versions prior to 2019.0. For more information, see Dispatcher Detection settings.

New Run Book "Determine parameter order by usage" option

Enabling this new option automatically sorts Run Book parameters by how often they are used. If this option is disabled, you can arrange parameters in any order needed and that arrangement will be preserved.

Updated DBProtocolEncryption deployment options

Consoles and dispatchers have new protocol encryption deployment options and behavior. Console encryption options are "Enabled" and "Disabled". Dispatchers have new "EnabledWithoutValidateCertificate" and "EnableWithValidateCertificate" options. For more information, see the "DBProtocolEncryption" section in Installing Ivanti Automation.

New SCUSER and SCPASSWORD options for unattended Dispatcher deployments that use Windows authentication

Use these options instead of DBUSER and DBPASSWORD if you want to specify a Windows service account user. For more information, see Installing Dispatchers.

Export2xml formats for exported Job Results

Ivanti Automation now supports -export2xml and /action=export2xml options. For more information, see Exporting Job Results.

New reboot/shutdown task options and behavior

Automation has redesigned the Force close of running applications and Shutdown timeout options for reboot/shutdown tasks. For more information, see Reboot Computer, Shutdown Computer.

Updated Ivanti Identity Director integration method

If you are using Ivanti Identity Director 2019.0 or newer, specify the URL used to open the Identity Director Management Portal in the form of:

http(s)://<hostname>:<port_if_not_standard>/IdentityDirector

Run Book publishing is no longer supported.

Updated Linux agent

An updated Linux Agent is available in this version containing a bug fix (see the ”Resolved issues” section). This updated agent includes new AddToTeam functionality that is similar to the Windows Agent AddToTeam install-time argument. A new switch was added to the agent initial configuration command, -t”Team Name”. This can be useful when you want the agent to automatically get its settings from a specific primary team. Multiple teams can be specified: -t"Linux Team1;Linux Team2; Linux Team3".

Microsoft SQL Server 2017 is now a supported database

 

 


Was this article useful?    

The topic was:

Inaccurate

Incomplete

Not what I expected

Other