On ZDNet: Twitter on your intranet

Avoid these gotchas when installing Exchange 2003 on a domain controller

Tags: Microsoft Corp., Microsoft Exchange Server 2003, Scott Lowe MCSE, domain controller, E-mail Administration Tips Newsletter

  • Save
  • Print
  • Recommend
  • 1

Takeaway: Make sure you know the limitations of installing Exchange 2003 on a domain controller.

Microsoft recommends against installing Exchange on a domain controller, but does support this practice in environments that need to run this way. However, if you do find that you need to run Exchange on a domain controller--perhaps for budgetary reasons--make sure you know the limitations and make an informed decision:

  • Once Exchange is installed on the domain controller, you cannot reduce the server to member server status.
  • Normally considered a best practice, don't use the /3GB switch on domain controllers that are also running Exchange as this can result in Exchange using too much system RAM.
  • A shut down or restart of a domain controller running Exchange can take more than 10 minutes due to the order in which services are unloaded for a shutdown. Before you restart these servers, manually stop the Exchange services to avoid these delays.
  • This installation method seriously hinders your high availability efforts as Exchange will use only the services offered by the host domain controller and will not seek out others if the AD services (i.e. Global Catalog servers) experience a problem.

In general, unless you absolutely have to run Exchange on a domain controller, you should try to install Exchange to a member server.

  • Save
  • Print
  • Recommend
  • 1

Print/View all Posts Comments on this article

CEO/President ceo@... | 05/15/06
Recovery Server thefrown | 06/30/06
b anazarov@... | 05/09/08
Run SBS instead! info@... | 05/15/06
Agreed. TomMerritt | 05/15/06
consultant david_scott@... | 05/15/06
Consultant did nothing wrong curlergirl | 06/30/06
SBS is not always a choice brasslet | 05/15/06
licensing avid | 05/15/06
Max users on 2003 rstultz@... | 05/15/06
thank you for the correction avid | 05/16/06
Nit-Picking info@... | 05/16/06
lame, man just lame dewers@... | 05/15/06
I wondered when someone would say this... brasslet | 05/15/06
For the record Cactus Pete | 05/15/06
That's Not Entirely True bdawson@... | 07/10/06
But SBS should always be considered info@... | 05/16/06
SBS is a rip yinbig | 05/17/06
Incorrect info@... | 05/17/06
Still a Rip because... yinbig | 05/18/06
Backup yinbig | 05/17/06
agreed second dc as backup pmclean | 05/17/06
caution fomoco@... | 05/17/06
Bassackwards... curlergirl | 06/30/06
Partial solution Tony K | 05/15/06
what about when you only have two servers on the network? pmclean | 05/15/06
DCs jdkeith@... | 05/17/06
Definitely 2 DCs rasilon | 07/10/06
Demotion to member server bmwmay@... | 06/27/06

What do you think?

White Papers, Webcasts, and Downloads

Article Categories

Security
Security Solutions, IT Locksmith
Networking and Communications
E-mail Administration NetNote, Cisco Routers and Switches
CIO and IT Management
Project Management, CIO Issues, Strategies that Scale
Desktops, Laptops & OS
Windows 2000 Professional, Microsoft Word, Microsoft Excel, Microsoft Access, Windows XP,
Data Management
Oracle, SQL Server
Servers
Windows NT, Linux NetNote, Windows Server 2003
Career Development
Geek Trivia
Software/Web Development
Web Development Zone, Visual Basic, .NET

Smartphones

advertisement
Click Here