Articles in this section

See more

JetPatch Release Notes 4.2.3

If upgrading from 4.1.2 or before, please see the following notes,

  • Get an export of Endpoints -> Management -> Endpoints Management Report, this will ensure you have a all endpoint names and their respective endpoint groups, in case auto-migration fails.
  • Disable predictive analytics in intigua.properties
    • pg.prediction.data-collection.enabled=false
  • Snapshot your environment before upgrading, because you will not be able to rollback to previous versions. If you need to use the snapshot, we recommend new VM, if existing VM does not work.
  • If you have any windows in your environment,
      • Make sure all windows servers are using at least connector 4.1.2.231 or above.
      • Verify IPV6 is disabled on all WSUS servers.
      • Ensure no endpoints are using Client Side Targeting mode, because it is not supported in this version.  Note: Client side targeting is not necessary with the move to smart groups and the WSUS group management mechanism enhancement (read 4.2.2 release notes for more information)
      • If using WSUS Replicas
        • Make sure all replicas are in a connected state, if even one is not connected, partial results will occur
        • Make sure the WSUS Replicas are syncing 24 times a day (see article), the endpoints reporting to replicas may be stuck in "Synchronizing" for several hours.
        • Make sure the WSUS Replicas are pointing to the Primary (see article), otherwise the WSUS Replicas will be stuck in "Synchronizing or Updating" and no windows patching will work. 
          • Note: this can easily be confirmed using the windows endpoint readiness script
        • Verify that you do not have any downstream servers set as autonomous mode.
      • If you receive a 404 error after upgrade, then review vmanage.log for information as something is preventing the application from starting properly.
        • Note: if upgrading from 4.1.2, there may be a merge conflict due to major tomcat upgrade, resulting in the intigua.properties files not copying from old tomcat directory to new default.  Please copy to default, provide permission to tomcat:tomcat, restart tomcat and try again. 
      • Once you are able to reach the login page, please allow some time after upgrade before using platform (initial migration will spike performance monitoring).
        • Note: if you have a lot of windows servers and replicas, it may take a few hours to sync.

      • If there are several endpoints in a "updating endpoint" or "synchronizing endpoint", then append the following to the JetPatch URL

        • vmanage-server/rest/experimental/wsus-activities/run-sync

        • Wait at least 30 minutes after running that command.  In the meantime, please verify all endpoints are passing endpoint readiness as per the patching checklist.
        • If there is still a problem, do the following steps
          1. Remove WSUS discovery source
          2. Remove WSUS connector from servers tab
          3. Remove WSUS entry from servers tab
          4. Re-add WSUS server as standalone
          5. Re-deploy WSUS connector (latest version)
          6. Re-add WSUS discovery soruce

Version: 4.2.3 + Connector 4.2.3.24 (Sep 8, 2022)

  • 4.2.3 UR1 (build 84) - Oct 13, 2022
  • 4.2.3 UR2 (build 96) + Connector 4.2.3.22 - Nov 17, 2022
  • 4.2.3 UR3 (build 101) + Connector 4.2.3.23 - Nov 28, 2022
  • 4.2.3 UR4 (build 108) + Connector 4.2.3.25 - Dec 23, 2022
  • 4.2.3 UR5 (build 114) + Connector 4.2.3.28 - Jan 14, 2023
  • 4.2.3 UR6 (build 122) - Jan 31, 2023
  • 4.2.3 UR7 (build 131) - Mar 1, 2023
  • 4.2.3 UR8 (build 134) - Mar 30, 2023
  • 4.2.3 UR9 (build 136) - Apr 24, 2023

What's New

UI Improvements: Various improvements have been made to the UI to not only improve the visual aspect of JetPatch but also many workflow improvements.

Before 4.2.3

before.png

 

With 4.2.3

after.png

  • As you can see, there has been changes to the color palette, as well as various changes to icons and pop up behavior. 
  • New Default Page: Endpoints > Management 
  • Knowledge Center Quick Access Links: Each page in JetPatch now has a quick link (in the form of a question mark) that will send the user directly to the corresponding Knowledge Center article

Quick_Link.PNG

  • Remediation Plan Board Improvements

    • New Bulk Actions

      • The "Remediation Plan" page allows for 5 new bulk actions:
                                                  remediation_plan_action.PNG 
      • Cancel All Completed Plans - This option will cancel all completed and archived remediation plans, changing the status from "Done" to "Cancelled," deactivating the remediation plan. 
      • Archive All Canceled Plans - This option will archive all cancelled remediation plans
      • Delete All Archived Plans - This option deletes all remediation plans that have been archived (either cancelled or completed)
      • Delete All New Plans - This option will delete all remediation plans that are in a "New" state (not activated)
      • Clean Up The Board - This option will delete all completed and archived plans, whether done or cancelled by the user

    • Additional Remediation Plan Board Improvements

      • Archiving a remediation plan will now automatically cancel it.  Status will be "Cancelled by user"
      • A remediation plan will now automatically cancel if current time > SLA End Date
        • By default SLA End Date is 30 days after activation.  This is configurable (see article)
        • Status will be “Cancelled by policy”
    • Please read the Remediation Plans Board article for more information
  • Service Now Template Integration: With enhancements to the out-of-the box ServiceNow integration, users are able to 
    • Ability to create a change request ticket with a standard template
    • Set ‘start_date’ and ‘end_date’ based on MW
    • Populate the ‘Affected CI’ list
      • Able to replace the table to be queried for Configuration Item (computer) match (Added In: 4.2.3 UR2)
      • Able to add a limit query according to ServiceNow Table API rules (Added In: 4.2.3 UR2)

      • Two more configuration properties were introduced to configure cmdb_ci property name matching (Both Added In: 4.2.3 UR3)

        • The new property itsm.cmdb_ci.use-full-name (default false) defines whether the cmdb_ci property will hold the full name or just the hostname part. By default only the host part will be sent. Setting the value to true defines sending a full name.

        • For the case when ServiceNow can hold both full names and hostnames and the definition of itsm.cmdb_ci.use-full-name does not help, the ServiceNow matching by hostname was introduced. For this a new configuration property was added: serviceNow.cmdb-ci.match-with-query (default false).  

    • Ticket close call in ServiceNow can be conditioned by a property serviceNow.ticket.close.on-state. If not set (default) the ticket close and close retry will be not condition. (Added In: 4.2.3 UR3)

servicenow-partduex.png

Continuous Improvements

  • Workflows can now be added or modified during remediation plan creation

mceclip0.png

  • Endpoints > Management now has a column for IP address

mceclip1.png

  • System created maintenance schedule set for "All Time" to allow 24/7 ad-hoc patching 

mceclip1.png

  • Agent Management Support added for Ubuntu 22.04 Jammy Jellyfish
  • Can now trigger WSUS full scan with API call.
  • When manually added a new endpoint to JetPatch, the following EOL operating systems are hidden:
    • RHEL 5
    • CentOS 5
    • CentOS 6
    • Ubuntu 14
  • Removed WSUS server from Endpoint Readiness Calculation (Changed In: 4.2.3 UR1)
  • All Agents' tasks (eg: deploying Evolven) timeout is now 40 minutes by default (Changed In: 4.2.3 UR2, Connector 4.2.3.22)
  • Support for vCenter7 as a discovery source (Added In: 4.2.3 UR4)
  • Added a help icon to the exemption column on all relevant pages that goes to the exemption KC article (Added In: 4.2.3 UR4)
  • vLink uninstall and upgrade improvement (Added In: 4.2.3 UR5, Connector 4.2.3.28)
  • vCenter 7 security improvements (Added In: 4.2.3 UR6)
    mceclip0.png
  • Added additional connection logging (Added In: 4.2.3 UR8)
  • Improved memory cache to improve connection stability (Added In: 4.2.3 UR8)
  • Improved WSUS Replica Sync (Added In: 4.2.3 UR8)
  • WSUS patch discovery enhancement (Added In: 4.2.3 UR9)

Bug Fixes

  • Slow loading of Agents & Tools > Tools Catalog and Agents & Tools > Exceptions page: Resolved issue where it took upwards to 20 seconds for both the Tools Catalog and Exceptions pages to load
  • RHEL 7 and 8 collect endpoint exit code 340: Resolved issue of RHEL7 and RHEL8 giving a "340" exit code when running the "Collect Endpoint Updates" system task
  • Failed to configure mail SMTP: when the system fails to configure the SMTP server
  • System default maintenance schedule "All Time" not created but maintenance entry present when creating new schedule (Fixed In: 4.2.3 UR1)
  • WSUS Connector Communication Issue (Fixed In: 4.2.3 UR2, Connector 4.2.3.22)
  • Windows Replica Group Sync
    • Some endpoints stuck on Synchronizing Endpoint (Fixed In: 4.2.3 UR3)
    • Some endpoints stuck on Updating Endpoint (Fixed In: 4.2.3 UR4)
  • Unable to patch WSUS server with built-in WSUS Smart Group (Fixed In: 4.2.3 UR2)
  • Unable to patch some OEL8 machines (Fixed In: 4.2.3 UR3, connector 4.2.3.23)
  • Agents & Tools > Tools Catalog - Displaying only up to 100 results instead of more (Fixed In: 4.2.3 UR3)
  • Unable to remove WSUS Discovery Source (Fixed In: 4.2.3 UR4)
  • Unable to filter on blank tags in Platform Configuration(Fixed In: 4.2.3 UR4)

  • Some connector communication issues (Fixed In: 4.2.3 UR4, connector 4.2.3.25)

  • Fixed an error with the Solaris installation script resulting in an error code 342 (Fixed In: 4.2.3 UR5)
  • Fixed an error where the failed patches list displayed incorrect results (Fixed In: 4.2.3 UR5)
  • Unable to bulk un-assign tags in the GWT (Fixed In: 4.2.3 UR5)
  • Removal of orphaned records for WSUS group activities (Fixed In: 4.2.3 UR5)
  • Fixed total endpoint readiness calculation bug introduced in UR1 (Fixed In: 4.2.3 UR5)
  • vLink file permission default values are incorrect (Fixed In: 4.2.3 UR5, Connector 28)
  • WSUS task "Get groups and computers in group" shows no patching status and an X in WUA communication (Fixed In: 4.2.3 UR6)
  • Removed vLink ban policy (Fixed In: 4.2.3 UR6)
  • Re-adding WSUS discovery source does not pull tags from WSUS on pre-existing DBs (Fixed In: 4.2.3 UR6)
  • Removing WSUS discovery source removes tags assigned to Windows endpoints (Fixed In: 4.2.3 UR6)
  • Fixed a "WSUS get updates" script parsing issue (Fixed In: 4.2.3 UR7)
  • Fixed a "Collect Endpoint Updates" script parsing issue for Oracle Linux 8.x endpoints. (Fixed In: 4.2.3 UR7)

Known Issues

New in 4.2.3

  • Unable to patch WSUS Server with JetPatch if it is apart of multiple smart groups (Fix: 4.2.6)
  • Patching WSUS Replica Servers with JetPatch - Must set WUA of Replica to Primary, see article (Fix: 4.2.6)
  • Patches Catalogs - No Indication for broken saved filter Based on Smart Groups (Fix: 4.2.4)
  • Predictive Patching - Smart Group statistics can show the same group twice (Fix: 4.2.4 UR3)
  • In Endpoints > Activities, "Succeeded" in the Status column is cut off at the final letter (Fix: 4.2.4)
  • Predictive Analytics disabled only on new installed (Fix: 4.2.4)

From 4.2.2

  • WSUS servers operating in Client Side Targeting mode are not supported in this version.  Client side targeting is not necessary with the move to smart groups and the WSUS group management mechanism enhancement. (4.3)
  • Dashboard->Operating System filter drop down list is not aligned with user server scope (Fix: 4.3)
  • Tasks - User Scheduled Queued Tasks don't persist after tomcat restart (Fix: 4.2.4)

 

Related articles

Comments

0 comments

Please sign in to leave a comment.