Hi all,
I have a conundrum I'm hoping we can get a discussion going around architecture. I have a two site Horizon View deployment for non-persistent VDI in an active active configuration. I wasn't involved in the original deployment and I'm not convinced it is to best practice I must admit. Each site has it's own vCenter, Connection Servers and Composers. Users are distributed between sites via load-balancers.
We are looking to offload the .OST for Office365 using UEM (already in place) via AppVolume Managers and Writeable Volumes for each user. We are also hoping that by creating a Compellent Live Volume accessible by all ESXi host from both sites (managed by their own respective vCenter), that would do away with having to manually copy files between the sites.
i.e. We will deploy one AppVolume Manager at each site, connected to their respective vCenter Server (and ESXi hosts directly) with it's own external SQL DB. The AppVolume Managers are therefore unaware of each other.
We create a Writeable Volume for a test user for example, and locate it on the Live Volume (accessible by all Hosts at both sites) and we configure this on one of the AppVolume Managers. It is my understanding that once configured, we would need to log on to the other AppVolume Manager and choose to 'Import Writeables' for the other site's AppVolume Manager to be aware of the writeable volume for that user? A bit of a headache to have to do that each time you set one of these up but a one time job as far as I can see.
Being non-persistent VDI we shouldn't have a situation where multiple sessions could occur for a user therefore we shouldn't have any clashes and each site's Gold Image will have the AppVolume Agent installed, configured to connect to it's site specific AppVolume Manager. We shouldn't therefore need to set the Witeable Volumes to 'Prevent user login if the writeable is in use on another computer, as when the user logs off one desktop (let's say for example located at site A or even disconnects) the writeable volume should be unmounted and therefore if the user logs in again and gets a different desktop at the same site, then no problem. If they get a different desktop at the other site then again no problem as the writeable volume has already been unmounted from the previous desktop at the other site?
Can anyone see any issues with this or have any suggestions for improvements?
Thanks.
Ed.