So our exam 800 objective here deals entirely with on‑premises
TCP/IP and the Windows Server IPAM feature.
IPAM stands for IP Address Management.
And basically, this is a solution,
it's a client server solution where we can initiate a
discovery of particular role holders that deal most
directly with TCP/IP in Windows Server.
That would be domain controllers, DHCP servers,
DNS servers, and network policy servers.
I mentioned it's client server.
The IPAM server is a database‑backed application that we can
manage principally using Server Manager,
although there's other mechanisms.
I'm going to in my demo use Server Manager for this.
But we can initiate that discovery and then undertake IP address space
management so we know what's used and what's not in our IP ranges.
We can create reservations in an easier way.
As a matter of fact,
what you find with IPAM is that it gives you a nice single pane of
glass for multi‑server management and monitoring. That is you can
manage DHCP on all of your servers,
DNS on all of your servers, NPS on all of your servers. And then operational
auditing means that we can centrally report on the state. And now, of course,
the weakness, or the Achilles heel, to this last point on operational auditing
is that unfortunately Windows Server IPAM does not have a mechanism to
synchronize database data. You're going to see in the demo that IPAM relies on
a SQL Server database.
You can either use a full instance of SQL Server, or you could use
the Windows Internal Database, but there's no synchronization if
you have more than one IPAM server, so that presents issues in
terms of, well, how distributed your environment is, how well
connected your sites are.
You may, in a worst‑case scenario,
need to deploy an IPAM server in each site and then use your own scripting
skills to do data exports and to aggregate that data.
Unfortunately, it's not an inbox feature. Now let's do that demo.