"Spin" wrote:

> Experts,
>
> How can I increase the DSAccess timeout setting?  I know that DSAccess in
> Exchange 2003 keys on one specific GC, and if that GC is unavailable to it
> an event will be recorded in the application event log.  But how often does
> Exchange query DSAccess and can I increase the timeout value, if any?
>
> --
> Spin
>
>
>

"Tony Murray" <TonyMur***@discussions.microsoft.com> wrote in message
news:D423B45E-22AB-4C1B-8505-A75ADE8B828D@microsoft.com...
> Hi Spin
>
> Actually, DSAccess will use as many GCs are available within a site (up to
> 10) and will load balance between them.  It will use only one
> configuration
> DC for write activities.  This makes sense given that there is potential
> for
> replication conflict if writes are made to 2 different DCs.
>
> DSAccess will perform toplogy discovery every 15 minutes by default and
> when
> Exchange starts.  Additionally, if a DC or GC fails DSAccess will
> immediately
> remove it from the list of working DCs/GCs, rather than waiting for the
> remaining time with the 15 minutes.
>
> Topology discovery is different to the DSAccess cache.  For performance
> reasons DSAccess will cache information from LDAP queries to AD for a
> period
> of 15 minutes.  For example, if DSAccess looks up a recipient address for
> routing purposes it will hold the information for up to 15 minutes in case
> there are subsequent requests for the same address. This value is
> adjustable.
> For details on how to change the default have a look at the Technical
> Reference Guide
>
> http://www.microsoft.com/downloads/details.aspx?FamilyID=3768246D-C9ED-45D8-BECE-A666143CBA4E&displaylang=en