Configuring Managed users with no local storage access (Roaming Facility)
When a user activates their machine with the ESET Endpoint Encryption (EEE) Server the process updates the HKEY_CURRENT_USER branch of the registry with their activation details and a file known as the Key-file is created within their Windows user profile for storage of encryption keys and licencing information.
If you are working in an environment where the users ability to write data to the system or registry is restricted then you can make use of the roaming facility in EEE to ensure the activation details and users encryption keys are stored on a network path.
This method can also be used to elimiate the requirement for a user to activate on every PC they use.
This guide assumes you are using EEE Server v2.4.5 or later and Client Install v4.5.4 or later.
To enable this within your EEE Server do the following :
Note - Configuring the clients in this manner will not allow the use of Full Disk Encryption on the machines.
The policy changes detailed above cannot be pushed across the network to the clients, instead you will need to update clients by using the Download Settings File button to obtain a registry file to update existing installs or download an install with the new settings merged using the following steps.
Activate the users as normal by generating an activation code and entering it into the client. Note when the users workstations will appear in the Enterprise Server Remote Desktop Services branch with a TS_ prefixed identifier.
When the user first activates, two files will be created in the path pointed to by their Key-File Location path, these are named tokenstore.dat (Key-file) and tokenstore.usr (registry settings).
When the user moves to a second machine the settings and activation data will already be loaded from the network path and they will not be required to activate again.
Keywords: citrix, redirected, rds, roaming