Skip to main content
Skip table of contents

Version 2023.02.1.231

This version was released on 


Announcements

Bug Fixes

  • Queries for collecting Ivanti incidents whose “Correlation ID” is not empty are sent with an incorrect filter.

Platform Features and Improvements

  • Extended the Ivanti integration to support additional “Journal” fields.

  • Implemented the ability to provide a hotfix for a specific connected system.

  • Implemented the ability to create sub-records in Jira (sub-task, sub-bug, etc.).

  • Added a server-side security validation for the Configurator endpoints.

Additional Content

  • N/A


Important Notes

Upgrading to the 2023.02.1.231 release requires clean-up and redeployment of the ZigiOps service.

  1. Stop the ZigiOps service or process.

  2. Back up the existing ZigiOps installation folder to another location.

  3. Remove the ZigiOps service.

    • Windows:

      • Execute the <ZigiOps>\service\uninstall_service.bat file to uninstall the ZigiOps service.

      • Delete all files from the <ZigiOps>\service\ folder.

    • Linux:

      • Delete the /etc/systemd/system/zigiwave.service file.

      • Delete the <ZigiOps>/zigiops_start.sh file.

  4. Install the ZigiOps 2023.01.191 release in the existing ZigiOps installation folder.

    • Check the OS Service option during the installation, depending on your preferences.

  5. The service is automatically started when the installation is complete.

Upgrading from the 2021.10.145 release (or earlier) may require resetting the ZigiOps web console certificate truststore credentials by following the steps below; otherwise, ZigiOps would start, but the web console wouldn't be accessible.

  1. Stop the ZigiOps service or process.

  2. Remove the following entries (lines) from <ZigiOps>\conf\config.properties file and save the changes afterward:

    • key-password

    • key-manager-pass

  3. Start the ZigiOps service or process.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.