Skip to content

DriveLock Customer Forum

Information

EN: Please share your ideas and suggestions for improvement with us.
At DriveLock, we want to be able to better understand and evaluate your concerns and are working to continually improve our products. Here in our forum you can leave ideas and suggestions, or view and vote for others' ideas. 
You are welcome to write your input in German, and we will translate it into English for you so that as many of our customers as possible can participate.

DE: Bitte teilen Sie uns Ihre Ideen und Verbesserungsvorschläge mit.
Wir von DriveLock möchten Ihre Anliegen besser verstehen und bewerten können und arbeiten an der ständigen Verbesserung unserer Produkte. Hier in unserem Forum können Sie Ideen und Anregungen hinterlassen, oder auch die Ideen anderer einsehen und für sie stimmen. 
Sie können gerne Ihre Eingaben in Deutsch verfassen, wir werden für Sie die Übersetzung ins Englische übernehmen, damit möglichst viele unserer Kunden an den Vorschlägen teilhaben können.


How can we improve DriveLock?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

8 results found

  1. Support for High Availability, Disaster Recovery with SQL Availability Group

    Support for High Availability, Disaster Recovery with SQL Availability Group:
    https://learn.microsoft.com/en-us/dotnet/framework/data/adonet/sql/sqlclient-support-for-high-availability-disaster-recovery#connecting-with-multisubnetfailover

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    on the roadmap  ·  1 comment  ·  Setup / Installation  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. Agent Autoupdate Build-Level Management

    Automatic Agent Update should support Agent-Build-Levels to get rid of the unreal timestamp workaround in the auto update scheduler.

    i.e. if I want to update my Agents to a certain Build, please add a selection of builds so that the Auto-Update-Feature could stay valid and active. If a new Agent-Build was released, Agents should not automatically update until I approve or change the Build level in the Auto-Update-Configuration.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Setup / Installation  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  3. 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 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Setup / Installation  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  4. MQTT (Port 8883) using an 30years SelfSigned Certificate

    MQTT Port 8883 is using an 30years (running time) SelfSigned Certificate, which will be not replaced by ChangeDesCert.exe

    Please implement a Feature within ChangeDesCert.exe tool that
    MQTT Port 8883 will use the same SSL certificate, used by the other DES Server TCP Ports (6667 and 4568)

    Our Company Security Audit (vulnerability scan) detected the Port 8883 with this old SelfSigned Certificate behind.

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    on the roadmap  ·  0 comments  ·  Setup / Installation  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  5. automatish push installation should support tenant

    it seems automatic push installation supports only root tenant

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Setup / Installation  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  6. Software Packages Publishing should be multi tenant aware

    actually the publishing of software package through the DES server (mainly the drivelock agent) works for all configured tenant. It should be possible to published different version of the agent in different tenant.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Setup / Installation  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  7. 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 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    on the roadmap  ·  3 comments  ·  Setup / Installation  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  8. Client update feedback message

    It would be good to see if a client performs an update installation after the release or gives a status that something is happening.
    Often we have the problem that users unintentionally turn off the devices during the drivelock installation, because they don't know that one is running. A popup or something like that would be nice.

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    on the roadmap  ·  1 comment  ·  Setup / Installation  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
  • Don't see your idea?

DriveLock Customer Forum

Categories

Feedback and Knowledge Base

(thinking…)