Release Notes Endpoint Data Protection 23.0.2
About This Release
Endpoint Data Protection 23.0 Update 2 provides new and improved features that have been implemented. During the development of this version, we have been focusing on valued feedback from our customers and partners to provide an ideal feature selection.
Deprecations
Please find all Endpoint Data Protection related deprecations in version 23.0 Update 2 below:
- SQL Server 2012 and Windows 2012 R2 are no longer supported
- MySQL will be out of support beginning with version 24.0.0
New Features and Improvements
Endpoint Data Protection
Please find all new Endpoint Data Protection related features and improvements in version 23.0 Update 2 below:
- Added BitLocker PIN management
- Added an option to define a preboot PIN before device encryption is complete
- Added possibility to mass edit BitLocker configurations
- Fixed an issue with data processing when using MySQL DB
- Fixed an issue where under certain circumstances, the keyboard and mouse controls were incorrectly shown as disabled in global client settings after a client reboot
- Fixed an issue where under certain circumstances, Azure AD / Entra ID failed to synchronize correctly
EgoSecure Agent
Please find all new EgoSecure Agent related features and improvements in version 23.0 Update 2 below:
- Fix an issue where in certain circumstances, the agent had a signing issue.
AntiVirus
Please find all new AntiVirus related features and improvements in version 23.0 Update 2 below:
- AntiVirus has been updated to Bitdefender SDK version 3.0.1.297.
Hotfixes
- 23.0.2.2
Fixes an issue where the Antivirus (AV) Component is partially dysfunctional. It is expected that only a server upgrade is needed, followed by a reboot of the affected agents, will restore full functionality of the AV Component without the need to upgrade all the agents to 23.0.2.2. However, we recommend updating the agents too as a precaution.
Fixes an issue in 23.0.2.1 regarding EgoSecureAgent.exe file's digital signature. - 23.0.2.1
Fixes an issue where after upgrading the server to 23.0.2.0 some older agents could not be upgraded to 23.0.2.0 as well.
Additional Information
- For details about system requirements, please refer to Software and hardware requirements
- For details about installation and update setup, please refer to Installation and Update