DriveLock Customer Forum
Information
51 results found
-
DOC deployment installation option should support DriveLock groups
In the new DOC 21.2, it is possible to deploy new agent on computer. It would be very nice to be able to use drivelock groups here instead of a static list of PCs.
2 votesThe deployment options are ok for individual computers. Otherwise, we ask customers to use a software distribution solution. I am therefore closing the request.
-
3rd party events should be directly sent by SMTP/SNMP
it seams 3rd party event can only be sent to the DES as oppose to DriveLock events that can be sent directly by the agent through SNMP/SMTP. Ths should be the case for 3rd party events too.
2 votesBackend is the single source of truth. Events can be forwarded by the backend service.
-
Multiselection in white list rules under devices is not possibe
In policy editor, it is possible to multi select WLR under drives in order to move them or delete them but it is not possible to do the very same thing in the devices category. It will be nice to have the same functionality.
2 votesDeclined since everything ultimately goes DOC
-
Make secure deletion feature available with File Protection
Currently the "secure delete" utility is only available with Encryption 2-Go license. Suggesting to also include it with File Protection license.
2 votes -
Share custom DOC dashboards & widget via UserVoice
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.
2 votes -
Too many messages, event ID: 129, because of locked devices
Every time a user connects an iPhone or Android phone to a computer, our Drivelock server gets a message that a device has been connected there. This is not allowed by us and the device will be locked, then different
Messages are sent Event ID: 129.
Now my question, is it possible to create a rule in these cases:
That the user always gets a message (bigger message, not only in the systray) to disconnect the device immediately until he disconnects the device? So that always new messages appear, which the user must click away and he is quasi forced…2 votes -
Agent Updates with Citrix 2016 Desktop
We use Citrix 2016 Desktop as an alternative to software distribution in our agency. With agent updates, the respective end devices should always be rebooted as soon as possible. However, we cannot set this in the update policy because the users cannot see the reboot warnings in the Citrix session, they only appear on the Citrix host. The devices would then just reboot and kick the users out of the Citrix session.
We would need to find a way to make the message visible in the Citrix desktop. Perhaps the reboot warning could also appear in the Windows notifications. We…
2 votesPlease use a software distribution that manages the update in a controlled manner. Furthermore, an agent update does not require a reboot in most cases
-
Temporary unlock with scripts
Sometimes a temporary unlock is almost a daily routine I notice with some customers. Example: PCx, 30 minutes free for USB. With input of PC and time, maybe even from-to (the from is not possible yet) would be very nice with a script. I need to be able to trigger this remotely of course.
2 votesAs there have not been any additional votes on this idea, we will not implement such kind of functionality into DriveLock.
Also because it would introduce a way to bypass security features currently available.
-
Power management
Actions under "power management" should have the option for notebooks in docking station or without alternative with ethernet/power supply or without connection. Otherwise, there is a risk that a notebook in the notebook bag performs an action. It would also be good to configure power options with all setting options as under Windows to establish itself as a central device management solution.
2 votesCurrently most customers do not use these settings and so we will probably deprecate this feature in a future release.
Therefor we will not put efforts into further enhancing this capability.
-
Check PBA Prerequisites - availibility of CA-certifiate "Microsoft Corporation UEFI CA 2011"
Many new notebook systems of the manufacturers HP and Lenovo are shipped with the CA-certifictate
"Microsoft Corporation UEFI CA 2011" disabled in their firmware settings.The DriveLock-PBA is signed with this CA-certificate. So this CA-certificate needs to be enabled and
available on a system in advance of installing the DriveLock-PBA.The installation routine of the DriveLock-PBA should verify if this CA-certifiacte is enabled and available on a system
when attepmpting to install the PBA, and write a message of level=Error when detecting this CA-certificate is not available
on a system.
With this enhancement the administrator of a DriveLock environment will…1 voteSince version 23.1 there is a message with EventID=757 “SecureBoot is enabled but the Microsoft Corporation UEFI CA 2011 certificate is missing.”. This function is therefore already implemented. Please configure this event in a policy so that it is sent from clients to the DES.
-
Wiederholung von Fehlgeschlagenen Installationen
Wir lassen Drivelock automatisch Installieren, indem Drivelock bestimmte AD-Verzeichnisse scannt.
Jetzt ist der Server aber ausgelastet oder Systeme sind zu dem Zeitpunkt nicht mehr am Netzwerk, da die Systeme nach der Installation des Betriebssystems ausgeschaltet werden und dann erst im AD verschoben werden.
Der Scann des ADs erfolgt anscheinen nur zu jeder vollen Stunde und dies lässt sich leider nicht ändern.Kann man implementieren, dass Drivelock fehlgeschlagene Installationen (Netzwerkname wurde nicht gefunden, RPC-Server ausgelastet etc) nicht regelmässig wiederholt?
RPC-Server ausgelastet vielleicht zur nächsten vollen Stunde immer wieder.
Netzwerkname nicht gefunden alle 8 Stunden.Allgemein finde ich es als Verantwortlicher etwas…
1 voteWe will no longer support this feature. We will even remove it because it no longer corresponds to our idea of practical distribution. Instead, one should rely on software distribution.
-
PC Neustart bei Push-Installation verzögern
Beim Update besteht ja über die Konfig die Möglichkeit, den Reboot des Clients zu verzögern.
Bei der Pushinstallation, wenn man den Restart anklickt, erfolgt dieser ja nahezu sofort, ohne das die Möglichkeit besteht Daten zu sprichern.Toll wäre es, wenn man hie die selben Einstellungen wie bei einem Update machen könnte, um dem Benutzer die Möglichkeit zu geben, den Neustart z.B. in eine Pause zu legen.
Den es ist Dumm, wenn der Neustart plötzlich während der Arbeit erfolgt. z.B. bei einem Meeting, Videokonferenz, Kundengespräch etc.
1 votePlease use Software Distribution for appropriate control
-
Citrix VDI and Terminal Server Golden Images should not be counted as a consumed license (from DOC).
Citrix VDI and Terminal Server Golden Images should not be counted as a consumed license (from DOC).
1 voteAt first glance, this use case seems sensible. However, the image is created from a computer with an agent and needs a license. After 30 days, an inactive computer is no longer counted anyway.
-
automatish push installation should support tenant
it seems automatic push installation supports only root tenant
1 voteIn any case, we are currently checking whether this feature should be discontinued in principle. In the cloud environment, this is not an option anyway. Software distribution does the job better.
-
Ability to disable Logging for specific uses of the Usage Policy
When using a Usage Policy with different rules we would sometimes not want the rule to be logged with our enterprise Service (or at least be able to filter it out of our log).
Example:
We have one Rule that creates Usage Policies that we want to see to validate the device daily and add it to the permanent whitelist.
We have a different rule where we would like to show a Usage Policy to that user group for certain devices they connect. We have no need to see this Log in our DOC.Right now we either get all…
1 vote -
Use fingerprint and/or face recognition at DriveLock PBA (Windows Hello support)
When using the Drivelock PBA with Yubikeys to implement a 2FA, the use of fingerprint scanners and facial recognition is not possible. Login works with PIN or username/password.
We have notebooks with fingerprint and face recognition in use. If you activate the functionality in Windows, the Drivelock PBA does not work anymore. The PBA cannot be installed or uninstalled. The PBA users are not synchronized. This means that the additional logon methods cannot be used. With the PBA fingerprint and face recognition should be possible.1 voteThe current PBA does not support face recognition or fingerprint. UEFI does not support that. The request is closed. There is a possibility that we will revisit the issue at some point with further development. Thank you for your understanding.
-
Using VMWare workstation , USB Device can be accessed in VM Client even though it is blocked in host machine..
Using VMWare workstation , USB Device can be accessed in VM Client even though it is blocked in host machine..
1 votePlease contact your support partner or our support team in case of problems. There you will get assistance in analyzing any error and fixing the issue.
-
Deactivate MQTT on the server
It should be possible to disable MQTT on the server side as well. The existing option to disable MQTT on the client side via policy is not sufficient in my opinion. It should best be configurable via a feature in the DMC UI.
1 voteDisabling MQTT by policy provides a way to respond to restrictions on the use of MQTT communications in certain situations and environments.
We do not foresee disabling MQTT server-side at this time, as it is a central part of the DriveLock components' technical communication, the use of which will continue to expand in the future.
-
Manual input of the stored uninstall password
Enable manual entry of the stored uninstall password. Either during uninstallation via "Programs and Features" or another entry "Uninstall Agent" via the systray icon of the DL Agent.
1 voteThank you for posting this request on our feedback forum.
This uninstall password is an additional layer of security to prevent local admins in environments without a zero trust approach from uninstalling the DriveLock agent part.
If for any reasons a single agent needs to be removed we already provide the possibility to use the following administration command-line:
msiexec /x DriveLockAgent.msi UNINSTPWD=<your_password>
The password is checked before the inner MSI part is executed. We would have to change this in order to fulfill requests like this one and decided not to lower security measures here, a while ago.
Please feel free to get in touch with us directly to discuss this in more detail.
-
Nach dem Test die Fehler anschauen
Leider ist es in der Aktuellen Version nach Abschluss der Fragen nicht möglich zusehen was man falsch beantwortet hat man sieht nur unten die runden Punkte mit X wenn man darauf kickt passiert nichts, hier wäre es gut die Frage nochmals zu sehen mit was wurde geantwortet und was wäre richtig gewesen
1 vote
- Don't see your idea?