- 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
Architecture Similarities
Data access in Exchange 5.5 was MAPI-centric, meaning that the store was primarily optimized for MAPI clients. A similarity between Exchange 5.5 and 2000 is that the store process supports MAPI.
Database files are still used, but they can now be partitioned for flexibility and ease of recovery. The streaming file is a new feature that speeds up performance considerably by keeping objects in their native format while storing only header information in the Exchange Database (EDB) file.
The MTA Stack, X.400 Connector, and Offline Address Book (OAB) have been brought forward into Exchange 2000. With Exchange 2000, a server is still appointed to generate the OAB.
EDBExchange Data Base.
An instance of a database implemented in Exchange server. A single EDB is normally identified as being public or private depending on the type of data that it stores. Active Directory negates the need for the directory EDB, as AD now houses all directory information for Exchange.