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:
Ivanti Automation Agent+ still uses multicast to connect to Automation Dispatcher
After configuring Ivanti Automation Master Caching, dispatcher port 3163 is still in use
Sorting jobs on the columns Duration or Start (local) does not sort the jobs correctly in the Ivanti Automation Console
Searching in Ivanti Automation for Modules, Projects or Run Books will show incorrect results
The Automation agent.exe process is consuming a high amount of memory
Scheduling a job to an Agent results in executing a job scheduled on boot for the same Agent
Aborting a job in the Automation Management Portal results in the error "Object reference not set to an instance of an object"
Query Database statement with REPLACE function to replace a single quote on Oracle does not work
Ivanti Automation task is executed, but the status of the task is reported as Skipped
The Delete Ivanti Automation Results task is finished although the database query is still running
Unable to use an Ivanti Automation variable or parameter in Account expiration Active Directory Property
Not all parameters are shown when using a WSDL file in the Invoke Web Service Module
When using a Powershell script as an Automation resource, the variables in the Powershell script may not be updated when ran
Dropped support for Oracle and MySQL database types
Customers that use the Oracle or MySQL database types will not be able to upgrade their environment. These database types are no longer supported.
New .NET Framework requirement for Dispatcher
.NET Framework 4.6.1 is required on Dispatcher machines to be able to install a new Dispatcher or update an existing Dispatcher.
Data compression for active jobs and job history
In large environments, with complex and large jobs, Ivanti Automation can take a lot of disk space on the SQL server. In 2020.1, data compression was implemented for active jobs and jobs history. The column imgTasks and imgOrgTasks now contain compressed data in tblJobs, tblMasterJob (tables used for active jobs), respectively tblJobsHistory and tblMasterJobHistory (tables used for job history).
Compression ratio of ~ 90% were measured during tests.
Please be aware that new jobs or job history generated using 2020.1 will not be readable if a downgrade to a lower version is executed. Using 2020.1, compressed and uncompressed data can be processed and presented to the user in Console and Management Portal.
Added support for a new licensing method (prototype)
In the Setup > Licensing we have introduced a new tab, Ivanti License Server, where the user can configure the settings for a new licensing method. This feature is a prototype and should not be configured for the moment.
New Linux agents were added
There's now Linux agent support for SUSE v15.1 (ppc64le), CentOS v7 and v8, RedHat v8 (x86, x86/64, and ppc64le)
Extended the “View trace content in Console” functionality
Traces for the Unix/Linux agent can be enabled in the Console now. More information about the files is presented in the Console. The trace content is transferred and saved in the database server in a compressed format. More information about the trace is presented, like trace size and date modified. Also, in the Agents view in Topology, a column as added to signal if tracing is enabled on an agent.
Search by GUID in the Library view
Users can search for a Module, Project, Runbook or Resource using its GUID in the search screen.
Custom job invoker in Dispatcher webAPI
A new filed was added to the POST Jobs method - JobInvoker. Users can fill in a custom value that will be presented in the job results view in the Console, under the Who Invoked column. If no data is passed in this field, the user that authenticated the API call will be reported in Console.
Also, for jobs scheduled from Console, the Who Invoked field will report the actual user that scheduled the job. Until now the only information available was in the Job Invoker column that had a generic value of "User" when a user was scheduling a job from the Console.
Tree-view like global variables menu
If the number of global variables is greater then 20, the context menu in various places (like tasks) will no longer present the list of global variables. Instead, you can click the See more... context menu option to show a tree-view list of global variables.
Search can be done in the new global variables screen just by start typing a variable name.
Category name behaves like a folder that can be closed or expanded with a double-click.
Evaluator for Local User task
The evaluator tab was introduced for the "Local User (Query)" task. We are planning to introduce the evaluator tab to other tasks that query for data, like Printers and Registry Settings.
Extend Firewall task to accept port ranges
The Firewall task can make use of port ranges. Currently we create a new configuration entry in the Windows Firewall for each port that is part of the port range configuration. We are working in the future releases to be able to create a single Windows Firewall entry for the configured list of port and port ranges.
Lowered the default value for PowerShell output width
The PowerShell task is using a new default value for output width, 256 instead of 16386 as it used to be in previous releases. Using such a large value can generate issues if large amounts of data are saved in an output parameter.
Enhanced the WebService Invoke task
Authentication type can now be configured. The supported types are: Basic Authentication, No Authentication, Negotiate Authorization, and NTLM User Authentication. In older versions, only Basic Authentication, if security context was used, and No Authentication, if no security context was used, were the supported authentication types.
Invoke Web Service - Allow dynamic Host name
In this version of Ivanti Automation, we have introduced the possibility to make use of WSDL files that reference the web service host using a global variable. This allows for flexibility in using the configuration based on this task in other environments that make use of the same web service. Just make sure the other environment has the same Ivanti Automation global variable, having the value of another web service instance host. The Ivanti Automation Console and Ivanti Automation Agent+ will make use of the variable value while using the Test button or running the job.
Improved search for agents
In 2019.3, a new column was added in Console in the Topology view, Last Contacted Dispatcher. When a search was performed, the new column was automatically take into account, but if an agent was also installed in the dispatcher machine, the search results would return all the agents that are connected to that Dispatcher, which is not ideal if you are looking for the agent only.
In this version we have introduced a new checkbox, Include “Last Contacted Dispatcher”, by default unchecked, to have the search functionality as it was before 2019.3. If you want to see the agents connected to that Dispatcher, the new checkbox should be checked.
Various database improvements
New indexes were created, and some queries were optimized to improve the Console interaction with the database server. Related to this, we have introduced some tweaks/improvements in the Console also.
Searching for agents is limited to 500 records. A pop-up will be presented to the user, informing that only the first 500 records will be displayed, to avoid DB hammering, and suggest a filtered search that would generate less then 500 agents.
New global settings are available, Auto load large data and Auto update Agent. For more information, see the documentation for these items in Other settings.
Ivanti Automation Console has no option for force protocol encryption with certificate validation
Enhancement: The information about the Automation database size is better specified
Installing a Dispatcher on a machine fails from a Console with Protocol Encryption enabled
Removing Job History with the build-in task Delete Automation Jobs will not delete jobs scheduled via an external tool
Running a PowerShell command via Ivanti Automation to get the windows build numbers returns wrong information
Passwords are visible during scheduling when used in the Execute Command line
Unix/Linux Automation Agents goes offline in the Ivanti Automation Console
Ivanti Automation Linux Agent 10.9.* uses sudo to execute shell /command scripts
Already finished Job stays active in the Automation Console for several minutes
The Query Database Statement task is not executed when the password is filled in by using a Parameter or Variable
Download Unix/Linux resource fails while downloading a large resource to an Ivanti Automation 2019 or higher Unix/Linux Agent
The Automation Console can't be started if it's installed via the Deploy Automation Component task
Resizing the Ivanti Automation console changes the number of active agents
Ivanti Automation Linux agent appears offline when downloading a large resource
Sorting the scheduled jobs on Tags in the Management Portal results in the error: 'Object reference not set to an instance of an object'
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