Ivanti Automation release notes
Release notes for the following Ivanti Automation versions are available in this topic:
- Ivanti Automation 2019.3 release notes
- Ivanti Automation 2019.2 release notes
- Ivanti Automation 2019.1 release notes
- Ivanti Automation 2019.0.1 release notes
- Ivanti Automation 2019.0 release notes
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.3 release notes
Known issues
None.
Resolved issues
Scheduling a job might result in triggering another (non-related) job
dsDAL.OpenResultSetEx error on connecting Automation Console to Datastore after installing Microsoft Windows Cumulative Updates
The Launch Timeout feature is not functioning since Automation 2019.2
Registry value configured by the Apply Registry Settings Automation task is incorrect
Console Output tab missing in Job History if ErrorActionPreference Stop is used in PowerShell task
Error: "Failed to rename the downloaded powershell console file" appears when a PowerShell task is executed configured with a PowerShell Console file
Login to the Ivanti Automation Management Portal keeps looping, no login possible
Automation job fails on an Agent with different code page settings
The file operation tasks fails with the result: Error 1326 - The username or password is incorrect
The Automation Console service is not always started after the start of the computer
Removing a scheduled Ivanti Automation job could cause the job to be executed and the details of the job to be removed
Query Database Statement task doesn't show password Parameter or Variable in the task
The auto created parameter in the Query Database Statement task is a TEXT type instead of MULTI-LINE TEXT
User impersonation not working as expected in Execute Command and PowerShell tasks
What's new
Implement exit code evaluation for the "PowerShell" task
The PowerShell task now has options to evaluate configured script exit codes. The task can be failed or succeeded based on the exit code. This is the same type of configuration already present in the Command (Execute) task.
Mac/Linux/Unix agent recycle
You can now restart the Mac/Linux/Unix agent. Console users can select a Mac/Linux/Unix 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.
Agent, Dispatcher and Console summary to Management Portal topology view
Management Portal users can see the summary of their environment components: total number, online number, offline number, and versions. This is the same information already available in the Console.
Timestamp of last usage
In this version of Ivanti Automation we have introduced a way to see the usage of a particular module, project or runbook. In large environments this can be very useful when trying to decide if a particular module, project or runbook is of any use or should be deleted. We provide the number of executions and the timestamp of the last execution. This information is available in both the Console and the Management Portal.
Dispatcher to Agent mapping
In this version of Ivanti Automation, we have added a new column in the Console/Management Portal's Topology > Agents view: Last Contacted/Accessed Dispatcher. In this column we report the Dispatcher that is currently servicing the selected Agent. Dispatcher-to-Agent mapping should bring a much clearer picture of the environment.
Oracle and MySQL DB types planned of end of support
In the Upgrade Pack we have added a warning if the selected database type is Oracle or MySQL. These database types will no longer be supported in future releases. Please migrate the environment to one of the supported database types: MSSQL, Azure MSSQL, or IBM DB2.
Update product logos
This version of Ivanti Automation has new icons and logos.
Remove current licensing server GUI/functionality
The License Server tab from the Licensing section was removed from the Console. Ivanti is looking into other ways to manage licensing.
Multiple Console windows
Until this version, only one Console window was allowed. This version lets you open multiple Ivanti Automation Console windows.
Added ALL, ONLINE, and OFFLINE tabs in the Management Portal's Consoles view
In this version of Management Portal, we have introduced the tabbed view in the Topology > Consoles section. Now Management Portal users can filter the Consoles based on their state: ALL, ONLINE, or OFFLINE.
Improved licensing info in the Console's Licensing tab
Before this version, the licensing information present in the Console was referring to licenses, eg: 1 server = 6 licenses. This introduced a lot of confusion when ordering the total number of necessary licenses. This version of Ivanti Automation refers to license points: eg: 1 server = 6 license points.
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.
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.
The Launch Timeout feature is not functioning since Automation 2019.2
Resolved issues
Changing the account of a Service with Ivanti Automation fails with Error 1069
Status and Duration of tasks in a 'Timed out' Ivanti Automation Job are incorrect
The Reboot Computer task fails but is executed and shows the result: 'A timeout has occurred'
Condition based on an Environment Variable fails after a reboot task
The 'Install Microsoft Updates' task fails to install bundled updates
The Ivanti Automation Agent+ service is not always started after the start of the system
Error: Failed to import Building Blocks when importing an Ivanti Automation Building block
Multiple environment variables are not appended correctly
Ivanti Automation Agent goes offline due to a task Query Active Directory
The activation email address is incorrect in Ivanti Automation
Parameter values are not correctly overwritten when used from a custom .ini file
Teams are showing all agents instead of only team agents
The Query Active Directory task can make the Agent go offline
Parameters are overwritten by PowerShell variables
Perform File Operations with action Edit/Create INI does not work correctly with Variables
Web Service Invoke task fails when testing the WSDL link
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.
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.
Resolved issues
Leading backslash is missing resolving a Global Variable or Parameter when used in Apply Registry Setting
Removing the Home Folder property from the Manage AD User task doesn't work
The countdown timer of a Postpone Job task is not available in an active job if started on an Ivanti Automation Agent+
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
Function @FINDINFILE does not work in Ivanti Automation Agent+
Adding multiple parameters/variables to User Properties in the Manage Active Directory User task removes the first parameter/variable
The duration of skipped tasks is incorrect in the Job History of an Ivanti Automation Job
Ivanti Automation Dispatcher does not log all events in the Windows Application eventlog after upgrade to 2018.3 and higher
Re-scheduled Runbook jobs using the Ivanti Automation Management Portal are not executed
The Job results for PowerShell task does not contain console output, error log, or grabbed log file when using Ivanti Automation Management Portal
Re-scheduling or viewing a runbook job result in the Ivanti Automation Management Portal will display an error
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
The Job results for PowerShell task does not contain console output, error log, or grabbed log file when using Ivanti Automation Management Portal
Re-scheduling or viewing a runbook job result in the Ivanti Automation Management Portal will display an error
No “Configure Secure Binding” screen available when connecting to an empty Ivanti Automation database
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"
No “Configure Secure Binding” screen available when connecting to an empty Ivanti Automation database
Changing "First try autodetect" in the Ivanti Automation global settings does not change the setting on team level
The option to choose an installed certificate is still present in the datastore wizard in Ivanti Automation
HOWTO: Configure the Ivanti Automation Agent check interval
Scheduled jobs via WMC.exe command line API tool are not executed and are shown in the Automation Portal with the status requested
Some security related features are missing in the Standard Edition of Ivanti Automation
Error in frmEditJob.fysnDetermineOrderParam: 13 - Type mismatch when scheduling a runbook after the upgrade to Ivanti Automation 2019.0
Execute command module does not execute the %script%-reference correctly after upgrade to Ivanti Automation 2019.0
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
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"
No “Configure Secure Binding” screen available when connecting to an empty Ivanti Automation database
Resolved issues
Unix/Linux Automation Agents show as offline in the Ivanti Automation Console
Permissions on a Teams parent folder are not inherited by the Ivanti Automation Agents
Reboot computer task doesn't actually reboot the computer
Push deployment of an Ivanti Automation component to local machine fails on "Remove previous deployment instance"
Current activity in the Ivanti Automation Agent job is empty since the upgrade to Ivanti Automation 2018.x
No file(s) found when sending an attachment with a wildcard via the send e-mail option in Ivanti Automation
Content of Tasks in a Recurring Job cannot be opened in the Ivanti Automation Console
Creating a multi-line REG_MULTI_SZ registry value using Ivanti Automation will corrupt the entry on the Agent
Ivanti Automation module apply registry setting does not work with special characters
Cannot set an unexpanded reference with task "Set Environment Variables"
Using task "Set Environment Variables" for value PATH results in unusable unexpanded references like %SYSTEMROOT%
Unable to read job variables with PowerShell in Ivanti Automation Agent+ if security context is used
No log file is available in the Ivanti Automation job results of a Windows PowerShell Script task
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
Ivanti Automation Dispatcher+ is not downloading resources from the Master Dispatcher
Automation Agent+ doesn't reconnect after a disconnect
Unable to change the position of the runbook parameters after the upgrade to Ivanti Automation 2018.3
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
Export Job Results parameter for WMC.exe command line no longer works after upgrade to 2018.3
"ERROR in sharedConditions.fysnTakeConditionAction: 5 - Invalid procedure call or argument" appears during the schedule of a job
Project parameters are not read correctly with the Ivanti Automation Agent+
Sorting on duration time in the Ivanti Automation job history does not sort correctly
Ivanti Automation jobs are not scheduled via the Ivanti Automation webapi
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