Re: Exchange auf DC?

Florian Schalk wrote:
Hi,

ich habe nun mehrfach in verschiedenen Beiträgen gelesen, das es von
MS nicht empfohlen ist Exchange auf einen DC zu installieren.
Hat bitte jemand einen Link von MS, wo das warum näher beschrieben
ist?

Hier mal ein wenig was der ExBPA dazu ausspuckt:
If you are running Exchange Server on a domain controller without Small Business Server, be aware of the following issues:

a.. Exchange Server and Active Directory are both resource-intensive applications. There are performance implications to be considered when both are running on the same computer.


b.. If Exchange Server is running on a domain controller, you must also make that domain controller a global catalog server. For more information about creating a global catalog server, see the Microsoft Knowledge Base article 816105, "HOW TO: Create or Move a Global Catalog in Windows Server 2003" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=816105).


c.. Several Exchange Server directory components, such as Directory Service Access (DSAccess), Directory Service Proxy (DSProxy) and the Message Categorizer will not fail over to any other domain controller or global catalog server.


d.. You should not take advantage of the /3GB startup switch in Windows because it could cause Exchange Server to consume all memory, thus reducing the memory available for Active Directory.


e.. System shutdown will take considerably longer if the Exchange Server services are not stopped before shutting down or restarting the server.


f.. This configuration is less secure because Exchange administrators will have local administrative access to Active Directory, enabling them to elevate their own privileges. In addition, any security vulnerability found in either Exchange Server or Active Directory exposes the other to compromise.


g.. If you are running Exchange Server 2003 on a domain controller, using the domain controller promotion tool (DCPromo) to change the computer role is not supported, and is known to break components such as Microsoft Outlook® Mobile Access.


h.. Running Exchange Server 2003 on a clustered node that is also an Active Directory domain controller is not supported and should never be done. This means that if you are running Exchange 2000 Server on a node in a cluster that is also a domain controller, you must demote the server to a member server prior to upgrading from Exchange 2000 Server to Exchange Server 2003.

Wobei der Aspekt des Restores dabei komplett aussen vorgelassen wird. Also dein Restorekonzept sollte dann schon getestet sein. ;)

Bye
Norbert

.

Relevant Pages

  • Re: Need upgrade help
    ... Microsoft Active Directory MVP ... > figuring out the best way to do all this upgrade. ... >> as well as the Exchange Admin news group. ... >> Server CD) on the Domain Controller that holds the fsmo role of Schema ...
    (microsoft.public.win2000.active_directory)
  • Re: Need upgrade help
    ... Microsoft Active Directory MVP ... > figuring out the best way to do all this upgrade. ... >> as well as the Exchange Admin news group. ... >> Server CD) on the Domain Controller that holds the fsmo role of Schema ...
    (microsoft.public.win2000.setup_deployment)
  • Re: Need upgrade help
    ... Microsoft Active Directory MVP ... > figuring out the best way to do all this upgrade. ... >> as well as the Exchange Admin news group. ... >> Server CD) on the Domain Controller that holds the fsmo role of Schema ...
    (microsoft.public.exchange2000.admin)
  • [NT] Vulnerability in Exchange Server Allows Remote Code Execution (MS05-021)
    ... A remote code execution vulnerability exists in Microsoft Exchange Server ... their choice in the security context of the SMTP service. ...
    (Securiteam)
  • RE: Catchall not working, EXTERNALLY?
    ... In the Microsoft Exchange Server box, type the local name of the ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
Loading