as soon as a new version of a policy is published, the computer status in the DOC change to Warning outdated policy. This should be configurable with either an offset ( policy version is not smaller than actual policy - offset ) or with a number of days ( new policy version exists since X days but still not deploy on the agent)

under global config > config the settings for automatic update should be set to "no update" when this setting is set to "not configure". Otherwise their might be a configuration conflict with other policies when multiple policy are in use.

Currently running commands can be done only on individual computers under DOC > Computers page. Suggesting to add the ability to issue commands on multiple computers under the same page mentioned above, as well as issue commands on group(s) under DOC > Groups page.

Occasionally there will be a need to manually restart the main DL agent service (enforce policy update, etc.). Suggesting to add the possibility to perform agent service restart while connected remotely using DCC or DOC. This is to be restricted to specific admins/operators only.

Currently the "User selection" rule under Encryption 2-Go or File Protection allows a maximum of three (3) selectable rules. Suggesting to increase this limit to at least five (5) rules if possible.

Currently you can only refresh the whole dashboard tab. Suggesting to also add the feature to allow refreshing a specific widget as needed.

Currently the "secure delete" utility is only available with Encryption 2-Go license. Suggesting to also include it with File Protection license.

Suggesting to allow and facilitate sharing of custom DOC dashboards and widgets created by DriveLock users (customers, resellers, consultants, etc.) via UserVoice or any other suitable platform.

It will be useful to have the possibility in PBA to allow saving/remembering the last used username so that user will only have to type the password. Make this an optional configuration.

DOC sessions will time out after a period of inactivity. This period should be configurable.

For SOCs and ability to display on big monitoring screens (SecOps style), DOC dashboards should have auto-refresh feature. Refresh intervals should be configurable (every 1 minute, 10 minutes, etc.). DOC dashboards should also have the ability to toggle between dashboard tabs every X amount of time (configurable).

Delete computers after x days of no activity/connection in the database (automatically/periodically).
Events should not be deleted.

We use Cisco sDUO as MFA for Windows. Unfortunately, the compatibility in connection with the PBA is missing here and thus no users are synchronized automatically.

When I'm giving a presentation and presentation mode is active, I don't want any DriveLock messages to come up. I want to be able to configure this centrally. The default setting is "No messages at all". And this must be a central general setting and not separately for each DriveLock module. With an extended possibility of this feature, the general switch can control the switches below it, if I want certain modules to show messages exceptionally after all, if I consider them important despite the presentation mode.

the license should be removed (configurable) after x days if the agent has not reported to the DES server.

If the agent then reports back to the DES server, it automatically receives a license again.

In the case of encrypted hard drives, it should not be automatically decrypted

the events that already exist should be retained until the default DES settings delete them

I want to identify actions on uncertain times (E.g: Actions out of business hours or during the weekend).
At the moment my only filter possibilities are e.g. last hour, last day, last x weeks etc. There is no possibility to define granular timeframes like "not from 9 to 5"

In a customer environment where many computers share the same hostname (eg. machines in a large distributed convenience store infrastructure), it would be very useful to be able to register the computer via its IP address or some other unique value, instead of just relying on hostnames/FQDN. Perhaps a feature to allow the customer to select the IP address (or a unique agent registration ID) to be used in our management and operations consoles - without the need for scripting or a convoluted workaround.

It is to be examined whether Drivelock can be used to equip USB data carriers (which are to be procured internally via SAP - e.g. Kingston Data Traveler) with 2-factor authentication (2-FA). Or if other USB data carriers (sticks) are available on the market that fulfill a 2FA requirement.