DriveLock Customer Forum
Information
104 results found
-
Delete computers after x days of no activity/connection
Delete computers after x days of no activity/connection in the database (automatically/periodically).
Events should not be deleted.16 votesThis feature request will be part of the 24.2 release
-
The Domain field for the PBA login should be able to be preconfigured via the policy
In the policy when configuring the DriveLock PBA for Full Disk Encryption and BitLocker Management, it should be possible to define the domain so that it does not have to be done by the user at the first login. Optimal would be to be able to determine whether this can be changed or not.
14 votes -
PBA Sperrbildschirm anpassen / ändern
Beim Start der BitLocker PBA soll es möglich sein, den Sperrbildschirm per DriveLock GPO überspringen zu können. Weiterhin soll es möglich sein, den dort angezeigten Text (momentan DriveLock Version & Uhrzeit) anpassen zu können.
12 votes -
improve the deinstallation
The DL Agent uninstallation should be complete.
Deleting all dl registry entries and directories would be nice.10 voteswill be part of 2023.1
-
Manage MS BitLocker within the DriveLock console
As an admin I want to fully manage BitLocker within the DriveLock console to enforce the BitLocker encryption policy options that I set for the enterprise. I want to monitor the compliance of endpoints with those policies, and report on the encryption status of both the enterprise and the individual computers
10 votes -
USB drive and device control on macOS
The goal with Device Control should be to support more platforms, especially macOS
9 votesWith the release 2022.2 we also released our first version of our DriveLock Agent for macOS.
Our release notes and documentation available on https://drivelock.help contains more detailed information.
We will continue to improve the feature set in the future and add more and more capabilities.
The status of this idea is updated to "released".
-
NTFS Write support for DriveLock MEA (Mobile Encryption Application) without installation
It should be possible to have read and write capabilities when using an NTFS file system in a DL container in combination with the MEA.
Currently you need to install the MEA on a client to have write access. For a lot of people without admin rights, the installation of the MEA is not possible.
Currently you need to use NTFS file system, when you want to us containers bigger than 4 GB, because FAT is only supporting 4 GB.
And exFAT is currently not supported.9 votespart of 24.1
-
Lock settings unique ID
It should be possible to create a unique assignment to the used rule from DriveLock events (Drive locked, Drive accessed, etc). Currently the ID 0000000-C0D0-C0D0-0001-00000000000X is used without being able to clearly identify the device category.
8 votesThe DOC now always displays the associated rule in the Detail View in the Related Object List block.
-
Security Awarness Viewer
It should be possible to see the offered context via a kind of viewer before setting up a campaign.
This could be a PLAY button in the DOC for security awareness, or similar.7 votesSince 2023.2 a preview can be started from the DOC. There is also a preview screenshot in the DOC for the respective content package
-
Bitlocker2Go Implementation
Die Möglichkeit, alternativ zu DL2Go, externe Datenträger mit Bitlocker2Go verschlüsseln zu lassen, um die bestehenden Beschränkungen von DL2Go zu umgehen.
6 votes -
Offer the possibility to remove the "blur" effect in the PBA
It should be possible to remove the "blur" effect in the PreBoot Authentication.
For customers who, for example, store a background image with company data in case the device is stolen / lost, this is not practical.
The "Show Pre-Boot User Information Message" feature is not really useful here, as probably only a few people will click on the small message icon at the bottom right of the screen. Alternatively, of course, this feature could be reworked to make this more present.5 votesThis feature request will be part of the 24.2 release
-
The hardcoded 1440min Defender State Reporting should be configurable by policy
The DriveLock Agent sents the Defender state today (hardcoded) every 1440min to the DES.
We want to have it configurable over Policy Settings, to allow a more frequent Status Report
sent by the Agent to the DES, to get a more sufficient and useful view within the DOC.
Just manual registry Settings are not sufficient for us, we want to rollout a Defender reporting Interval of every 6hours
to all of our clients - configured by policy.5 votesSince version 2023.2, the interval is 6 hours and no longer 24 hours. In addition, the Defender add-on sends messages as soon as something happens on the agent (virus, pattern updated, ...).
-
Get Local Admin Password via DOC (Native Security)
It should be possible to retrieve the password of a user created via the OS management in the DOC and not only via the agent.
Maybe if the Trust to the AD gets lost, the user won´t be able to login to his computer anymore.
5 votes -
automatic license removal after x days
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
5 votesAgents no longer use a license after 30 days of inactivity, so the license becomes available.
-
DOC: Filter for timestamp should be more granular
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"5 voteswe added more granular filters (2023.1)
-
Prevent duplicate Serial Numbers in Whitelist Rules
When creating a new device whitelist rule e.g. für USB flash drives, there is an option to allow only USB flash drives with specific serial numbers. However, it is possible to add the exact same serial multiple times in the same rule. That makes no sense and therefore should not be possible. DriveLock should check whether or not the serial to add already exists and if so, notify the user and not add the same serial again.
5 votesDriveLock 2021.2 is available now.
-
USB drive and device control on Linux
The goal with Device Control is to support more platforms, especially Linux.
USB drive and device control on Linux (of several flavors)5 votes -
Dark Mode bzw. Dunkelmodus
Es wäre schön, dass im DOC die Möglichkeit besteht (Toggle), dieses auch im Dark Mode anzeigen zu lassen. Ist mittlerweile in sehr vielen Apps standard und extrem gut genutzt. :)
4 votesThis feature request will be part of the 24.2 release
-
DOC: Run commands on groups and multiple computers
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.
4 votesIt is possible to perform remote actions on several computers at the same time. Go to the inventory, select a group, select several computers and perform actions.
-
Support of Azure AD objects (e.g. groups)
We would like to give different users on our InTune managed notebooks access to certain devices based on Azure-AD groups and not to other users.
4 votesAzure AD integration was released with DriveLock 2022.1 for all our cloud managed services customers.
- Don't see your idea?