I keep hearing that the best way to do VDI is to couple UEM and AppVolumes, using AppVolumes for AppStacks and Writeables (UIA Only), and using UEM for the user's profile (folder redirection, windows settings, app settings). Would most of you agree with this recommendation?
We're a small organization (150-200 persistent desktops) and I'm currently running a small pilot group to test these two products (we're going to move away from Citrix/Unidesk). I currently have my pilot group exclusively using Writeable Volumes for a persistent experience and it generally works pretty well, however, I'm told that using UEM for maintaining the persistent experience would be better in the long run, so I've taken the time to setup a UEM environment and test.
Since doing so I've tested the User Environment functionality (folder redirection, shortcuts, drive mappings, etc.) and the Personalization functionality (windows settings, application settings, etc.). All of which seem to work well, but at this point I've only tried using the out-of-the-box configurations for Personalizations. It seems like it could take a lot of time to build your own configs for every application that isn't already listed. It appears that I would have to track down the registry entries of every 3rd party application that we use in order to try and build configuration files for all of them that would capture user edits/changes (seems daunting and maybe impractical for one person).
Given that, I'm considering using UEM for folder redirection (to protect a user's files) in combination with Writeable Volumes (UIA & Profile). That way I can backup and protect the user's files using UEM, maybe use it to deploy printers, shortcuts, etc., but then rely on Writeable Volumes to catch user installed apps and any custom windows and application configuration changes that the user makes.
Any thoughts? Thank you in advance.