Okay.
So now I want to summarize what we've learned in this module around loopback process.
So loopback processing again is this notion that you can have a different set of user settings when
a user logs on to a specific machine or machines than they would normally get from their user account.
So loopback processing comes in those two modes replace and merge.
And remember that Replace says We're going to run your user settings from the loopback machine and whatever
user settings are processed by the loopback machine.
But we're not going to run your normal user settings.
It doesn't mean it removes your normal user settings.
It means it doesn't reinforce them from the policies that they normally get processed from.
So if your loopback user settings conflict with any of your normal user settings, those loopback settings
are going to get are going to win.
Now Merge Mode says first we're going to run your regular user settings just like we normally do, and
then we're going to process the loopback user settings.
And again, if any loopback settings are in conflict with your regular user settings, they will get
they will essentially win.
So loopback settings for the user always win in the case of both merge and replace when there's a conflict
with your current settings.
So loopback is useful, of course, for several different scenarios that we talked about kiosks, VDI
systems, remote desktop server systems, Citrix Zen app or Zen Desktop Systems.
Any situation where you want the user to have a different user experience based on the particular machine
that they're logging into.
Kiosks again, often run in a single application mode.
You'll recall that I set up a kiosk that was running only IEEE, and the idea is to lock that system
down to prevent all other user activity.
Aadhaar system shared by multiple users.
VDI systems, often wanting to be constrained.
They certainly have shared infrastructure on the back end.
So you want to constrain what the user can do so that they don't wallop other users that are using that
environment.
So both of these use cases benefit from loop back processing.
And again, you may end up using merge mode loopback because you still want the user to get their normal
settings, but you might also want them to get some loopback settings.