Bitdefender Endpoint Security Tools Version 6.2.6.669 Release Notes
Release date: 2015-11-12
New Features and Improvements
File System Protection
Windows
- Improved the product stability in endurance tests.
- Improved the performance of the filters from local console.
- Reorganized the scan log summary for a better user experience.
- The endpoint notifications pop-ups contain also the name of the product.
Resolved Issues
File System Protection
Windows
- The security agent reconfiguration failed when an uninstall password was set. The issue is now fixed.
- On some Windows XP and Windows 2003 operating systems, the endpoint failed to communicate with Control Center. The issue is now fixed.
- The update failed when a proxy was configured both in Control Center and in the browser on the endpoint. The issue is now fixed.
- Traffic scan exclusions for websites with self-signed certificates were not applying and the websites were displayed as unsafe. The issue is now fixed.
-
In some situations, the security agent deployment status in Control Center remained stuck to
In Progress . The issue is now fixed. - In some situations, the full system scan log contained some fictive disk drives. The issue is now fixed.
- The missed scheduled scans were running as soon as possible only when the day was selected in the scheduler. The issue is now fixed.
- In some situations, the firewall rules descriptions were missing from the Power User menu. The issue is now fixed.
- In some situations, the update events were incorrectly added to other types of events in the main window. The issue is now fixed.
- Fixed several untranslated texts.
- Fixed an issue where the favorite scan text was overlapping in some localizations.
Linux
- Linux physical machines from Active Directory appeared in Custom Groups. The issue is now fixed.
- The missed scheduled scans were running as soon as possible only when the day was selected in the scheduler. The issue is now fixed.
Exchange Protection
-
Fixed an issue where the security agent was ignoring email addresses written with wildcards, on these filters: connection blacklist, antispam whitelist, and content and attachment filtering exclusions.
The issue occurred only when the lists contained both plain email addresses and email addresses patterns.