DriveLock Product Feedback & Ideas
Share your ideas for DriveLock.
Teilen Sie Ihre Ideen mit DriveLock.
10 results found
-
Restart option after agent update
Currently, a reboot before updating the agent can be configured via the option "Reboot to update agent". This causes the users to be logged out first, then DriveLock is updated and then a reboot occurs. If users logs on immediately afterwards, they can work for 2-3 minutes before a reboot occurs without further warning.
It would be better for the users if the update would happen in the background without reboot (similar to push install/push update via the DCC). The user should get after successful update a message that he should close all programs because the computer reboots. This reboot…
13 votesI don't see it as particularly important, because a reboot during an update is usually not useful. only FFE and FDE actually need a reboot - but only later when the agent is already running again and not when the msi is finished.
-
Automatic client uninstallation when license revoked
Client, which are in a licensed PUSH-OU get the agent automatically installed.
If the client is removed from this, the agent should also be uninstalled again (as with FDE).
The DCC/DOC must also be "informed" about this.
Background is that with a Client with an agent - if necessary inadvertently in the "wrong" OU was installed - but is outside of the "Licensed Group" can neither be administered nor even devices allowed without the agent clean - unfortunately only by "hand" is removed. With geographically distant devices within the organization, this leads to significant problems. With a "network rule" even…
11 voteswe consider automatic uninstallation to be potentially dangerous. We recommend the use of a software distribution solution (UEM)
-
DriveLock License Management (expire dates) over DOC, within an Enterprise Environment
DES Servers, running into an an protected Enterprise Environment configured according Microsoft's Recommendation
for an Enterprise-Access-Modell, should be able to renew their License Date (Maintenance Date) over the DOC,
without having direct Internet access, and without getting each year a new license to activate by phone.
An Implementation idea is maybe a Windows 10 Client System running DOC Companion, while the Client have
Internet Access over a Company Proxy Server, to renew the License at the DES Server backend.4 votesif you issue a new license annually (or whenever the maintenance is extended), then you don't even need one without activation, because the mmc does the activation and you can run it on a computer with internet access or use the telephone activation. You can either activate by telephone or issue the customer with a license without activation. Subscription licenses have to be reissued anyway, at least until now
-
DLSupportAgent.exe
Der "DLSupportAgent.exe" sollte via Kommandozeile bedienbar sein, so dass die Aktivierung nicht zwingend grafisch erfolgen muss. Es sollten die Kommandozeile und die Windows-Powershell unterstützt werden:
z.B. DLSupportAgent.exe -Step [1/2/3/4/5/6/7]
The "DLSupportAgent.exe" should support a interaction via command line (cmd / Windows-Powershell) so that there is no need for a graphical access to the traget system.
3 votesMittlerweile kann man alles über DOC ansteuern.
-
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
-
DOC: X-XXS-Protection aktivieren
DOC: Durch ein Audit ist aufgefallen das der Parameter X-XXS-Protection nicht gesetzt ist. Da dies als Abweichung gilt wäre es gute wenn dieser Paramter gesetzt werden könnte
1 voteAfter checking with and getting an explanation from the customer, this request can be closed.
-
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
-
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.
-
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.
- Don't see your idea?