Release Date: December 5th, 2019  

Installation Arguments

• Release Build RPM - 1543
• JetPatch Server - 3.9.6.95
• Connector - 3.9.4.226

Enhancements 

Longer Script Timeout Execution (requires connector 226) 

It is possible to configure both internal (built-in) and external (uploaded by user) scripts a timeout (a specified period of time) until JetPatch terminates the task (5-hour maximum).  See article for configuration details.

Refactor Compliance Calculation - Improves performance and internal calculations 

Server jobs for calculating compliance were re-designed and re-tested to improve interaction with Database and UI. Resulting in Data memory and performance improvements. 

When looking at a Remediation plans View or Compliance report information, the calculations will be done faster and give a more accurate picture.        

Remediation plan compliance report, new Status under Non-compliant Devices “Maintenance Window Expired” 

This status will appear when one of the servers in the Remediation plan is connected to a Maintenance window that has expired. In such cases, the server is exempt from the remediation plan.

For more information, please go to JetPatch Knowledge center: Remediation Plan Compliance Report

New exit code: code 342

See Exit Codes article for more information. 

Bug Fixes

Patch Management Bug Fixes

• Fixed: Resolved several issues causing activities failures, including stabilizing workflow mechanisms
• Fixed: Active Directory Discovery Source issue deploying connector on CentOS and RHEL
• Fixed: CentOS wrong calculation of needed patches for server
• Fixed: Filter by Smart Group not equal to results in Platform Configuration
• Fixed: Custom Exit Code not showing as successful

Agent Management Bug Fixes

• Fixed: Azure discovery source failed to retrieve data when the virtual machine and the assigned NIC were in different resource groups 
• Fixed: Policies Running in a Loop -  An agent was being installed by a lower priority inclusion rule and then uninstalled by a higher priority ban rule. This issue occurred because the permission for 'Smart group administration' was not being implemented on ban rules.
• Fixed: Console slowing down -  When an automation script was executed on over 10K servers console activity slowed down 
• Fixed: Policy Manager not running remediations - An increase in CPU load for the DB was causing the policy manager to almost stop activity 
• Fixed: DB Activities clean-up - Activities log showing old activities (more than a year) - Activities log is back to standard behavior showing up to 10K activities 

Known Issues

Patch Manager Known Issues

• Unable to edit or delete workflows, even when there are no active remediation plans. 
• When there are two confiting active remediation plans, the first installing a patch and the second removing the same patch from a computer group. JetPatch will alter the install Action and change it to remove in the first remediation plan, this will affect any other computer groups on this plan and remove the patch from them as well. The same behavior will apply when the Actions are vice versa. 
• A remediation plan with patches for Window applied on Linux server and vice versa will continuously remain in Waiting For Execution status under the completed column and will not reach completion 
• Declined patches are calculated as part of the remediation plans' compliance status and will prevent a remediation plan from reaching 100% compliance. This will be reflected in the remediation plan compliance report and in Management Table under the “patching status” * 
• When a Patch Action (install/remove) has failed on a server JetPatch will continuously show the failed status until the required action is successfully completed. The Failed status will appear in any compliance report with the same patch and server configuration. For Example: If a patch has failed on a server and the same patch is run on the same server in a new remediation plan the corresponding compliance report will show a Failed status even if the new plan has not yet attempted any action on the patch.  

• Emergency Remediation Plan displaying inconsistent information in Remediation plan board
• In some cases, the information displayed on an Emergency Remediation Plan may contain the information related to the original maintenance windows (related to the servers on the plan) and not the emergency maintenance window. This information will appear in three places only: Devices Status, Actions Status, Remediation plan status. All the other related information, the column the plan is in, related compliance report or the view tab, is correct.
  

• Patch Catalog showing Deleted & Canceled remediation plans 
• 'Deleted' & 'Canceled' Remediation plans continue to appear in the patch catalog under the Plan ID
  

• Scripts can not be disabled
• When clicking on the disabled button, the scripts are reverted back to enabled
  

• Maintenance Schedule: ‘Repeat Until' field
• When adding a Scheduled Entry and choosing a 'repeat type' Does Not Repeat, the 'Repeat Until' field will still appear but any entry will not affect the Maintenance schedule
  

• Scripts table Total Task Link 
  • When clicking  'Total Task' number the Scripts Table the link doesn't work and will not display the tasks that are connected to each script
    

Agent Management Known Issues  

• Native agents have Null ID for certain properties 
• Networker Agent exit process event is not listed in 'Logs&Alerts'. In cases were the Networker process is 'killed' On Ubuntu servers the event is not registered in 'Logs and Alerts'.