This message was deleted.

What you are trying to achieve is quite illogical, especially with FSLogix.

Yeah I guess its just a glaring oversight on my part. Looking into other options. I mean worst case we have a DG of XenApp boxes

Best option really, make your published appson "silo" application servers

Yeah think its the case.

So then it's just an FSLogix issue, if it's on on silo servers, look above for UPM to become a supplement to your FSLogix sessions and work as a write back system on FSLogix disks.

This is normal, If you have a XA Session that is a desktop, and the same user launches a publihed application it will not launch on the same server. Look up Session sharing details. However it's not supposed to jack up the session

So our desired architecture is we have 2500 users or so with a hosted shared desktop (2019 Server multi-session host), and we also hosts our published apps on that same DG. So we have another 1000 users that will launch published apps from a physical device or persistent desktop, but there are users in the 2500 HSD users that need to launch legacy apps from that same pool their desktop sits on

I see, so you have users that open up a Shared Desktop aka Published Desktop, then they also open up published apps? Are they opening the published application from within the Shared Desktop? Or are they going back to workspace and opening the app from the source where they clicked to open the Published Deskop? The reason I am asking, is if they are in the published Desktop and using Workspace in the share desktop to open published applications vPerfer would help you.

From within the desktop, so logically it may not work at all

Ok, So here is the ticker. What profile type do you have set in FSlogix? I ask because I set Profile type to 3. The first session was RW disk, and the seconds launch for the same user will be in Read mode.

Yeah we have it that way too. I will double check

Also, the shared Desktop they are on. The application that they are opening from Workspace app isn't already on the Published desktop? I am trying to understand why they would go into a published desktop, then open a published app that is hosted on the same machines? Forgive me if you already said this.

Yeah my logic keeps going in a circle and I see more and more why you wouldn't want to do that. We changed vprefer policy and now all the apps launch locally as expected/ desired. We will have some siloed apps that will need to be in a different machine catalog and some legacy apps in the same situation too. So I think I just wasn't thinking this through at all originally. Thanks for the help all.

No worries man. I have done this as well before sometimes we just try to put out something to make everyone happy, we forget about making it easy on us. Glad I could offer some help.