This message was deleted.

The way I see it, we have two options: 1st, allow multiple connections to the same profile container. I don't know if this is still/ever was the recommended config, open to input. 2nd, publish seamless apps and published desktops from separate delivery groups, each pointing to a different profile disk. While this would work, I can see potential for confusion from the user (file exists in downloads/desktop folder on published desktop profile, but isn't there in the seamless app profile.

I use a dedicated DG for published apps. Concurrent access to FSLogix containers was a nightmare for us.

I would take a look, at this article by 🐐 Kindon: https://jkindon.com/citrix-upm-and-fslogix-containers/

@Ryan Gallier are you using folder redirection or anything like that to, for example, make the "desktop" folder consistent between both DG?

you can do that if you so chose. Depending on the needs of your specific published apps

Published Apps are typically (not always, but a lot of the time) a prime candidate for UPM file based profiles - lean mean and quick. Combine with folder redirection for appropriate data (maybe documents, maybe desktop etc) and you are home free. Typically I see published apps on dedicated delivery groups - not always of course and it depends on the apps and use case

We do redirect my docs to home dir, and have always instructed users to keep any important files there vs the "desktop" folder, so I suppose that can be our "out" if someone complains about desktop folder discrepancies. Good to know about UPM - I think in this case, if I can get away with it, continuing to use FSLogix for those and even avoiding folder redirection will be the simplest from a management perspective. I'd say we're > 90% published desktop users/sessions. Good article, thanks for chiming in!