The compliance state shown in the Metadefender Endpoint Management console and APIs always reflects the most recent report compiled by the Metadefender Endpoint agent. This can create a situation where no user is logged in to the PC but Metadefender Endpoint is running in the background, and therefore cannot report the compliance state of any user-specific settings. These settings include password and lockscreen.
A common scenario is when Metadefender Endpoint is installed on a device, and the device is rebooted but left at the log on screen for an extended period of time. During this time Metadefender Endpoint Management will report user authentication settings are out-of-compliance. The issue is resolved automatically after a user logs in to the device.
This article applies to Metadefender Endpoint Management
This article was last updated on 2015-07-22
(This article was changed to reflect the new name of Metadefender Endpoint on 2016-02-23)