Ivanti Automation 2023.4 Release Notes
What's New
Updated logo
The logo for Ivanti Automation has been updated to reflect the latest design.
Resolved issues
The following issues were resolved in this release:
| Problem ID | Title |
| 93334 | Automation team based on Operating System Version Microsoft Windows 11 rule also includes Windows 10 computers. More information |
| 93646 |
Dispatchers are stuck at random times. More information |
| 93652 | Building block created using 'Automation/API/BuildingBlocks/Create' is missing the Run Elevated info: <runelevated>yes</runelevated>. More information |
| 94122 | Runbook containing multiple projects are giving visual inconsistency. More information |
| 94218 | Netbios name resolve is not working anymore in task Install Windows Installer package with a resource located on fileshare (UNC). More information |
| 94406 | The previously used Root certificate information still resides in the Automation Agent MSI file. More information |
|
CVE-2022-44569 |
Resolved an Automation Manager authentication bypass vulnerability |
Note: Ivanti would like to thank Remko Weijnen's contribution in discovering and responsibly reporting vulnerability CVE-2022-44569.
Release Notes for previous versions of Ivanti Automation 2023
Ivanti Automation 2023.3
Resolved issues
The following issues were resolved in this release:
| Problem ID | Title |
| 92405 | Projects still runs in prepare for image task, regardless if the project is enabled or disabled. More information |
| 92597 | The File Operations task fails when wildcards are used in the path. More information |
| 93108 | Option grab log file in perform unattended installation task does not work in Ivanti Automation. More information |
|
93464 |
The Install Windows Installer Package task fails after upgrade to 10.22.0.0 More information |
| 93850 | The spelling of the word 'following' is incorrect in the pop-up that appears when deleting a team that has a task in it. More information |
Ivanti Automation 2023.2.0.1
Resolved issues
The following issues were resolved in this release:
| Problem ID | Title |
| 93451 | Runbook is not fully processed when a Project is used in the Runbook job in Ivanti Automation 2023.2.0.0 More information |
Resolved in release 2023.2(.0.0):
| Problem ID | Title |
| 90177 | The View button for Resulting Tasks in scheduled recurring Jobs is not working. More information |
|
92477 |
Task Install Windows Installer Package fails after upgrade to Ivanti Automation 2023.1 (10.22.0.0). More information |
| 92587 | After installing Ivanti Automation 2022.4: File Operations task to move folder content fails: Access to the path is denied. More information |
| 92868 | The Perform Unattended Installation task fails after updating Ivanti Automation. More information |
|
92929 |
Task Apply Registry Settings using Expandable String Values adds additional backslashes in the data value. More information |
|
93038 |
Module Conditions in a Project are not visible when viewed via the Job History. |
Released in 2023.2(.0.0), but reverted:
| Problem ID | Title |
| 92405 (reverted) |
Projects still run in Prepare for Image task regardless if the project is enabled or disabled. More information |
Ivanti Automation 2023.1
Resolved issues
The following issues were resolved in this release:
| Problem ID | Title |
| 92110 | The PowerShell Core (Execute) task does not show the Console Output tab in the executed job details. More information |
| 92144 | After editing a configured Condition based on a registry value, the following error is shown: A string literal was not closed. More information |
| 91747 | After an Ivanti Automation upgrade is performed, the C:\IA_RecycleBin folder not auto-cleaned up. More information |
| 91932 | The order of jobs scheduled on multiple agents is incorrect in the Activity and Job History tabs. More information |
| 91976 | The Query Parameters task behaves differently, causing Execute Commands tasks to fail. More information |
|
91966 |
When the Set Environment Variables task is used, the Variable name is changed to case-sensitive. More information |
Release Notes for Ivanti Automation 2022
Ivanti Automation 2022.4
What's New
Tracing optimizations
Starting with Ivanti Automation 2022.4, you have more control over how much disk space tracing takes up. By implementing the MaxLogFileSizeMB, FreeDiskspacePercent, and FileLogThreshold registers, you can set up the maximum amount of megabytes a trace file can take up before rewriting itself, how much space needs to be available in order for the trace entries to be written in the trace file, and control what trace levels should be written.
Resolved issues
The following issues were resolved in this release:
| Problem ID | Title |
| 91488 | If the date/time information stored in the TelemetryLastSend registry key has an incorrect format, the Automation Dispatcher logs the following error in the Microsoft Windows Event Viewer: String was not recognized as a valid DateTime. More information |
| 91321 | Handles on agent.exe are not completely released after running Powershell tasks in Ivanti Automation. More information |
| 91010 | Missing Global option in the drop down menu within Topology > Teams settings in Ivanti Automation. More information |
| 91513 | The REST Request task fails with the following error: An error has occurred. More information |
| 91138 | The Deploy Automation Components task does not contain connection information when used to deploy the Ivanti Automation Console. More information |
|
91477 |
When upgrading the Automation environment, the upgrade pack requests credentials to continue. More information |
|
91079 |
Recurring schedule stops and is not reschedules as expected. More information |
|
91362 |
The Apply Registry Settings task fails when the REG_MULTI_SZ registry entry is set with an empty Data field. More information |
|
90574 |
When the use of Comments on Versioning is avoided when editing a Runbook, it causes the Ivanti Automation Console to freeze. More information |
| 91170 | Filtering the Job History in Ivanti Automation does not work since version 2022.3. More information |
| 91011 | The Perform Single File Operation task in Ivanti Automation does not accept * to delete subfolders and content in subfolders. More information |
| 91020 | Tasks using Global Variables of type Credentials fail with the following error: 1326 The username or password is incorrect. More information |
| 91212 | When an Automation Resource Package is used in the Perform Unattended Installation task, the task fails with the following errors: Process failed to start or Timeout expired - Process terminated. More information |
| 91476 |
Visual view in the Ivanti Automation Console seems not to be correct, order is not as it should be. |
Ivanti Automation 2022.3.1
Resolved issues
The following issues were resolved in this release:
| Problem ID | Title |
| 90807 | When using the Download Resource task to download an Ivanti Automation Resource Package, the task fails with the following error: Failed (completely or partly) to extract 'ResourcePackage' to 'C:\<PATH>\DestinationFolder. More information |
| 90796 | Changing the Windows Defender Firewall service startup type with Ivanti Automation fails. More information |
| 90753 | The AutoCreate button for RunBook and Project parameters only works in combination with AutoLink. More information |
| 90767 |
After upgrading to Ivanti Automation 2022.3, the Perform Unattended Installation task fails to download linked resources. More information |
| 90736 |
After upgrading to Ivanti Automation 2022.3, the Perform Unattended Installation task fails if the resource is located on FileShare. More information |
|
90786 |
After upgrading to Ivanti Automation 2022.3, the Perform Unattended Installation task fails when using an Ivanti Automation Resource Package. More information |
Ivanti Automation 2022.3
What's New
Ivanti Automation tasks migrated to a newer code base
For continued maintainability of the code, the following tasks have been migrated to a newer code base:
-
Registry Settings (Apply);
-
Environment Variables (Query);
-
Unattended Installation (Perform).
Updated prerequisites for the deployment of Ivanti Automation components
Starting with Ivanti Automation 2022.3, all components require Microsoft .Net Framework 4.6.2, including the Console.
Resolved issues
The following issues were resolved in this release:
| Problem ID | Title |
| 90055 | When an automated installation using Chef tool is started, communication between the Agent and the Dispatcher fails and the resamad.xml file is not created. More information |
| 90346 | The Download Resource task fails when the destination path is set to C:\. More information |
| 90091 | Intermittently, the Project Parameter value is cleared during Job activity. More information |
| 90431 | Ivanti Automation tasks with linked Resources fail with the following error: StartIndex cannot be less than zero. More information |
| 90012 | When an Automation Agent has a Primary Team set, the Download Resource task fails with the following error: Resource could not be downloaded in cache: <Resource.wis>. Original resource name: <FileName>. More information |
|
90531 |
A module containing the task Perform File Operation: Action Edit/Create INI file and having the file path set to C:\fails with the following error: Failed to rename, file or folder "C:\placeholder.ini" does not exist. |
|
|
When a string used to filter Job History or Audit Trail entries contains a single quote character ('), the filtering returns no records. |
|
|
When the Automation Console is used to configure the maximum number of parallel jobs that an Agent can execute to 100, the agent will only execute 50 Jobs in parallel. |
|
|
When Auto-Refresh is enabled and many entries are present, deadlocks occur in the Scheduling and Activity nodes. |
|
|
When the Agent Alias feature is enabled, but no paths are configured, CheckForChanges errors are logged and no jobs are picked by the Agents. |
|
|
The Evaluator is not functional for the Parameters (Query) and Microsoft System Center Configuration Manager (Query Server) tasks. |
Ivanti Automation 2022.2.2
Resolved issues
The following issues were resolved in this release:
| Problem ID | Title |
| 90037 | The Perform Single File Operation task fails if the destination folder does not exist. More information |
| 90091 | Intermittently, the Project Parameter value is cleared during Job activity. More information |
| 90012 | When an Automation Agent has a Primary Team set, the Download Resource task fails with the following error: Resource could not be downloaded in cache: <Resource.wis>. Original resource name: <FileName>. More information |
| 90130 | The exit code in an Execute Command task is always 0. More information |
|
90271 |
The Manage Service task does not work if the service name contains a space. More information |
|
|
The Dispatcher is not updated after upgrading the Automation environment. |
|
|
An Execute Command task configured with credentials and referencing a resource file fails. |
|
|
Unicode characters are incorrectly presented in job results in the Automation Console. |
Ivanti Automation 2022.2.1
Known issues
The list below contains known issues for this release:
| Problem ID | Title |
| 90037 | The Perform Single File Operation task fails if the destination folder does not exist. More information |
| 90091 | Intermittently, the Project Parameter value is cleared during Job activity. More information |
| 90012 | When an Automation Agent has a Primary Team set, the Download Resource task fails with the following error: Resource could not be downloaded in cache: <Resource.wis>. Original resource name: <FileName>. More information |
| 90130 | The exit code in an Execute Command task is always 0. More information |
|
90271 |
The Manage Service task does not work if the service name contains a space. More information |
|
|
The Dispatcher is not updated after upgrading the Automation environment. |
|
|
An Execute Command task configured with credentials and referencing a resource file fails. |
|
|
Unicode characters are incorrectly presented in job results in the Automation Console. |
Resolved issues
The following issues were resolved in this release:
| Problem ID | Title |
| 89803 | The Manage Service Properties task fails with the following error: Invalid access to memory location. More information |
| 89821 | An Execute Command task fails when Execute command using the Windows command interpreter is unchecked. More information |
| 89818 | The variable in the Execute Command task is case sensitive. More information |
| 89819 |
The Copy - File/Folder action of a single file in the Perform File Operations task fails. More information |
| Stopping a service by using the Manage Service Properties task fails without returning an error. More information |
Ivanti Automation 2022.2
What's new
Automation tasks migrated to a newer code base
For continued maintainability of the code, the following tasks have been migrated to a newer code base:
-
Files (Perform Operations);
-
Environment Variables (Set, Delete);
-
Service Properties (Manage);
-
Resource (Download);
-
Command (Execute).
Database revision level update
The database revision level for Ivanti Automation 2022.2 has changed to 84.
Known issues
The list below contains known issues for this release:
| Problem ID | Title |
| 89803 | The Manage Service Properties task fails with the following error: Invalid access to memory location. More information |
| 89821 | An Execute Command task fails when Execute command using the Windows command interpreter is unchecked. More information |
| 89818 | The variable in the Execute Command task is case sensitive. More information |
| 89819 |
The Copy - File/Folder action of a single file in the Perform File Operations task fails. More information |
| Stopping a service by using the Manage Service Properties task fails to report the actual error message. More information |
Resolved issues
The following issues were resolved in this release:
| Problem ID | Title |
| 89428 | Automation jobs scheduled via the Dispatcher to an empty team stay in the Scheduled state indefinitely. More information |
| 88869 | Automation jobs are incorrectly processed on Agents installed on non-persisted machines. More information |
| 89331 | After upgrading to Ivanti Automation 2021.4, the Automation Console is not responding when scheduling runbooks. More information |
| 89381 | Downloading resource fails with the following error: Resource could not be downloaded in cache: <Resource.wis>. Original resource name: <FileName>. More information |
| 89376 | Automation Agents show an increase in memory usage while no jobs are being executed. More information |
| 89406 | After selecting a new Automation Module or Project in Environment Manager, the following error is shown: Unable to connect to the selected Dispatcher service. More information |
| 89113 | The operation of checking if the LanmanWorkstation service is running fails on non-English operating systems. More information |
| 88752 | When choosing the option Change settings for multiple Agents in the Automation console, the Global <value> is visible and the Team <value> is not available. More information |
| 89484 | When selecting the Variables node in the Ivanti Automation Console, the following error is shown: clsVariable.Load_Internal: 13 - Type mismatch. More information |
| 89216 | When a condition checking a parameter has to check a value containing 5 or more digits, the following error appears when opening the task and condition: Error in sharedEncryption.fstrLegecyDecrypt: 5 - Invalid procedure call or argument. More information |
|
The license overview now displays license points correctly when old and new license types are combined. More information |
Ivanti Automation 2022.1
What's new
New team membership rules
Automatically add Agents to Teams with new file/folder and registry key detection rules. More information.
Service triggers
Start and stop Windows services based on trigger events. More information.
Interactive job execution
Use this task to create interactive multipart jobs, where the user sees a Windows notification and can choose to continue, skip, or abort job actions. More information.
New Automation component deployment logs
When deploying Ivanti Automation components, the Job History has a new Log tab that displays the MSI installation log. This can help troubleshoot deployment issues. In Job History > Tasks, double-click the task you want and then click the Log tab.
The database revision level remains at 83
There was no database revision level update for this release.
Resolved issues
The following issues were resolved in this release:
| Problem ID | Title |
| 87369 |
Agents will not pick up jobs after recreating a global variable that is used on a Teams or Agents level. More information |
| 87675 |
Scheduled Jobs based on a CRON expression return the following error: Please enter a valid cron expression. More information |
| 87561 |
Opening a scheduled job results in the error: Error in clsParamters.Load: 452 This key is already associated with an element of this collection. More information |
| 87739 |
The drop-down list for the RunbookWho parameter in a runbook contains an additional entry. More information |
| 88147 |
Using functions in an Automation task results in the error that the task contains illegal characters. More information |
| 87960 |
Error in modWMC.MoveListItemTop:13 Type mismatch appears when changing the order of a Runbook job. More information |
| 88048 |
The Date/Time information in some of the columns of the Automation Console is presented with an incorrect order of the day and month. More information |
| 88229 |
World writable permissions on the resamad.log are marked as violations by third party security scanners. More information |
| 88250 |
Windows 10 21H2 - v2009 (19044.1348) is not detected when using as condition OS Windows 10. More information |
| 88292 |
Using PowerCLI to manage a VMWare vCenter environment via Ivanti Automation results in the error: Could not load file or assembly 'Newtonsoft.Json'. More information |
| 88341 | Could not load file or assembly server error on opening Ivanti Automation Management Portal. More information |
| 87107 |
Error during the creation of a building block: ERROR in modBuildingBlocks.FillCustomSettings: 91 - Object variable or With block variable not set. More information |
|
The Automation Console connection registry values are changed when using Windows Authentication even though the user was not prompted to save them. More information |
|
|
No error is presented when Windows Authentication is used and the impersonation is done using the logged on user instead of configured user. More information |
|
|
The Automation Agent fails to auto update when the download of the new msi file takes too long. More information |