No, that's not particularly helpful.
How about repadmin /queue?
Okay, that doesn't look too problematic at this point.
And we can force a pull.
I'm just going through the examples that I mentioned on the slide a moment ago.
And then let's force a sync.
Okay, well that seemed like it worked okay.
So let's do a cls, and let's try a repadmin /replsummary.
Okay.
Yep, so 0 failures, no error count, but we've got a short delta.
Okay, yeah, so it's looking good.
I'm kind of talking aloud, thinking aloud, as I mentioned before.
The other thing we can do is look at Sites & Services,
the MMC console, and then, of course,
there is Event Log and all of your traditional services.
But in terms of troubleshooting network‑related errors,
latencies, and that kind of stuff,
we actually want to be really careful to make sure that our
domain controllers are placed properly.
In my case, they are.
I know because they both are in fact on the same subnet.
So I'll want to associate a new subnet object with that site so that
Active Directory knows exactly what the topology is.
What you're doing here with Sites & Services is mapping the physical TCP/IP
topology of your environment to these logical constructs,
these sites,
and then you wind up with these connection objects
that come up between your machines.
Now notice that you can replicate, you can force a replication here as well.
Okay, yeah, I clearly have a non‑optimal environment now,
and I'm really curious to get into it.
I'm not going to bore you with those details myself.
So I'm going to call this demo done.
Certainly, for the purposes of AZ‑801,
you have everything you need to know as far as troubleshooting
these Azure and on‑premises virtual machines.
You may see a little bit of repadmin syntax.
You won't have to write any code on your exams.
Instead, you'll see an extractive code,
and you will be asked to interpret what's there.
And I would submit that you setting up a small two‑VM
domain controller‑to‑domain controller environment and
playing around a bit on your own, going into Event Logs, you'll get a nice intuitive feel for how the technology works.