1
00:00:03,080 --> 00:00:03,700
Okay.

2
00:00:03,710 --> 00:00:08,450
So now I want to summarize what we've learned in this module around loopback process.

3
00:00:09,460 --> 00:00:15,010
So loopback processing again is this notion that you can have a different set of user settings when

4
00:00:15,010 --> 00:00:20,500
a user logs on to a specific machine or machines than they would normally get from their user account.

5
00:00:21,530 --> 00:00:25,700
So loopback processing comes in those two modes replace and merge.

6
00:00:26,650 --> 00:00:32,050
And remember that Replace says We're going to run your user settings from the loopback machine and whatever

7
00:00:32,050 --> 00:00:34,930
user settings are processed by the loopback machine.

8
00:00:35,080 --> 00:00:37,780
But we're not going to run your normal user settings.

9
00:00:38,750 --> 00:00:41,630
It doesn't mean it removes your normal user settings.

10
00:00:41,750 --> 00:00:46,490
It means it doesn't reinforce them from the policies that they normally get processed from.

11
00:00:47,430 --> 00:00:53,310
So if your loopback user settings conflict with any of your normal user settings, those loopback settings

12
00:00:53,310 --> 00:00:55,230
are going to get are going to win.

13
00:00:56,160 --> 00:01:02,040
Now Merge Mode says first we're going to run your regular user settings just like we normally do, and

14
00:01:02,040 --> 00:01:04,830
then we're going to process the loopback user settings.

15
00:01:05,800 --> 00:01:11,770
And again, if any loopback settings are in conflict with your regular user settings, they will get

16
00:01:11,890 --> 00:01:13,330
they will essentially win.

17
00:01:14,280 --> 00:01:20,340
So loopback settings for the user always win in the case of both merge and replace when there's a conflict

18
00:01:20,340 --> 00:01:21,660
with your current settings.

19
00:01:22,680 --> 00:01:28,560
So loopback is useful, of course, for several different scenarios that we talked about kiosks, VDI

20
00:01:28,560 --> 00:01:33,810
systems, remote desktop server systems, Citrix Zen app or Zen Desktop Systems.

21
00:01:33,930 --> 00:01:39,510
Any situation where you want the user to have a different user experience based on the particular machine

22
00:01:39,510 --> 00:01:40,800
that they're logging into.

23
00:01:41,670 --> 00:01:45,690
Kiosks again, often run in a single application mode.

24
00:01:46,660 --> 00:01:52,510
You'll recall that I set up a kiosk that was running only IEEE, and the idea is to lock that system

25
00:01:52,510 --> 00:01:55,140
down to prevent all other user activity.

26
00:01:56,080 --> 00:01:59,200
Aadhaar system shared by multiple users.

27
00:02:00,180 --> 00:02:03,030
VDI systems, often wanting to be constrained.

28
00:02:03,240 --> 00:02:06,120
They certainly have shared infrastructure on the back end.

29
00:02:06,120 --> 00:02:11,310
So you want to constrain what the user can do so that they don't wallop other users that are using that

30
00:02:11,310 --> 00:02:12,030
environment.

31
00:02:13,020 --> 00:02:17,040
So both of these use cases benefit from loop back processing.

32
00:02:17,930 --> 00:02:23,420
And again, you may end up using merge mode loopback because you still want the user to get their normal

33
00:02:23,420 --> 00:02:27,050
settings, but you might also want them to get some loopback settings.