DriveLock Customer Forum
Information
4 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 -
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 -
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.
-
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?