Should I make the email server a domain controller? 2

[gtgren]

I have a web/email server that uses local user accounts and a network server that has is the domain controller of course that has active directory. Currently my users have a separate password for their email and for their logon onto the network. Should I promote the web/email server to a domain controller so that it can read from the network server, and that way it will be less adminsitration and when a user changes the password it will be replicated. What are the pros and cons? Thanks in advance!

 

[Castor66]

What email package are they using?

 

[agrappe]

I wouldn't do that. Your email authentication is seperate from your AD authentication. You shouldn't need more than one DC per LAN. The replication between DCs could increase the traffic on your LAN and slow your network's performance.

 

[buddafish]

i have to dissagree with agrappe. no less than 2 DC's per segment. this is a MS standard for AD. But... if this WEB server is available from an untrusted network, then no way. also, DC's do a lot of work that is not usually apparent to naked eye. exchange servers (and other mail servers) often consume lots of resources. if it is possible, keep the mail server on it's own.

scottie

 

[agrappe]

That would depend on the speed of your WAN links. I guess I'm just spoiled to my OC-3 & Gigabit WAN links. We have no need for more than one DC per campus.

The debate on MS standards aside, we both agree that the email server should not be made a DC.

 

[gtgren]

Thank everyone I will keep the email server separate. I am using Imail by the way.