In general you don't want to do that because of the requirements of Exchange; it should be on a server by itself, not part of the domain controller.
-----------------------------------------------------------
There are some major reasons behind not installing Exchange Server on Domain Controller, some of them are as below.
01. Redundancy and Stability: If both of these are running on the same system, it may reduce the performance and stability of server. If in any case Exchange Server services fails, the whole DC will fail, which may create critical problems.
02. Port Conflict: Domain Controller & Exchange Server both uses port 389 for LDAP queries, which creates conflict.
03. Disaster & Recovery: Disaster & Recovery can not be performed.
04. DSAccess: DSAccess, DSProxy and many other services will perform well.
-----------------------------------------------------------
Global Catalog, Normal Domain Controller, and Configuration Domain Controller
NO, Exchange been designed for domain environment.
In network first server has been install is call domain controller server.. If you wan t to check server is domain controller or, backup domain controller. you can check Run -> cmd -> net accounts If computer role will show PRIMARY it means your domain is PRIYMARY domain controller, if it will be show BACKUP, means you can assume my domain installed in my network is ADC (Additional Domain Controller) Hope you will get benefit.. Regards, Ranjeet karak New Delhi
In network first server has been install is call domain controller server.. If you wan t to check server is domain controller or, backup domain controller. you can check Run -> cmd -> net accounts If computer role will show PRIMARY it means your domain is PRIYMARY domain controller, if it will be show BACKUP, means you can assume my domain installed in my network is ADC (Additional Domain Controller) Hope you will get benefit.. Regards, Ranjeet karak New Delhi
any group ar user who has domain admin rights can do it
Domain controller is the physical object.
A simple 2003 installed server in domain is known as the Member server. When we install AD on it then It becomes Domain Controller.
No, you do not. You only install Active Directory if the system is going to be a domain controller. If it is a member server or a standalone server Active Directory should not be installed.
Domain functional level of all domains at Windows 2000 Server or higherDomain controller with Active Directory running Windows Server 2003Stand-alone server (with Windows 2003 Server, .Net Framework 2.0, CD drive)Microsoft Exchange Server 2007
No the reason it's called a primary Domain Controller is because it's the one controller that has all the domain names and address for that Domain.
Domain controller
Domain controller