Re: Recommendations for Win2k3 Domain Controllers
- From: "Andrei Ungureanu" <andreix at msn dot com>
- Date: Tue, 14 Jun 2005 22:27:33 +0300
for your number of users you don't need a performant machine. Just put 2
inexpensive computers (no need of server that can run SQL or Exchange; a
computer with 256Mb of RAM is enough) as DCs at main site and one in a
remote site. Ensure that you do system state backups of the DCs. Because of
the way AD sites works no users will authenticate to the remote DC (unless
they are in that site or no other DC is available).
hope my little comment will help you.
--
Andrei Ungureanu
www.eventid.net
Free Windows event logs reports
http://www.altairtech.ca/evlog/
"T. Garay" <moc.etluhcS-noirehpS@yhtomiT> wrote in message
news:ek6ua11k6tdo0b696v87n9dituf8dacbcg@xxxxxxxxxx
>I am looking for comments and suggestions on Win2k3 Domain Controllers
> for our domain...
>
> We have roughly 150 users in AD. Roughly 50 of those are only
> Exchange mailboxes/users.
>
> We have roughly 12 outter offices that will be connected via VPN and
> will have between 1 and 5 users in each.
>
> We have 1 SQL 2000 server that houses all our critical company data.
> We have 1 Exchange 2003 server for email. One main fileserver for all
> user files and profiles. Two Citrix Servers providing applications to
> the outter offices. After that, just a few other servers for other
> misc applications. At the main location, there are roughly 50 or so
> workstations + misc servers.
>
> I would like one VPN site as a disaster recovery location. I plan to
> put a domain controller machine there plus a SQL server, Citrix Server
> and possibly an Exchange server as well. All as backup hardware only.
>
> Right now, we have just 2 domain controllers running on Windows 2000
> servers (one is the SQL server and the other is the fileserver), both
> are DNS and DHCP servers as well.
>
> I am building a machine to be the master Win2k3 Domain Controller and
> that is it (no other software on there except possibly DNS and DHCP).
> I haven't really found a definitive document that says you shouldn't
> put anything else on the machine but I have found numerous references
> to not running a DC with Exchange or SQL.
>
> I want a backup DC as well in the same location but was wondering what
> the thoughts were as far as housing that on a machine such as the
> fileserver? Should I have two machines devoted to nothing else but
> being a DC?
>
> I've had plenty of experiences where an app on a DC misbehaved and I
> had to reboot and suddenly users couldn't send email until that DC was
> back up even though Exchange was on a different machine.
>
> I've also had plenty of issues with apps being IIS-enabled and won't
> work on a DC because of the need for the IUSR and other accounts.
>
> At the disaster recovery location, if I setup a machine there as a DC
> through the VPN, are there any potential problems with that? I don't
> want any authentication to happen with that machine since it will be a
> slow connection. I pretty much only want it to maintain a reasonable
> copy of AD in the event of catastrophic failure at the main location.
>
> Thanks for your thoughts!
>
> -Tim
>
.
- References:
- Recommendations for Win2k3 Domain Controllers
- From: T . Garay
- Recommendations for Win2k3 Domain Controllers
- Prev by Date: Re: getting the lastlogon attr
- Next by Date: ADAM Error: "A referral was returned..."
- Previous by thread: Recommendations for Win2k3 Domain Controllers
- Next by thread: Re: Recommendations for Win2k3 Domain Controllers
- Index(es):
Relevant Pages
|
