> In order to setup the domain controller features the machine must have a
> static IP address.
Does it need to have a fixed address (static, or reserved dynamic),
or is a true static address required?
> [...] To that end I reserved the IP address of the machine and also
> entered the connection information into the machine manually instead of
> using the automatic setting.
You _can_ do both, of course, but expecting to keep the router's DHCP
reserved-address table synchronized with a static address on the machine
itself mau be asking for trouble. You can do it if you're careful, but
you'd need to remember that these data are kept in two places (which
should agree).
> Now that the information is entered do I still need the address
> reservation entry or can it be removed?
If the machine is configured with a static address, then it might be
safer to remove the reservation in the DHCP server. You can have both
(if you're careful), but you don't need both.
In either case, I suggest using a static (and/or reserved) address
which is outside the router's DHCP pool. (Shrink the pool if it
occupies all the addresses from ".2" - ".254".) If the DHCP server is
smart enough, then it won't issue a reserved address to some random
client, but it can't see your static address assignment, so, if that
static address is (still) in the DHCP pool, then there's little to stop
the DHCP server from issuing it to any random client which asks for an
address.
> [...] Additionally, will this configuration work for the purposes of
> installing the other necessary components of the server or are there
> other factors that need to be dealt with?
My VPN expertise is nil, and I don't know what these "other necessary
components" might be, so I can't tell you much in that direction.
