Why does OMVA agent not working as expected?

If you encounter scenarios where everything is $link[page,386145,setup,utilizing-media-manifest-via-the-opswat-media-validation] correctly on the Kiosk/Core/OCM side regarding OMVA functionality as described below, please consider the following limitation that might be impacting OMVA functionality:

Due to faulty settings on the MetaDefender Core side

• Please make sure the “Skip hash calculation “is not enabled on the MetaDefender Core side on the workflow rule to avoid any OMVA inconsistencies.
• Having this option enabled on the MetaDefender Core workflow-rule will result in the media validation process involving the OMVA agent to not function as expected.

Due to faulty time-date settings on the OMVA device

• Please make sure the date/time is set up correctly on the OMVA machine (on an OS level) to avoid any OMVA inconsistencies.
• Having the wrong date/time setup on the OMVA (in comparison to the MetaDefender Core/Kiosk machine) device might result in the validation process not functioning as intended.