1 00:00:03,080 --> 00:00:08,060 So now I want to shift gears and talk about monitoring group policy replication. 2 00:00:08,950 --> 00:00:14,200 But before I do, I want to make a note about the previous section when I've talked about group policy 3 00:00:14,200 --> 00:00:19,000 results and RSVP and all the data that you've got out of those RSVP reports. 4 00:00:19,930 --> 00:00:26,260 So I was showing you the data on a server 2012 or two box, and I will say that Microsoft made some 5 00:00:26,260 --> 00:00:32,230 big strides in terms of the data that it delivered in server 2012 or two and next versions as far as 6 00:00:32,230 --> 00:00:33,640 RSVP is concerned. 7 00:00:34,650 --> 00:00:41,730 The same obviously holds true if you're running AMC on Windows 8.1 and next client versions such as 8 00:00:41,730 --> 00:00:43,710 Windows ten or 11 as well. 9 00:00:44,640 --> 00:00:50,070 But the point here is that you will not get the same level of detail if you're running RSP on AM, for 10 00:00:50,070 --> 00:00:53,970 example, server 2008 or two or Windows seven box. 11 00:00:54,980 --> 00:01:00,710 So for example, the drill downs I showed where it showed how long each client side extension took to 12 00:01:00,710 --> 00:01:01,100 run. 13 00:01:02,040 --> 00:01:07,140 That will not be available if you're on a Win7 box or server 2008 box. 14 00:01:08,160 --> 00:01:10,710 So just a note about RCP data. 15 00:01:10,830 --> 00:01:17,310 If you had the luxury of being able to run your GPM c management station on a Windows eight X or 2012 16 00:01:17,310 --> 00:01:19,620 or two box, you're going to get the most. 17 00:01:20,620 --> 00:01:21,760 Information. 18 00:01:22,680 --> 00:01:28,290 And that includes being able to return that level of detail against down level clients, like reporting 19 00:01:28,290 --> 00:01:30,170 against Windows seven machines. 20 00:01:31,170 --> 00:01:33,230 So lots of good detail there. 21 00:01:33,270 --> 00:01:35,460 If you're running on the latest and greatest. 22 00:01:36,450 --> 00:01:37,260 Okay. 23 00:01:38,210 --> 00:01:40,940 So let's talk about GPL replication. 24 00:01:41,900 --> 00:01:47,720 So as I mentioned, the server side issues were largely caused by the GPU changes, not getting to every 25 00:01:47,720 --> 00:01:50,600 DC in a timely manner or in an accurate manner. 26 00:01:51,610 --> 00:01:56,860 So as you probably remember from my earlier module when I talked about GPL editing. 27 00:01:57,780 --> 00:01:58,620 By default. 28 00:01:58,740 --> 00:02:03,180 All GPIO changes originate at the PDC emulator DC. 29 00:02:04,170 --> 00:02:10,800 So a GPO change has to replicate across all DCS in order for clients in remote locations using those 30 00:02:10,800 --> 00:02:12,630 DCS to get those changes. 31 00:02:13,680 --> 00:02:17,100 So it's important to know when a GPO is up to date. 32 00:02:18,100 --> 00:02:23,110 That's kind of a key piece of knowing, you know, is there really a problem or am I just waiting on 33 00:02:23,120 --> 00:02:24,550 GPL replication? 34 00:02:25,520 --> 00:02:32,600 So starting in Windows eight, Exxon Server 2012 2012, where two Microsoft provides now some basic 35 00:02:32,600 --> 00:02:35,360 GPO status monitoring in PMC. 36 00:02:36,300 --> 00:02:42,120 And this provides a way of monitoring all GPOs across the whole domain, which I wouldn't necessarily 37 00:02:42,120 --> 00:02:48,120 recommend if you're in a very large environment with lots of disks and lots of GPOs or more kind of 38 00:02:48,120 --> 00:02:54,960 pointed being able to monitor individual GPOs across all disks and be able to tell you for a given GPO. 39 00:02:55,890 --> 00:02:57,840 This GPO is up to date. 40 00:02:58,800 --> 00:03:05,070 And this kind of this guy based tool in M.S. sort of supplants what was available in the command line 41 00:03:05,070 --> 00:03:12,270 prior to when 818. X and Server 2012, which was a command line tool called Patrol Duty XXI. 42 00:03:13,180 --> 00:03:15,490 And I never really liked using portable. 43 00:03:15,640 --> 00:03:18,010 It provided some basic information. 44 00:03:18,920 --> 00:03:24,410 But it really didn't have the ability to go deep in terms of replication monitoring, and it would always 45 00:03:24,410 --> 00:03:26,870 seem to hang if you were in large environments. 46 00:03:27,820 --> 00:03:34,870 And the one big plus that the M.S. replication monitoring provides over the alternative, which is tool, 47 00:03:34,870 --> 00:03:40,720 is that the AMC version can do checks summing of the actual file system content in insensible. 48 00:03:41,680 --> 00:03:47,530 So not only can it detect, for example, if the version of the GPO in AD is different than the version 49 00:03:47,530 --> 00:03:49,240 on CIS will on a given DC. 50 00:03:49,360 --> 00:03:55,270 But again, it can also detect whether or not there's content that's missing in that Cisco replica out 51 00:03:55,270 --> 00:03:56,680 on that remote DC. 52 00:03:57,650 --> 00:04:03,200 So if a file is not yet replicated, but the version number has been updated, then you'll actually 53 00:04:03,200 --> 00:04:03,830 see that. 54 00:04:04,850 --> 00:04:10,310 So that's a big plus in terms of monitoring, and that's not something that patrol provides. 55 00:04:11,280 --> 00:04:16,020 And so this is the screenshot of the replication monitoring in PMC. 56 00:04:16,970 --> 00:04:22,310 I've selected this App Locker policy, and if I clicked on the status tab, you'll see that it shows 57 00:04:22,310 --> 00:04:29,690 the baseline GPO, which is usually my PDC emulator, and then whether other GPOs are in sync or replication 58 00:04:29,690 --> 00:04:30,950 is still in progress. 59 00:04:31,890 --> 00:04:37,710 And if you click the Detect Now button, it will rerun the check, go out and touch all those replicas 60 00:04:37,710 --> 00:04:39,930 and find out the state of this GPO. 61 00:04:40,860 --> 00:04:44,970 So let's go ahead and play with that and see what that looks like in practice.