Connection types
Supported functions depending on the connection type (drive connections only):
| Function |
FAT Clients |
Windows Embedded Client |
Virtual Clients |
Thin Clients |
|---|---|---|---|---|
|
Yes |
Yes |
Yes |
Yes |
|
|
Sharing based on the connected drive letter |
Yes |
Yes |
Yes |
Yes |
|
Approvals based on hardware data incl. serial number |
Yes |
Yes |
Yes |
No |
|
File system filter |
Yes |
Yes |
Yes |
Yes |
|
File system filter incl. header check |
Yes |
Yes |
Yes |
Yes |
|
File logging |
Yes |
Yes |
Yes |
Yes |
|
Shadow copy |
Yes |
Yes |
Yes |
Yes |
|
Requires DriveLock Agent locally |
Yes |
Yes |
Yes |
No |
|
Requires DriveLock Agent on the TS |
No |
No |
The virtual client is used instead of the terminal server. |
Yes |
If you want to use application control on the terminal server, the DriveLock Agent is always required on the terminal server, regardless of the above chart.
FAT clients / desktop clients
A FAT client or desktop client is a normal computer running Windows. The FAT client connects to the terminal server. The DriveLock Agent is already installed on the FAT client, so control occurs right where a device is connected. The user may only use the devices in his terminal server session that are also enabled locally by the DriveLock Agent.
If the FAT clients are in the same domain, the configuration can be done via group policy. Otherwise, we recommend using centrally stored policies.
Windows Embedded Clients
A Windows Embedded client is a special computer running Windows XP Embedded or above. The Windows Embedded client connects to the terminal server. The DriveLock agent is already installed on the embedded client or integrated into the image. Thus, control takes place exactly where a device is connected. The user may only use the devices in his terminal server session that are also enabled locally by the DriveLock Agent.
If the Windows Embedded clients are located in a domain, the configuration can be done via group policy. Otherwise, we recommend using centrally stored policies.
Virtual Desktop Infrastructure (VDI)
A virtual client is a virtual computer with Windows. A client connects to the virtual desktop. The DriveLock agent is installed on the virtual client. A USB mapping driver is used to connect all locally connected USB devices into the virtual computer. The user may only use the devices in his virtual client that are also released there by the DriveLock Agent.
If the virtual clients are located in the same domain, the configuration can be done via group policy. Otherwise, we recommend using centrally stored policies.
Thin Clients
A thin client is a specially stripped-down computer with a proprietary operating system. A thin client connects to the terminal server. The DriveLock agent is installed on the terminal server. The user may only use the devices in his terminal server session that are also released there by the DriveLock Agent.
If the terminal servers are located in the same domain, the configuration can be done via group policy. Otherwise, we recommend using centrally stored policies.