- Exchange's Core Components
- Design Goals
- Architecture Similarities
- Terminology Changes
- Architecture Changes
- Directory Services
- Directory Access
- How DSProxy Is Used
- How DS Referral Is Used
- Transport Services
- IIS Integration
- Distributed Configurations
- Addressing with Exchange 2000
- Address Generation
- Directory Connectivity
- Active Directory Connector (ADC)
- Site Replication Service
- Address Lists
- Accessing Filter Rules for Address Lists
- Configuring Filter Rules for Address Lists
- Active Directory Users and Computers
- Creating Users
- Creating Groups
- Creating Contacts
- Managing Users
- Managing Groups
- Managing Contacts
- Tools
- ADSIEDIT
- NTDSUTIL
- Troubleshooting
- DS Referral
- Configuration of Diagnostic Logging
- Displaying Routing and Administrative Groups
Directory Access
Legacy MAPI client software (prior to Outlook 2000) doesn't keep Directory Service location information in the messaging profile. Because of this, legacy client software will always look to the server that hosts the user's mailbox for directory lookups. This is not an issue if the Exchange 2000 server also happens to be a Global Catalog (GC) server. A normal lookup will occur because AD supports MAPI Directory Services (DS). DSProxy will handle the directory requests from legacy client software in the event that the Exchange 2000 server is not also a GC server. Client software requires access to the AD for Address Book lookup and name resolution.
DSProxyDirectory Services Proxy. DSProxy is used to query the active directory on behalf of legacy software clients. Outlook 2000 can maintain DS information and therefore does not use DSProxy.