DriveLock Customer Forum
Information
5 results found
-
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-multisubnetfailover3 votes -
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 -
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 voteWe plan to add the possibility that a certain agent version can be published to a specific tenant only. This feature will add flexibility for our own managed services and our partners who manage the environments for their customers.
-
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 -
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
- Don't see your idea?