We are beginning to develop a Horizon infrastructure. We see use cases where a given user could be using an Instant Clone, an RDSH session or even a published application. My question is what the best way is to handle the DEM profiles.
I could allow each connection method to use the same profile, but that seems cumbersome (if they use a published app, they would get a lot of profile data they don't need - like Chrome!).
I could create share structures for each connection method: The DEM Config share AND the Profiles share (cumbersome for me)
Could I use nested profiles in the existing shares?
Am I just barking up the wrong tree?
BTW: My Instant Clone test bed w/ DEM is working GREAT!