As an administrator I want to let the Linux Agent send all drivelock agent events also to external systems.
It should work similar like DriveLock Agents for Windows OS.
If we can define a priority, we would like to see the following priority order (for implementing):
1) SMTP (email, supporting TLS/SSL)
2) SNMP

In Encryption2Go it is possible to format the USB removables before encryption and keep the data if necessary - these options are completely missing in BitLocker2Go.

Actually the DOC offers for MS Defender scans: quick, full an drives. An additional option should be add to support the offline scan MS defender supports.

I think it would be good to allow DOC reports (in list format) to be exportable to spreadsheet format, not just in pdf format.

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.

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.

We have repeated requests for USB releases for specific time periods in the future. Would it be possible in the helpdesk temporary unlock window to select a period in the future with time and date specification?

Currently there is no option in the computer config details view of the DOC to have a look at the order of how the policies will be applied on a device.
I would suggest to add a column where you can see the order of the applied policies.

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.

it seams 3rd party event can only be send to the DES as oppose to DriveLock events that cab be send directly by the agent through SNMP/SMTP. Ths should be the case for 3rd party events too.

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.

After the DriveLock Bitlocker installation with PBA, the PBA screen also appears if no user has previously logged on.

The DriveLock PBA should be skipped until the first Windows User has logged on.

Currently the DOC Companion can only be installed, when the user is also local admin on his machine.
But it's a really good security recommendation to separate users internet activities from admin tasks.
So we'd suggest to have an install procedure, that can be started from an admin command line or via a software distribution system.

Add a configuration option to prevent the download/start of DOC_Companion.exe.

DriveLock should allow the creation of alert based on frequency and time. Ideally with boolean logic f.e:
-if event happens (more¦less) X time within Y minutes (most important one)
-if event happens between X am and Y pm
-if event does not happen between X am and Y pm
-if event happened at least X minutes after the last event
-if event not happened after X minutes of the previous event

Today the Encryption to Go feature is able to reformat the physical USB sticks only from FAT32 -> to exFat or NTFS.
We want to have a feature that the USB stick will be always reformatted for example to exFat, regardless which Filesystem is current used by the USB stick. This feature would help to always cleanup USB sticks during container creation, and would help to move from NTFS formatted sticks back to exFat. Which is otherwise a manual task (not possible in a large environment).

Currently the Single-Sign-On method for the PBA or for Windows doesn't support port configuration of 802.1x.
That hinder us from using this feature.

So I'd like to suggest implementing the support of a port configuration 802.1x to use the SSO in the PBA/Win-Login.

With 2021.2 permanently unlocking single drives has become easier than ever before. It would be great to have the same capability for other devices like cameras, smartphones.
Unlocking applications previously blocked by DriveLock application control has been added with 2022.1.

It would be nice to have a set of diagrams showing the use of devices, applications or even other assets over a period of time, as line graphs. This would support risk evaluation showing trends or values different from an expected or usual trend.

Data related to a single person (for example, user names or computer names) should only be visible in any DOC view, if the anonymization has been manually deactivated and if either the current user has a special permission which is allowing to view this data or a second user with appropriate permissions has logged in additionally (four-eyes principle).