I don't think anyone denies that reality. 

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Craig Mills
Posted At: Thursday, March 22, 2007 1:17 AM
Posted To: swynk
Conversation: Having the Exchange 2003 be a DC as well.
Subject: RE: Having the Exchange 2003 be a DC as well.

Well said Mr. Crowley. And I appreciate the detailed succinct comments.
However, with SBS one server, one DC with Exchange. The small client
does
not always have the niceties of putting everything on a separate server.
The
small client must live with your stated limitations and does so
admirably.


Craig A. Mills
Advance-Tech Services
(714) 620-5386

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ed
Crowley [MVP]
Sent: Wednesday, March 21, 2007 9:06 PM
To: Exchange Discussions
Subject: RE: Having the Exchange 2003 be a DC as well.

Is that a pro or a con?  And what does it mean?

Here are my reasons not to install Exchange on a DC.

1. Performing a disaster recovery on a DC is quite a bit more difficult
than
on a member server.

2. Once you make the decision to install Exchange on a domain
controller,
you cannot demote it later.

3. Exchange 2003 directory services won't fail over to other domain
controllers when it is installed on a domain controller.

4. Exchange admins must have log on locally rights to the Exchange
server,
so when Exchange is on a domain controller they must have that right in
the
entire domain.

5. Exchange takes longer to shut down when installed on a domain
controller.

6. Use the /3GB switch can cause Exchange to monopolize the memory on
the
domain controller.

7. All services run under the LocalSystem context, so any attacker
gaining
access to Active Directory will also have access to Exchange. 

Ed Crowley MCSE+Internet MVP
Time Magazine's Person of the Year! 
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Michael
Henry
Sent: Wednesday, March 21, 2007 5:32 PM
To: Exchange Discussions
Subject: Having the Exchange 2003 be a DC as well.

I am back peddling here, because a 'consultant' said, "that it's
generally
not recommended that the Exchanger server be a DC as well.", to my
manager.

Ok, I have two Exchange 2003 Books, and neither one cautioned against
this.
Nor did this show up in my research for the upgrade. 

So what are my pros and cons:

1.  My reason is that E-mail will always deliver to clients, because it
will
not when a DC is not present.

Thank much,  Michael


_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange
To subscribe: http://e-newsletters.internet.com/discussionlists.html/
To unsubscribe send a blank email to [EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]
To unsubscribe via postal mail, please contact us at:
Jupitermedia Corp.
Attn: Discussion List Management
475 Park Avenue South
New York, NY 10016

Please include the email address which you have been contacted with.

Reply via email to