Hi Windminstrel,
DHCP Clustering is easy to use, but you can also make a big scope on two
machines and use the same scope with conflict detection.
Keep the following points in mind when using a Windows cluster for the DHCP
service:
The DHCP service should be installed before the clustering service is
installed on the computers.
As with most cluster installs, one server should be configured first, with
the DHCP service and the clustering service, while the other cluster
member-to-be is powered off.
When you're finished with the installation on the first member, power up the
second and install the DHCP service and then the cluster service.
Here are some Microsoft article's about clustering
http://technet.microsoft.com/en-us/l.../cc778572.aspx
http://www.microsoft.com/technet/pro....mspx?mfr=true
http://technet.microsoft.com/en-us/l.../cc739532.aspx
--
Greetings,
Robert Smit
Blog :
http://fiberman.spaces.live.com/
"Windminstrel" <> schreef in bericht
news:4940528e$0$48225$...
> It goes without saying that there are a good number of reasons to deploy
> fault-tolerant DHCP, and that in the case of reserved leases (such as for
> printers and remote servers that move about like those on construction
> sites), how can we deploy DHCP such that no intervention would be required
> immediately in the event of a loss-of-single-point-service failure. I
> thank-you all in advance for your responses. I am having trouble locating
> a
> documented best-practice.
>
>