1 00:00:03,090 --> 00:00:05,010 So order of precedence. 2 00:00:05,940 --> 00:00:09,060 Let's take a look at it in the test system that we have here. 3 00:00:09,930 --> 00:00:15,780 Now, let's take the scenario where my user Joe user Joe Sales in the user's view in sales wants to 4 00:00:15,780 --> 00:00:16,860 process policy. 5 00:00:17,730 --> 00:00:22,080 Remember that we said that the order of processing is LCD, O.U. 6 00:00:22,890 --> 00:00:25,230 Or local site domain and. 7 00:00:25,230 --> 00:00:25,800 Oh, you. 8 00:00:26,610 --> 00:00:30,060 Well, let's say that Joe's sales computer is in the Dallas site. 9 00:00:30,930 --> 00:00:35,550 And let's say that the Dallas site in in this case is this default first site, name site. 10 00:00:36,420 --> 00:00:40,680 Note that I have a link to that site called Dallas Sales Office Printers. 11 00:00:41,580 --> 00:00:45,420 So after Joel logs into his system, the local GPO gets processed. 12 00:00:45,600 --> 00:00:51,210 Then he's going to process the site based on EU or GPOs, in this case, the Dallas Sales Office printers. 13 00:00:51,420 --> 00:00:55,200 Then we move up to the domain level and you will see that at the domain level. 14 00:00:55,230 --> 00:01:00,510 The domain has the default domain policy linked and this other GPO called Domain Wide Settings link 15 00:01:00,510 --> 00:01:00,900 to it. 16 00:01:01,770 --> 00:01:06,120 If I come over here, you'll see these links and you'll note that they have a link order. 17 00:01:07,050 --> 00:01:07,710 I can. 18 00:01:07,710 --> 00:01:12,390 In the case of any container, you can have many GPOs linked to that container level. 19 00:01:13,260 --> 00:01:18,630 I can use these up and down arrows to change the order of precedence or the order of processing within 20 00:01:18,630 --> 00:01:19,320 a container. 21 00:01:20,240 --> 00:01:25,130 Where the one that's number one in the link order is process last and therefore remembering our last 22 00:01:25,130 --> 00:01:27,740 writer wins rule this the GPO. 23 00:01:27,770 --> 00:01:35,060 If there are any conflicting settings between these two GPOs the domain wide settings GPL will win because 24 00:01:35,060 --> 00:01:37,880 it will be the last one that gets processed by that user. 25 00:01:38,810 --> 00:01:44,960 So again, you can have multiple GPOs on a container and you can control not only, you know, the LSW 26 00:01:44,960 --> 00:01:49,760 model applies across containers but within containers you can apply or control the order. 27 00:01:50,640 --> 00:01:53,820 And number one means process last and therefore wins. 28 00:01:54,720 --> 00:01:56,400 It's the highest priority. 29 00:01:57,330 --> 00:01:59,770 Finally any GPOs linked to the users. 30 00:01:59,790 --> 00:02:05,460 Oh you were the Joe sales user account resides are processed lsw. 31 00:02:05,490 --> 00:02:07,440 So this guy gets processed last. 32 00:02:08,330 --> 00:02:13,550 And if it has any conflicting settings of any of the GPOs above it, those also would be overridden 33 00:02:13,550 --> 00:02:16,160 by the settings within the sales user policy. 34 00:02:17,060 --> 00:02:21,320 So the concepts are local site domain or you for a given user or computer. 35 00:02:21,320 --> 00:02:25,910 And within a container you can have multiple GPOs and you can control the order of those. 36 00:02:26,840 --> 00:02:32,000 Hopefully that makes the whole notion of LSW a little bit clearer and brings it home in terms of how 37 00:02:32,000 --> 00:02:35,870 the engine evaluates the list and when it runs each GPO.