Re: Pitfalls of Combining DC, DNS, DHCP
From: Patrick Kremer (n/a)
Date: 08/03/04
- Next message: Scott Harding - MS MVP: "Re: Pitfalls of Combining DC, DNS, DHCP"
- Previous message: ply: "Adding Second Processor"
- In reply to: SWE: "Pitfalls of Combining DC, DNS, DHCP"
- Next in thread: Scott Harding - MS MVP: "Re: Pitfalls of Combining DC, DNS, DHCP"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 3 Aug 2004 16:19:31 -0500
I do this in smaller installations such as yours all the time...
particularly with DNS and DHCP.
I would be concerned about having only 1 domain controller. If one machine
crashes, your whole active directory installation is toast and you have to
start over. Even if it's just a crappy spare box running AD and nothing
else, I highly recommend a second domain controller.
"SWE" <me@privacy.net> wrote in message news:2naaohFuprt3U1@uni-berlin.de...
> We have limited funds at my company and are getting ready to purchase a
> Windows 2003 Server to be accessed by 35 users. I know we can put the DC,
> DNS, and DHCP all on the same machine. However, I'd like to know what
kinds
> of problems we might run into by combining all these services. Also, if
it's
> recommended that they be separated (may not be an option for us though)
> which services are more likely to play nice with each other?
>
> If you need more information from me in order to answer this question,
> please let me know what I've missed. Thanks in advance.
>
>
- Next message: Scott Harding - MS MVP: "Re: Pitfalls of Combining DC, DNS, DHCP"
- Previous message: ply: "Adding Second Processor"
- In reply to: SWE: "Pitfalls of Combining DC, DNS, DHCP"
- Next in thread: Scott Harding - MS MVP: "Re: Pitfalls of Combining DC, DNS, DHCP"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|