Re: can all our servers be a domain controller?
- From: "Asher_N" <compguy666@xxxxxxxxxxx>
- Date: Fri, 25 Nov 2005 08:47:01 -0800
Only marginally. In any case, you might want to promote it and assign all
FSMO roles to it (the 2003 server) before doing the upgrade of the other
2 servers.
having 3 DC as opposed to 2 on the same LAN segment is not gaining you
anything, not hurting either. I can think of only 3 instances where I
would not want to make a server a DC. Exchange, Terminal Services and
ISA.
=?Utf-8?B?VmlqYXkgTWlzdHJ5?= <VijayMistry@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in news:D8D04233-F803-44A9-A92E-085FC15FCC65@xxxxxxxxxxxxx:
>
> well the member server is used as a database server... by making this
> also a DC...would that affect its performance?
>
> "seth" wrote:
>
>> the pro's and con's are going to depend on what the server will be
>> doing i would recommend having at least 2 DC's for redundancy, but
>> of course all of them being DC's isn't wrong in itself
>> as i said, it might matter depending upon the other roles
>>
>> "Vijay Mistry" <VijayMistry@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>> message news:7CBFB750-D9D0-4BB6-9ABE-2E1F1C2F2903@xxxxxxxxxxxxxxxx
>> >
>> > We have 3 servers at our company.
>> >
>> > One of our servers is a member server which is a windows server
>> > 2003. Our other 2 servers are domain controllers running windows
>> > 2000 server.
>> >
>> > We will soon be upgrading to windows server 2003 on these servers
>> > soon.
>> >
>> > Can I make all 3 servers domain controllers? Does it make a big
>> > difference if all 3 are DC or should i leave the member server as
>> > it is..
>> >
>> > What are the pro's and con's of doing this? Thanks
>>
>>
>>
>
.
- References:
- Prev by Date: Re: Lost log files for priv.edb
- Next by Date: win 2003 AD + exchange problem
- Previous by thread: Re: can all our servers be a domain controller?
- Next by thread: Newbie: Auto fowarding to external email address not working
- Index(es):
Relevant Pages
|
