Version: 4.2.6.123 + Connector 4.2.6.21 (Feb 25th, 2024)
- 4.2.6 UR1 (build 132) - Mar 5, 2024
- 4.2.6 UR2 (build 142) + Connector 4.2.6.22 - Mar 24, 2024
- 4.2.6 UR3 (build 147) + Connecter 4.2.6.24 - Apr 10, 2024
- 4.2.6 UR4 (build 151) + Connecter 4.2.6.25 - Apr 24, 2024
- 4.2.6 UR5 (build 155) - May 7, 2024
- 4.2.6 UR6 (build 156) + Connector 4.2.6.26 - May 19, 2024
- 4.2.6 UR7 (build 158) - May 30, 2024
- 4.2.6 UR8 (build 161) - June 17, 2024
- 4.2.6 UR9 (build 170) - July 3, 2024
- 4.2.6 UR10 (build 174) - July 23, 2024
- 4.2.6 UR11 (build 179) - August 1, 2024
- 4.2.6 UR12 (build 181) + Connecter 4.2.6.27 - August 14, 2024
- 4.2.6 UR13 (build 183) - August 24, 2024
- 4.2.6 UR14 (build 187) - August 27 , 2024
- 4.2.6 UR15 (build 188) - September 17, 2024
- 4.2.6 UR16 (build 189) - September 25, 2024
- 4.2.6 UR17 (build 190) - November 14, 2024
- 4.2.6 UR18 (build 191) - November 19, 2024
Latest UR available on our 4.2.6 Live Repo
Connector Note
4.2.6.X Connector now supports TLS 1.3. As a result, EL6 Linux is not supported (as EL6 does not have the library for TLS 1.3). Thus, please keep using connector 4.2.5.X or earlier for EL6 (eg: RHEL 6.X, OL 6.X, CentOS 6.X)
Pre-Requisite: Java Migration - Java 8 to Java 11
JAVA version must be upgraded from Java 8 to Java 11 for JetPatch on supported Enterprise Linux systems. If you are already running Java 11, you can skip this step. Check with the following command:
java -version
After completing the specified steps, your JetPatch application should be fully functional on Java 11, ensuring compatibility and security for your Linux host system. Please always verify app functionality after upgrading to ensure no issues.
For more information please visit: Transitioning from Java 8 to Java 11
Extended Platforms Support
Note: The new OS requires a 4.2.6 connector
Rocky Linux
-
Support for Patches and Agents
-
Rocky Linux Enterprise Server 8.X
-
Rocky Linux Enterprise Server 9.X
-
Oracle Linux 9.X
-
Support for Patches and Agents
For more information on supported Operating Systems and patching downloading techniques please visit JetPatch Supported Platforms
Remediation Plan Improvements
Sequence Patching
Purpose: To elevate patch management strategies, Sequence Patching is introduced, aiming to address the complexity of effective enterprise patching. This innovative feature is designed to manage various patching dependencies systematically, including but not limited to dependent group patching across different stages (QA, Staging, Pre-Prod, Prod), application layer patching (DB, Backend, Frontend), cluster patching, and high-availability (H/A) server patching. By considering different thresholds and "green lights" for transitioning to subsequent phases, Sequence Patching embodies a holistic approach to managing patch workflows, ensuring a seamless and risk-managed deployment across environments.
Can be found under Patches > Sequence Patching
Key Features:
- Dependency Management: Facilitates the creation of dependencies between Remediation Plans, enabling orderly and risk-managed patch deployments.
- Automated Sequencing: Streamlines the patching process by automating sequences, reducing manual oversight and accelerating patch deployment.
- Dynamic Alerting and Success Criteria: Offers configurable success criteria and alerting mechanisms to ensure patches meet predefined standards before progressing.
- Comprehensive Support: Extends support across various patching scenarios, including high-availability servers, clusters, application layers, and prioritized patching based on criticality (e.g., security, bug fixes).
Enhanced User Experience:
- Intuitive Creation and Management: Provides a dedicated interface for the creation and management of Sequence Patching plans, enhancing user interaction and operational efficiency.
- Simplified Plan Creation: This enables users to easily define and organize patch sequences, set activation criteria, and select approval methods for each step in the patching sequence.
Operational Benefits:
- Efficient Dashboard Navigation: Incorporates new filters for swift identification and management of sequence patching plans directly from the dashboard.
- ITSM Integration: Ensures seamless integration with ITSM for enhanced ticketing processes, providing comprehensive visibility into patch management activities.
- Adaptable Approval Processes: Offers flexibility in selecting manual or automatic approval methods for each sequence step, accommodating various operational workflows
For detailed guidance and further information, visit our Sequence Patching documentation.
Remediation Plans Ticket - New Statuses & Activate Icon
Remediation Plan Statuses
To maintain uniformity and logic between the Remediation Plans statuses and Their location in the Dashboard,
- ‘Pending Activation’ Changed to - Activation Required
- ‘Waiting for Execution’ Changed to - Pending Execution
- ‘Pending Configuration’ charged to - Missing Configuration
- ‘Pending cancel’ changed to - Cancellation
- 'Pending Approval" changed to - Pending ITSM Approval
- 'Rejected by User' changed to - Rejected by ITSM
Activate Icon (New)
User will be able to Activate New RPs in Status - Pending Activation, Directly from RP Ticket.
When the user presses on this Icon a warning message will be displayed
Are you sure you want to activate the remediation plan? (YES / NO)
-
YES - will activate the current RP & RP Will be moved to the Pending Column
-
NO - Will cancel the activation process & RP will stay in the current Status ‘Pending Activation
Patches Catalog - Make patch titles clickable and redirect to OS vendor Info
Patch titles are clickable and redirect to User to the Operating System vendor for more information
UI/UX Improvements
Merging Screens - System Resources in One Screen
Smart Groups & Maintenance Schedule will be fully Managed (CRUD & Assign) With their own Screen
Each Screen will Have 2 Tabs
- Management - Will be Equal to Screen exist on ‘System’ Section
- Assignment - Will be Equal to Screen exist on ‘Endpoint’ Section
System - Smart Groups
System - Maintenance Schedule
Endpoint > Management > 'ACTION' Button - Add Assignments Options
When the user Select Option 'Assignments” he will have the option to Assign Selected Endpoint to Relevant Resources :
- Assign Endpoints to MW
- Assign Endpoints to Smart Groups
When the User Select several Applicable Endpoints & Select the Sub Option to ‘Assign to Maintenance' / 'Assign to Smart Group' the system will act the same as on the Dedicated Screens & the same Popup window will be displayed with ALL the same UI and functionality
Smart Groups - New Statuses & Endpoint Details
Status ‘READY’ for Smart Groups - Updates
Change Smart Groups Status - ‘READY’
- Change the Status ‘Ready’ to ‘Created’
- Display tooltip on Mouse Hover: This Smart Group was Created On JetPatch Manager, also on WSUS & Replicas (If Needed)
Change Current Filler - Status
Change Filter Title ‘Status’ to ‘Group Status’
Add New Filter - Endpoint Statuses
A dropdown list of all available Statuses (Multi-Select)
- Assigned - It will filter the table & display Smartgroups that Include Endpoints in Statuses ‘- Assigned’
- Failed - It will filter the table & display Smartgroups that Include Endpoints in Statuses ‘- Failed’
- Updating - It will filter the table & display Smartgroups that Include Endpoints in Statuses ‘- Updating’
- Table results will be filtered according to selected values (multi-select)
New Table Column - Endpoint Statuses
The new Column will Have 3 Endpoint Statuses Details :
- Assigned - Summerized the Group Endpoints in statuses ‘Assigned’
- Failed - Summerized the Group Endpoints in statuses ‘Failed’
- Updating - Summerized the Group Endpoints in statuses ‘Updating’
Click on the Status Number will Navigate the User to Endpoint > Groups Screens filtered by the relevant ‘Smart Group’ & ‘Endpoint Status'
Endpoint > Activities - Add a 'Rerun' Button
Users will be able to rerun an activity that ended either successfully or unsuccessfully.
All This without the need to do it with a large number of clicks and switch to another screen
When the User Press on the ‘Retry’ Button the Specific Activity will be re-run The same Task will be Re-Run Immediately (on the relevant Server / Endpoint) in this way.
Additional Enhancements
- TLS 1.3 support for Windows and Linux endpoints
-
Enable / Disable Users Column (Platform Configuration > Users) is now added for AzureAD groups (the previous version was just for local users, AD users, and AD groups)
- Replace 'Policy Manager' User Title by - JetPatch System
- System > Scripts > Built-In Scripts - Disable option to Change
- RP wizard > Create Cycle - Changes on Non-Applicable Smart Groups Details
- Auto RP - Change Icon
- Unrecognized Operating Systems will be displayed as 'Unidentified'
- Table - Add Column Title "Actions”
- RP Wizard > Cycle > Patch Breakdown - Change the title 'Missing' to 'Not Installed'
- UI / UX - Operating System Families are supposed to be displayed as - All [OS_Name]
- WSUS Server will be displayed with a Warning Icon 'W' - When Assigned to Multiple SGs (Unable to Patch)
- System > Smart Group - Add New CIDR Filter (IP Filtering)
- Patches > Remediation Plans - Changed Pending Status of 'Sent for approval' to 'Sent for ITSM approval' (Added In: UR1)
- Aggregated Permissions and Domain Group Handling (Added In UR1)
- Endpoints > Activities > Actions > View Details - "task was launched date" now formatted as an alphanumeric date (Added In UR3)
- Endpoint > Management - Improved performance of all CSV reports (Added in UR3)
- Upgraded spring core (Added in UR3)
- Improved connectors status and error display information (Added in UR3)
Bug Fixes
- Patches > Patches Catalog - Fixed CVE filtering issue (Fixed In: UR1)
- AD Enable / Disable Domain user issue (Fixed In: UR1)
- Azure DS issue (Fixed In UR1)
- System > Maintenance - From date will now be shown in the maintenance schedule's timezone. Previously, it was shown in the user's local timezone, causing discrepancies with repeat windows based on the selected "From" date. (fixed in UR2)
- Patches > Sequence Patching > added cancel button for RPs in 'Sequence Manual Approval' (Fixed In UR2)
- Endpoints > Readiness > Settings > Configure Repositories > Autocomplete - Fixed issue with Windows (Fixed In: UR3)
- Fixed issue with Standalone Server API POST request (Fixed in UR3)
- Fixed an agent management issue affecting AWS EC2 RedHat instances that were upgraded with the in-place Leapp upgrade method (Fixed in UR3)
- Patches > Remediation Plan >Actions > Cleanup Board fix for error received (Fixed in UR4)
- Service Now > Maintenance Windows - fixed issue with Maintenance Schedule import (Fixed in UR4)
- Connectors - Temporarily disabled TLS1.3 protocol support to fix the virtualization of Windows agents issue (only affecting agent management) (Fixed in UR3)
- Platform Configuration > Servers > Fixed CSV report for unmanaged endpoints (Fixed in UR5)
- Platform Configuration > Servers > Unable to remove standalone server from inventory (Fixed in UR6)
- Platform Configuration > Settings > Email ->Changes were not getting reflected in the screen (Fixed in UR7)
- Identify and resolve the permission issues preventing the Solaris connector from starting (Fixed in UR7)
- Downloading of Smart groups under System > Smart Groups > Smart Groups - Management (Fixed in UR7)
- When a New RP is created and saved the status of the RP will be Activation Required and Activation time will be empty (Fixed in UR7)
- Unable to restart or stop service by clicking the server name using Azure AD credentials (Fixed in UR8)
- GWT > Server when trying to merge an existing Endpoint for discovery status fails for Active Directory (Fixed in UR8)
- Patches > Remediation Plan > Apply Date Filter > Actions >Download Reports Download fails (Fixed in UR8)
- Endpoint > Readiness > Endpoint Readiness settings > Enable. Getting disabled after some time (Fixed in UR9)
- System > Smart Group > Create - SG Stuck on the status "Create Group" for Linux Only (Fixed in UR9)
- RP Dashboard > Action > Delete all Archive Plans (Fixed in UR9)
- Discovery source involved querying a different group within Active Directory compared to the existing AD discovery (Fixed in UR9)
- Patches > Remediation Plans > Apply Filters > Download Reports (Fixed in UR9)
-
Remediation Dashboard > Filter View > ACTION > Bulk Procedure – Actions will be performed on Filtered view only (Fixed in UR9)
- Automatic Remediation Plan Rules > Create Auto RP Rule and save without auto-activation > click on Create RP now (Fixed in UR9)
- Endpoint Management > Filter Endpoints > Assign to Tag - Tag is assigned to all endpoints instead of only the filtered ones.(Fixed in UR10)
- Fixes issue when you upload empty JSON for discovery under Tools Catalog > Tools Discovery (Fixed in UR10)
- Fixes issue when trying to upload a file/Script under Tools Catalog > Tools Discovery & System > Tasks & Scripts.(Fixed in UR10)
- Upgrade Tomcat to version 9.0.91 (Fixed in UR11)
- Fixes issue with incorrect "Unsupported PowerShell Execution Policy" exemption for VMs with "RemoteSigned" policy (Fixed in UR11)
- Fixes issue for potential overlapping AD group discovery (Fixed in UR11)
- Fixed inconsistent AD Group discovery counts due to sync timing with the same baseDN (Fixed in UR12)
- Resolved an issue where endpoints were repeatedly moved between directory services during AD Group discovery, causing inconsistent workstation counts (Fixed in UR12)
- Fixed issue where endpoints were not assigned to tags in the Endpoint > Management > Manage Tags (Fixed in UR13)
- Fixed loading issue on Maintenance Rules page by resolving query timeout and improving error handling (Fixed in UR14)
- Fixed a potential race condition that caused transient parameters to be lost, resulting in missing arguments and patch files (Fixed in UR14)
- Fixed redundant logging of exemption additions and removals occurring simultaneously in Logs & Alerts (Fixed in UR14)
- Fixed CSRF checks for API calls under "/rest/experimental/patch-governance/" (Fixed in UR15)
- Minor UI issue in the inspect window (Fixed in UR15)
- Added a method to retrieve a list of servers filtered by a specific tag, with space in tag (replace with %20) or those without any tags (using /vmanage-server/rest/rest-api/servers?tags=null) (Fixed in UR16)
- Fixed NPE on VLinkNetworkEventListener (Fixed in UR17)
- Fixed Maintanance Window incorrect next slot calculation (Fixed in UR18)
Comments
0 comments
Please sign in to leave a comment.