0
There are many components within Exchange that require access to Active Directory services, such as the information store and the message categorizer. The DSAccess component optimizes the communication between these components and Active Directory.
The Exchange components that need to interact with Active Directory use DSAccess to retrieve Active Directory information rather than communicating directly with domain controllers and global catalog servers. As a result, DSAccess is therefore a very important part of Exchange. DSAccess is good for system performance, since it maintains a cache that effectively reduces the number of LDAP queries that these Exchange server components make to Active Directory. This is good for query speed as well as load reduction on both domain controllers and global catalog servers.
What else can I help you with?
What MS Exchange process is responsible for communication with AD?
DSACCESS-Directory access or dsa.msc
Why not install exchange on a domain controller?
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. -----------------------------------------------------------
