Answer / sasidhar

It is a exchange process to communicate with AD

Answer / saif ali khan

Starting with Exchange Server 2000 Microsoft began using
the AD - Active Directory as the repository for Exchange
related data. So microsoft had to create certain rules to
make sure that the Exchange Server communiated with the AD
in such a way that it did not create excessive network
traffic or overwhelm domain controllers with too many LDAP
requests. ( For beginners i would like to explain this in a
little more detail - whenever Exchange would need any data
from the Active Directory it will use an LDAP query for
geting the data. Now all the data is present in the AD and
AD is present on DCs - that is Domain Controlers, hence
Exchange would be sending LDAP queries to DCs for the data.)
So for controlling the communication between
Exchange and AD; microsoft created a component called the
DS Access. DS Access would act as an intermediary between
the AD and Exchange Server.
Thus, DS is used by all the Exchange components
to query the AD and acquire the configuration and recipient
information. Example of the Exchange components that use DS
Access are Exchange System Attendant, Message Transfer
Agent and the Exchange information store.
DS Access is a generic name assigned to a group
of DLLs - DSAccess.dll, Dscmgs.dll and Dscperf.dll. These
are collectively called the DS Access or the DS access
cache. The DS Access cache is actually made up of two
seperate caches:

The Configuration Cache - The configuration cache is used
to store information pertaining to the configuration data,
including store and routing objects. It is set to 5 MB by
default.
When the system boots, DS Access initiates a
discovery process designed to identify the AD topology
(primarily related to the site structure), the domain
controllers, and which domain controllers act as global
catalog servers.
DS Access repeats the discovery process every 15
minutes to check for configuration changes and verify that
the known domain controllers are still available. Whenever
Exchange server needs to access a domain controller or a
global catalog server, it consults the DS Access cache to
determine which server is best fit for the job.

The User Object Cache - By default the Exchange Server sets
aside 140 MB for the user object cache, which stores user
object data. Objects within this cache are flushed when the
cache fills up or when the object's TTL expires. The
default TTL for the user object is 5 mins.
This user object cache is designed for preventing
excessive LDAP queries. When the Exchange server needs to
know something about a user, it checks the DS Access cache
first to see if the information is already stored there. If
the information is cached, then Exchange uses the cached
copy instead of issuing an LDAP query. If the required
information is not cached, Exchange has to retrieve the
necessary information from the DC via an LDAP query and it
stores the results in the DS Access cache.

Answer / imtiaz

DSAccess implements a directory access cache that stores
recently accessed information for a configurable length of
time. This reduces the number of queries made to global
catalog servers

Answer / raveesh katiyar

DSACCESS: Means also communicate with Acdive Directory in
Exchange Server

Answer / saif_ali_khan

Starting with Exchange Server 2000 Microsoft began using
the AD - Active Directory as the repository for Exchange
related data. So microsoft had to create certain rules to
make sure that the Exchange Server communiated with the AD
in such a way that it did not create excessive network
traffic or overwhelm domain controllers with too many LDAP
requests. ( For beginners i would like to explain this in a
little more detail - whenever Exchange would need any data
from the Active Directory it will use an LDAP query for
geting the data. Now all the data is present in the AD and
AD is present on DCs - that is Domain Controlers, hence
Exchange would be sending LDAP queries to DCs for the data.)
So for controlling the communication between
Exchange and AD; microsoft created a component called the
DS Access. DS Access would act as an intermediary between
the AD and Exchange Server.
Thus, DS is used by all the Exchange components
to query the AD and acquire the configuration and recipient
information. Example of the Exchange components that use DS
Access are Exchange System Attendant, Message Transfer
Agent and the Exchange information store.
DS Access is a generic name assigned to a group
of DLLs - DSAccess.dll, Dscmgs.dll and Dscperf.dll. These
are collectively called the DS Access or the DS access
cache. The DS Access cache is actually made up of two
seperate caches:

The Configuration Cache - The configuration cache is used
to store information pertaining to the configuration data,
including store and routing objects. It is set to 5 MB by
default.
When the system boots, DS Access initiates a
discovery process designed to identify the AD topology
(primarily related to the site structure), the domain
controllers, and which domain controllers act as global
catalog servers.
DS Access repeats the discovery process every 15
minutes to check for configuration changes and verify that
the known domain controllers are still available. Whenever
Exchange server needs to access a domain controller or a
global catalog server, it consults the DS Access cache to
determine which server is best fit for the job.

The User Object Cache - By default the Exchange Server sets
aside 140 MB for the user object cache, which stores user
object data. Objects within this cache are flushed when the
cache fills up or when the object's TTL expires. The
default TTL for the user object is 5 mins.
This user object cache is designed for preventing
excessive LDAP queries. When the Exchange server needs to
know something about a user, it checks the DS Access cache
first to see if the information is already stored there. If
the information is cached, then Exchange uses the cached
copy instead of issuing an LDAP query. If the required
information is not cached, Exchange has to retrieve the
necessary information from the DC via an LDAP query and it
stores the results in the DS Access cache.

Answer / mukram khan

DSAccess is a component that optimizes the communication
between Active Directory and components within exchange server.

Answer / mishri nishad

Its very simple answer is that when exchenge clients send
request to access his/her mailbox,tthat time exchange sent
cliets request for authentication to dc and for this it
maintains a dsaccess profile in which it maintains the name
of DC and GC server and according to this profile it sends
authentication request to clients nearest dc means dsaccess
is a process which works as bridge between exchnage server
and dc to pass AD releated query from exchange server to
Domain controller.

Answer / mukesh singh, isource

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. Note, though, that Global Address List (GAL)
lookups from Outlook clients do not use this cache.

It’s the System Attendant service that initializes
DSAccess, which comes in the form of a Dynamic Link Library
(DLL) file DSACCESS.DLL. In addition to DSACCESS.DLL there
are two other associated DLLs, DSCMGS.DLL and DSCPERF.DLL.
DSCMGS.DLL contains the information DSAccess uses to write
event log entries, whilst DSCPERF.DLL contains performance
object information.

To see which processes are using DSACCESS.DLL, you can use
TASKLIST.EXE (Windows 2003 and Windows XP) or TLIST.EXE
(older versions of Windows) for from a command line by
running the following command on your Exchange server:

tasklist –m dsaccess.dll

You should see output similar to that shown in Figure 1,
where you can see that processes such as the Information
Store (store.exe) and the System Attendant (mad.exe) are
using DSACCESS.DLL.

What ports does the exchange server use?

0 Answers  

How the mail flow occur in exchange server 2013?

0 Answers  

If there is still an m: drive mapped, why does the free space number look funny?

0 Answers  

Explain the term dag (data availability group)?

0 Answers  

What’s new in protection and compliance?

0 Answers  

Explain how do I verify oma is functioning?

0 Answers  

How can I upgrade my current exchange 2000 server or exchange server 2003 environment?

0 Answers  

What are the new adc tools?

0 Answers  

What are the exchange management tools who and where can you install them

2 Answers  

Why when I try to add an additional mailbox store do I receive the following error? This storage group already contains the maximum number of stores allowed. Idno: c1034a7a

0 Answers  

How message is delivered to the mailbox database in exchange 2013?

0 Answers  

Routing group ?

2 Answers   IBM,