The configuration of Exchange 2000 resources relies primarily on the Active Directory and MMC snap-ins. Snap-ins for Exchange 2000 Server are added to the standard console when you install the Exchange 2000 Management utilities. Exchange 2000 also changes the Active Directory schema definition to include new classes and attributes, extend existing classes, and modify existing attribute definitions to support the configuration of the messaging system.
Exchange 2000 Server modifies a variety of directory attributes to include them in Global Catalog replication, such as the
class's givenName attribute. This is necessary to provide similar address book information to Outlook users, as in Exchange Server 5.5. For address list lookups, Outlook users connect to the computer running Exchange 2000 Server, where a specific process known as DSProxy intercepts the request and forwards it without modification to the Global Catalog server. DSProxy returns the results from the Global Catalog to the Outlook client as well. Smart MAPI-based
, such as Outlook 2000, can store referral information received from DSProxy in their messaging profile to subsequently contact the Global Catalog directly without the help of DSProxy.
MAPI-based clients communicate with Exchange 2000 Server using synchronous RPCs that can be carried over a variety of network protocols. In a Windows 2000/Active Directory/Exchange 2000 environment, communication via TCP/IP and Windows Sockets is preferred. Server-to-server communication, on the other hand, relies primarily on SMTP. Unlike previous versions of Exchange Server, Exchange 2000 Server does not utilize RPCs for server-to-server communication. Asynchronous SMTP offers more flexibility and independence from the underlying network than RPCs. Exchange 2000 Server extends the SMTP and NNTP services that ship with IIS 5.0 through event sinks to implement the required functionality for a top-class enterprise messaging and collaboration solution.
The following review questions can help you determine if you have sufficiently familiarized yourself with the material covered in this chapter. You can find the answers to these questions at the end of this book in Appendix A, "Questions and Answers."
After the installation of Exchange 2000 Server, you want to create new mailboxes for your
accounts. Which MMC snap-in would you use?
Recently, you have installed Exchange 2000 Server in your organization. Your organization is comprised of multiple domain trees arranged in a single forest. You intend to configure your mailbox resources from one of your computers. However, when you
the Active Directory Users and Computers snap-in, most of the Exchange-
property pages are not available. What do you have to install on the computer to configure mailboxes successfully?
Your organization has deployed Active Directory and organized its resources in OUs according to the structure of the enterprise. Names of OUs reflect the
of departments. Frequently, users move between departments. Consequently, it is necessary to move user accounts to the appropriate OUs as well. Do you need to delete the old user accounts and create new ones to reflect the organizational changes in Active Directory?
Active Directory holds all of the address information, such as the Global Address List, of Exchange 2000 Server. How does Exchange 2000 Server support MAPI-based client programs that are expecting to connect to an Exchange-based directory service?
In the past, your organization deployed Outlook 2000 successfully. Now you are installing Exchange 2000 Server. You wish to redirect your Outlook 2000
to a Global Catalog server. Outlook 2000 should contact the Global Catalog directly and without proxying. What do you have to configure on the computer running Exchange 2000 to achieve the desired result?
You plan to install Exchange 2000 Server in two locations connected to each other via a slow dial-up telephone connection. Do you need to upgrade the existing link to a permanent connection?