| Author |
Message |
Guest
|
 Posted:
Thu Mar 10, 2005 1:03 am Post subject:
DSAccess and DSProxy |
|
|
According to best practices for large organizations, I would like to
establish a dedicated Windows site (with corresponding IP subnet) for
all my Exchange 2003 servers and it associated DC/GC. For Outlook
client address lookups, I would like to direct them to use other GCs
closer to their location.
It seems however that the GC specified for access via DSAccess is also
the same list of GCs used by DSProxy. The DSProxy, in essence, directs
MAPI clients where to go for lookups. Below is an excerpt from the
Exchange Technical Reference Manual.
Is there a way I can segregate the GC located on the same IP
subnet/Windows Site for use only by Exchange Servers and the other GC's
to be used by Outlook clients?
MAPI clients running Outlook 2002 Service Release 1 (SR-1) and earlier
versions use the proxy functionality. These earlier clients were
designed with the assumption that each Exchange server contains a
directory service. In Exchange Server 2003, this is no longer the case.
Therefore, DSProxy emulates a directory service, so that earlier
clients can function. In actuality, however, the Exchange Server 2003
server forwards the requests to Active Directory.
Later versions of Outlook, such as Outlook 2000 (SR-2 and later) and
Outlook 2002, are designed with the assumption that Exchange Server
2003 does not have its own directory service. After DSProxy refers one
of these later clients to a global catalog server, the client
communicates directly with Active Directory.
DSProxy obtains its list of working global catalog servers from
DSAccess, but it does not route its queries through DSAccess. This is
because DSProxy uses the Name Service Provider Interface (NSPI) to
submit MAPI address book lookups. DSAccess handles only LDAP queries.
However, DSProxy fully relies on DSAccess to provide global catalog
failover support
|
|
| Back to top |
|
 |
Kip Ng [MSFT]
Guest
|
| Posted:
Fri Mar 11, 2005 6:54 am Post subject:
Re: DSAccess and DSProxy |
|
|
This behavior occurs when the Exchange Server computer (where the Outlook
client is homed) and the global catalog server are both located in a site
that is remote from the Outlook client location.
Try looking at article 319206 to see how you can configure your Outlook to
locate closest GC.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
OR if you wish to include a script sample in your post please add "Use of
included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
<rambogjohn@netscape.net> wrote in message
news:1110395031.270108.314850@o13g2000cwo.googlegroups.com...
| Quote: | According to best practices for large organizations, I would like to
establish a dedicated Windows site (with corresponding IP subnet) for
all my Exchange 2003 servers and it associated DC/GC. For Outlook
client address lookups, I would like to direct them to use other GCs
closer to their location.
It seems however that the GC specified for access via DSAccess is also
the same list of GCs used by DSProxy. The DSProxy, in essence, directs
MAPI clients where to go for lookups. Below is an excerpt from the
Exchange Technical Reference Manual.
Is there a way I can segregate the GC located on the same IP
subnet/Windows Site for use only by Exchange Servers and the other GC's
to be used by Outlook clients?
MAPI clients running Outlook 2002 Service Release 1 (SR-1) and earlier
versions use the proxy functionality. These earlier clients were
designed with the assumption that each Exchange server contains a
directory service. In Exchange Server 2003, this is no longer the case.
Therefore, DSProxy emulates a directory service, so that earlier
clients can function. In actuality, however, the Exchange Server 2003
server forwards the requests to Active Directory.
Later versions of Outlook, such as Outlook 2000 (SR-2 and later) and
Outlook 2002, are designed with the assumption that Exchange Server
2003 does not have its own directory service. After DSProxy refers one
of these later clients to a global catalog server, the client
communicates directly with Active Directory.
DSProxy obtains its list of working global catalog servers from
DSAccess, but it does not route its queries through DSAccess. This is
because DSProxy uses the Name Service Provider Interface (NSPI) to
submit MAPI address book lookups. DSAccess handles only LDAP queries.
However, DSProxy fully relies on DSAccess to provide global catalog
failover support
|
|
|
| Back to top |
|
|
Al Mulnick
Guest
|
| Posted:
Fri Mar 11, 2005 7:04 am Post subject:
Re: DSAccess and DSProxy |
|
|
Yeah, that's one way to do it, but before you go that route, I think it's
important that you decide if that's worth it.
What I mean by that is that if your mail client is going to traverse the
network to get to the mail data, is address book lookup going to be that big
a deal in the scheme of things?
It might actually make more sense to deploy a dedicated site for Exchange
servers and put some GC's in there for the clients to also use vs. fiddling
with the registry key.
Al
"Kip Ng [MSFT]" <king@online.microsoft.com> wrote in message
news:%23h$xbTdJFHA.2648@TK2MSFTNGP14.phx.gbl...
| Quote: | This behavior occurs when the Exchange Server computer (where the Outlook
client is homed) and the global catalog server are both located in a site
that is remote from the Outlook client location.
Try looking at article 319206 to see how you can configure your Outlook to
locate closest GC.
--
This posting is provided "AS IS" with no warranties, and confers no
rights. OR if you wish to include a script sample in your post please add
"Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
rambogjohn@netscape.net> wrote in message
news:1110395031.270108.314850@o13g2000cwo.googlegroups.com...
According to best practices for large organizations, I would like to
establish a dedicated Windows site (with corresponding IP subnet) for
all my Exchange 2003 servers and it associated DC/GC. For Outlook
client address lookups, I would like to direct them to use other GCs
closer to their location.
It seems however that the GC specified for access via DSAccess is also
the same list of GCs used by DSProxy. The DSProxy, in essence, directs
MAPI clients where to go for lookups. Below is an excerpt from the
Exchange Technical Reference Manual.
Is there a way I can segregate the GC located on the same IP
subnet/Windows Site for use only by Exchange Servers and the other GC's
to be used by Outlook clients?
MAPI clients running Outlook 2002 Service Release 1 (SR-1) and earlier
versions use the proxy functionality. These earlier clients were
designed with the assumption that each Exchange server contains a
directory service. In Exchange Server 2003, this is no longer the case.
Therefore, DSProxy emulates a directory service, so that earlier
clients can function. In actuality, however, the Exchange Server 2003
server forwards the requests to Active Directory.
Later versions of Outlook, such as Outlook 2000 (SR-2 and later) and
Outlook 2002, are designed with the assumption that Exchange Server
2003 does not have its own directory service. After DSProxy refers one
of these later clients to a global catalog server, the client
communicates directly with Active Directory.
DSProxy obtains its list of working global catalog servers from
DSAccess, but it does not route its queries through DSAccess. This is
because DSProxy uses the Name Service Provider Interface (NSPI) to
submit MAPI address book lookups. DSAccess handles only LDAP queries.
However, DSProxy fully relies on DSAccess to provide global catalog
failover support
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in