This message was deleted.

I always give them a published desktop, then they don't get confused

^^^ This is what we did...and there's still confusion from time to time. But surely less confusion than trying to decipher which apps are truly running on their endpoint and which ones are "seamless".

I always provided a Published desktop, provided access to local applications using ivanti VDX and published apps to silo servers if the apps were incompatible due to very OLD OS requirements or other reasons.

Yeah, if I can't remediate them into the target OS I do siloing via published apps in the published desktop also

We've got both published apps and published desktop. I think i might have to tell the weaker users to try using published desktops to see if that's less confusing

Playing devil‘s advocate here, but in a ideal deployment the end user doesn't have to care or to know if the app is running local or coming as a published app because there's no difference in the environment

Once upon a time, a a client, we changed the color scheme of the title bar for published apps. This made it easy to explain the user that the application was running a published app. I didn't explain them how Citrix works but they knew that it was that special app they were told about.

@Jesper Graff Thanks for the tip! I was considering something like that as well - changing the color of the title bar, or possibly changing the color of the cursor while inside published apps.