Symantec Enterprise Vault Outlook Add-in in Non-Persistent VDIs

[cbaptiste]

Has anyone successfully deploy Symantec Enterprise Vault Outlook Add-in in Non-Persistent VDIs successfully?

[VDINinja311]

cbaptiste​ Yes, we have had the EV Outlook Add-in's installed in our Non-Persistent Windows 10 VDI environment for several years now.

Our current setup:

Non-persistent Windows 10 1703 x64 Enterprise (Office 2016 installed on Master Image)

Horizon 7.3.2

App Volumes 2.13.2

UEM 9.2

Veritas Enterprise Vault Outlook Add-in 12.3.1 (Installed into a AppVolumes Appstack where 99% of users get upon logon)

[cbaptiste]

How do you make the cache for EV persistent?

[VDINinja311]

cbaptiste​ Please explain what you mean. The only thing we use the EV Outlook add-in for is to have the end users be able to search through archived emails and to restore them if need be. We don't persist anything for the EV Outlook add-in.

[cbaptiste]

Sure. EV stores cache data in %LocalAppData%\KVS\. It this is not stored somewhere every time user logs in the data will be sync'ed again. Also the EV registries needs to be imported at login and exported at log off. Otherwise, the user will have to configure EV at every logon.

My dilemma here is, and apparently many others, is to change the OVRootDirectory which is %LocalAppData%\KVS\ to another path base on the environment.

[VDINinja311]

We must have some sort of different setup than yours. Here is my %localappdata% while the EV Outlook Add-in is running. No KVS folder at all.

About the only thing I do find when launching Outlook with the EV add-in enabled is some random temp files related to EV logs in %localappdata%\Temp.