- 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
Exchange 2000 improves upon client access through the integration with Microsoft Internet Information Server (IIS). IIS supports the Internet protocols SMTP, POP3, IMAP4, NNTP, and HTTP-DAV for accessing Exchange data. The integration with IIS brings some exciting changes regarding data access. Exchange 2000 provides a new feature called the Web Store. The Web Store allows users to access Exchange data as messaging clients, from a Web server, or as a file system. These varied types of access give users a high level of flexibility and functionality.
It is through Exchange SMTP virtual servers that the various Internet protocols are serviced. The EXIPC layer (prerelease codename EPOXY layer) allows communication between these Internet protocols and Exchange. (See Figure 3.1.) Virtual servers run under the control of the IIS. The information about these virtual servers is stored in the IIS metabase. When a virtual server is created or changed using the Exchange System Manager (ESM), the Configuration NC is updated with this information. IIS is updated with the information about these Exchange virtual servers via a synchronization process between the Configuration NC and the IIS metabase.
Figure 3.1 Two main processes are in this diagram: the store and IIS. EXIPC is a queuing layer that enables the store and IIS processes to pass data quickly.
Separating the protocols from the database provides flexibility for future architectures.
Because of the synchronization process between the Configuration NC and the IIS metabase, it is imperative that the Exchange virtual SMTP servers only be modified from the ESM. Modification of the Exchange virtual servers from the IIS snap-in could produce heinous results.