1
00:00:01,140 --> 00:00:03,830
No, that's not particularly helpful.

2
00:00:03,830 --> 00:00:09,820
How about repadmin /queue?

3
00:00:09,820 --> 00:00:14,540
Okay, that doesn't look too problematic at this point.

4
00:00:14,540 --> 00:00:16,240
And we can force a pull.

5
00:00:16,240 --> 00:00:22,040
I'm just going through the examples that I mentioned on the slide a moment ago.

6
00:00:22,040 --> 00:00:23,420
And then let's force a sync.

7
00:00:23,420 --> 00:00:26,400
Okay, well that seemed like it worked okay.

8
00:00:26,400 --> 00:00:33,840
So let's do a cls, and let's try a repadmin /replsummary.

9
00:00:33,840 --> 00:00:34,380
Okay.

10
00:00:34,380 --> 00:00:39,440
Yep, so 0 failures, no error count, but we've got a short delta.

11
00:00:39,440 --> 00:00:40,740
Okay, yeah, so it's looking good.

12
00:00:40,740 --> 00:00:44,620
I'm kind of talking aloud, thinking aloud, as I mentioned before.

13
00:00:44,620 --> 00:00:48,790
The other thing we can do is look at Sites & Services,

14
00:00:48,790 --> 00:00:51,500
the MMC console, and then, of course,

15
00:00:51,500 --> 00:00:55,740
there is Event Log and all of your traditional services.

16
00:00:55,740 --> 00:00:59,110
But in terms of troubleshooting network‑related errors,

17
00:00:59,110 --> 00:01:00,900
latencies, and that kind of stuff,

18
00:01:00,900 --> 00:01:04,250
we actually want to be really careful to make sure that our

19
00:01:04,250 --> 00:01:06,300
domain controllers are placed properly.

20
00:01:06,300 --> 00:01:07,530
In my case, they are.

21
00:01:07,530 --> 00:01:11,540
I know because they both are in fact on the same subnet.

22
00:01:11,540 --> 00:01:16,500
So I'll want to associate a new subnet object with that site so that

23
00:01:16,500 --> 00:01:20,500
Active Directory knows exactly what the topology is.

24
00:01:20,500 --> 00:01:25,260
What you're doing here with Sites & Services is mapping the physical TCP/IP

25
00:01:25,260 --> 00:01:29,470
topology of your environment to these logical constructs,

26
00:01:29,470 --> 00:01:30,290
these sites,

27
00:01:30,290 --> 00:01:33,290
and then you wind up with these connection objects

28
00:01:33,290 --> 00:01:36,260
that come up between your machines.

29
00:01:36,260 --> 00:01:41,740
Now notice that you can replicate, you can force a replication here as well.

30
00:01:41,740 --> 00:01:46,430
Okay, yeah, I clearly have a non‑optimal environment now,

31
00:01:46,430 --> 00:01:49,240
and I'm really curious to get into it.

32
00:01:49,240 --> 00:01:52,350
I'm not going to bore you with those details myself.

33
00:01:52,350 --> 00:01:54,740
So I'm going to call this demo done.

34
00:01:54,740 --> 00:01:57,480
Certainly, for the purposes of AZ‑801,

35
00:01:57,480 --> 00:02:01,230
you have everything you need to know as far as troubleshooting

36
00:02:01,230 --> 00:02:04,540
these Azure and on‑premises virtual machines.

37
00:02:04,540 --> 00:02:07,090
You may see a little bit of repadmin syntax.

38
00:02:07,090 --> 00:02:09,940
You won't have to write any code on your exams.

39
00:02:09,940 --> 00:02:12,310
Instead, you'll see an extractive code,

40
00:02:12,310 --> 00:02:15,140
and you will be asked to interpret what's there.

41
00:02:15,140 --> 00:02:19,200
And I would submit that you setting up a small two‑VM

42
00:02:19,200 --> 00:02:22,290
domain controller‑to‑domain controller environment and

43
00:02:22,290 --> 00:02:31,000
playing around a bit on your own, going into Event Logs, you'll get a nice intuitive feel for how the technology works.