1
00:00:00,840 --> 00:00:05,240
So our exam 800 objective here deals entirely with on‑premises

2
00:00:05,240 --> 00:00:08,900
TCP/IP and the Windows Server IPAM feature.

3
00:00:08,900 --> 00:00:12,010
IPAM stands for IP Address Management.

4
00:00:12,010 --> 00:00:13,740
And basically, this is a solution,

5
00:00:13,740 --> 00:00:17,230
it's a client server solution where we can initiate a

6
00:00:17,230 --> 00:00:20,980
discovery of particular role holders that deal most

7
00:00:20,980 --> 00:00:23,990
directly with TCP/IP in Windows Server.

8
00:00:23,990 --> 00:00:27,510
That would be domain controllers, DHCP servers,

9
00:00:27,510 --> 00:00:30,500
DNS servers, and network policy servers.

10
00:00:30,500 --> 00:00:32,260
I mentioned it's client server.

11
00:00:32,260 --> 00:00:36,610
The IPAM server is a database‑backed application that we can

12
00:00:36,610 --> 00:00:38,760
manage principally using Server Manager,

13
00:00:38,760 --> 00:00:40,860
although there's other mechanisms.

14
00:00:40,860 --> 00:00:43,300
I'm going to in my demo use Server Manager for this.

15
00:00:43,300 --> 00:00:48,180
But we can initiate that discovery and then undertake IP address space

16
00:00:48,180 --> 00:00:52,410
management so we know what's used and what's not in our IP ranges.

17
00:00:52,410 --> 00:00:55,560
We can create reservations in an easier way.

18
00:00:55,560 --> 00:00:56,380
As a matter of fact,

19
00:00:56,380 --> 00:00:59,430
what you find with IPAM is that it gives you a nice single pane of

20
00:00:59,430 --> 00:01:02,850
glass for multi‑server management and monitoring. That is you can

21
00:01:02,850 --> 00:01:05,520
manage DHCP on all of your servers,

22
00:01:05,520 --> 00:01:10,410
DNS on all of your servers, NPS on all of your servers. And then operational

23
00:01:10,410 --> 00:01:15,060
auditing means that we can centrally report on the state. And now, of course,

24
00:01:15,060 --> 00:01:19,430
the weakness, or the Achilles heel, to this last point on operational auditing

25
00:01:19,430 --> 00:01:23,920
is that unfortunately Windows Server IPAM does not have a mechanism to

26
00:01:23,920 --> 00:01:28,930
synchronize database data. You're going to see in the demo that IPAM relies on

27
00:01:28,930 --> 00:01:30,580
a SQL Server database.

28
00:01:30,580 --> 00:01:34,510
You can either use a full instance of SQL Server, or you could use

29
00:01:34,510 --> 00:01:38,390
the Windows Internal Database, but there's no synchronization if

30
00:01:38,390 --> 00:01:42,140
you have more than one IPAM server, so that presents issues in

31
00:01:42,140 --> 00:01:46,830
terms of, well, how distributed your environment is, how well

32
00:01:46,830 --> 00:01:48,410
connected your sites are.

33
00:01:48,410 --> 00:01:50,550
You may, in a worst‑case scenario,

34
00:01:50,550 --> 00:01:56,040
need to deploy an IPAM server in each site and then use your own scripting

35
00:01:56,040 --> 00:01:59,900
skills to do data exports and to aggregate that data.

36
00:01:59,900 --> 00:02:05,000
Unfortunately, it's not an inbox feature. Now let's do that demo.