Release Notes
| 7.36.0 OPSWAT Central Management release November 14, 2024 | OPSWAT Central Management V7 (OCMv7), the newest version of the series, streamlines the product central configuration and added OPSWAT Client management to further enhance the security stance of organizations to protect against risky devices. |
|---|---|
| Built-in MetaDefender Endpoint version | |
| Windows Persistent Endpoint 7.6.2410.580 | Detailed release notes for MetaDefender Endpoint are here. |
| Windows On-demand Endpoint 7.3.2410.315 | |
| macOS Persistent Endpoint 10.4.2410.149 | |
| macOS On-demand Endpoint 10.5.2410.117 | |
| Enhancement | |
| MetaDefender Endpoint's patches for 3rd-party softwares | OPSWAT Central Management now hosts the patches for MetaDefender Endpoint's auto-update feature. Please note that the patch file is packed with OPSWAT Central Management (OCM) installer and users could not updated it through the product console. |
| Setting to configure how long the system should keep an old version of modules | Administrators can configure how long the system should keep old versions of an module. This can be configured via the parameter clean.engines.afterDays in the configuration file gears-onpremise_definition.properties |
| Security Updates | |
| Addressed potential security issues | Upgraded 3rd party libraries and updated server configuration to remediate related vulnerabilities. |
| Bugs Fixed | |
| Processing History did not show scan events with certain scan result types such as "Blocked Verdict by DeepCDR". | Processing History now shows scan events for all scan result types. |
| (Windows only) Memory leak in the OCMService.exe process. | Fixed an issue where a memory leak occurred when the Windows Policy for PowerShell Transcription was enabled but the local System account, used to run the OCM service OCMService.exe, doesn't have Write permission on the target directory |
| The system could not clean up old versions of modules. | Fixed an issue where the cleanup process could not execute if the system could not update an engine when the update package size is more than 3GB. |
| MetaDefender Endpoint instances could not communicate with the OPSWAT Central Management server due to an "invalid agent token" error. | Fixed an issue where the agent token was incorrectly generated on the OPSWAT Central Management server if the active system locale was not English-US. |
Was this page helpful?
