Skip to main content
All CollectionsProduct InfoRelease Notes
Minor Release Notes - v2024.2
Minor Release Notes - v2024.2
Alex Patnick avatar
Written by Alex Patnick
Updated over a week ago

2024.2.72

Improved Load Balancer Discovery

We've fixed a minor issue where, in some cases, it was not possible to set up a new load balancer.

2024.2.69

Improved Software Discovery
We've fixed a minor issue with remote proxy functionality to ensure smoother software discovery processes.

Enhanced Azure Discovery
Addressed a specific scenario where Azure discovery might not function as expected, ensuring consistent performance.

Shadow IT Filters Now in the UI
Filters previously limited to the database are now accessible in the UI, giving you more control to manage and customize them.

Advanced Search Enhancements
Resolved an issue where advanced searches with multiple parameters occasionally returned empty results, ensuring more reliable outcomes.

2024.2.67

Enhanced Netscaler Integration
We’re excited to announce that Faddom now supports discovering your Citrix Netscaler via APIs, offering a modern alternative to SNMP for seamless integration.

With this update, Faddom can now discover your SNIPs and display them accurately within Application Maps, enhancing their precision and usability.

Improved Accuracy in Software Discovery Testing
Windows credentials now display correctly when using Test Discovery > Specific Credentials.

Streamlined License Count Display
We’ve resolved discrepancies in license counts between the Dashboard and My Account screen.

Simplified User Access Control
Administrator password changes are now guaranteed to take effect every time, eliminating any previous inconsistencies.

2024.2.63

Improved Migration Waves View
You can now expand the dependencies card to full screen, making it easier to explore server dependencies during migration wave planning.

Application Maps Update Fix
We’ve resolved an issue that occasionally prevented Application Maps from updating.

Azure Discovery Fix
We’ve resolved an issue that previously impacted the accurate discovery of Azure environments in some cases.

Did this answer your question?