So now I want to shift gears and talk about monitoring group policy replication.
But before I do, I want to make a note about the previous section when I've talked about group policy
results and RSVP and all the data that you've got out of those RSVP reports.
So I was showing you the data on a server 2012 or two box, and I will say that Microsoft made some
big strides in terms of the data that it delivered in server 2012 or two and next versions as far as
RSVP is concerned.
The same obviously holds true if you're running AMC on Windows 8.1 and next client versions such as
Windows ten or 11 as well.
But the point here is that you will not get the same level of detail if you're running RSP on AM, for
example, server 2008 or two or Windows seven box.
So for example, the drill downs I showed where it showed how long each client side extension took to
run.
That will not be available if you're on a Win7 box or server 2008 box.
So just a note about RCP data.
If you had the luxury of being able to run your GPM c management station on a Windows eight X or 2012
or two box, you're going to get the most.
Information.
And that includes being able to return that level of detail against down level clients, like reporting
against Windows seven machines.
So lots of good detail there.
If you're running on the latest and greatest.
Okay.
So let's talk about GPL replication.
So as I mentioned, the server side issues were largely caused by the GPU changes, not getting to every
DC in a timely manner or in an accurate manner.
So as you probably remember from my earlier module when I talked about GPL editing.
By default.
All GPIO changes originate at the PDC emulator DC.
So a GPO change has to replicate across all DCS in order for clients in remote locations using those
DCS to get those changes.
So it's important to know when a GPO is up to date.
That's kind of a key piece of knowing, you know, is there really a problem or am I just waiting on
GPL replication?
So starting in Windows eight, Exxon Server 2012 2012, where two Microsoft provides now some basic
GPO status monitoring in PMC.
And this provides a way of monitoring all GPOs across the whole domain, which I wouldn't necessarily
recommend if you're in a very large environment with lots of disks and lots of GPOs or more kind of
pointed being able to monitor individual GPOs across all disks and be able to tell you for a given GPO.
This GPO is up to date.
And this kind of this guy based tool in M.S. sort of supplants what was available in the command line
prior to when 818. X and Server 2012, which was a command line tool called Patrol Duty XXI.
And I never really liked using portable.
It provided some basic information.
But it really didn't have the ability to go deep in terms of replication monitoring, and it would always
seem to hang if you were in large environments.
And the one big plus that the M.S. replication monitoring provides over the alternative, which is tool,
is that the AMC version can do checks summing of the actual file system content in insensible.
So not only can it detect, for example, if the version of the GPO in AD is different than the version
on CIS will on a given DC.
But again, it can also detect whether or not there's content that's missing in that Cisco replica out
on that remote DC.
So if a file is not yet replicated, but the version number has been updated, then you'll actually
see that.
So that's a big plus in terms of monitoring, and that's not something that patrol provides.
And so this is the screenshot of the replication monitoring in PMC.
I've selected this App Locker policy, and if I clicked on the status tab, you'll see that it shows
the baseline GPO, which is usually my PDC emulator, and then whether other GPOs are in sync or replication
is still in progress.
And if you click the Detect Now button, it will rerun the check, go out and touch all those replicas
and find out the state of this GPO.
So let's go ahead and play with that and see what that looks like in practice.