- 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
- DS Referral
- Configuration of Diagnostic Logging
- Displaying Routing and Administrative Groups
How DSProxy Is Used
DSProxy makes requests to the GC server on behalf of the legacy client software. This transparent proxying allows the legacy client software access to AD information by using the Exchange server to proxy client software requests. The user can access the AD data without additional configuration to the legacy client software.
When Exchange 2000 starts up, the System Attendant (SA) process will discover the most suitable GC server in the domain using the Domain Name Services (DNS) resolver. The SA then registers its name with the DSProxy process. The DSProxy service uses this information to proxy legacy client requests to the GC that the SA found at startup. Microsoft may change this GC discovery method in favor of a load-balancing method for the final Release To Manufacturing (RTM) version of Exchange 2000.
RTMRelease to Manufacturing (a.k.a. Gold Code).
After the software code passes the Beta testing phase, it goes into a release candidate (RC) phase. After most of the kinks are worked out, the software code is frozen and released to manufacturing to become the final product.
The Recipient Update Service (RUS) is part of the Exchange System Attendant and is responsible for keeping Address Lists up to date and creating proxy addresses for users.
The server indicated as the MSExchangeSA source within Event Log ID 2059, is the Global Catalog server that was discovered by the SA. This information can be viewed by looking at the detail of a 2059 event from the Event Viewer.