- 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
Address lists are used to organize mail-enabled or mailbox-enabled AD objects into virtual containers that can be used by Outlook clients through the Address Book. One of the major improvements of Address Lists over Address Book Views (ABVs) is the significant increase in control. The administrator has much more control over the criteria used for an object's inclusion in an Address List. ABVs only allow the creation of virtual containers based on the data in certain fields of the object. If the data in these fields is not consistent, the result is numerous containers that are not very useful. ABVs expose every typographical error or standards inconsistency in the Exchange 5.x directory.
It is very important to have clean data in the Active Directory. Inconsistencies in Active Directory will result in inconsistency in the Address List queries.
Address Lists are assembled using LDAP search queries. These LDAP searches are used as the filter for inclusion of an object in the Address List's virtual container. The Address List Server is integrated with the System Attendant; its process can either be run manually or on a scheduled basis. The Address List Server updates an attribute called ShowInAddressBook with the name and location of the list of all the objects that were found by the query.
The nesting of Address List queries has no limit. This means that the user can have many different views of the hierarchy of Active Directory objects. An example of this is user objects that fit overlapping sets of LDAP query criteria. If a subset of user objects fits into an Accounting virtual container, these same objects can also fit into other virtual containers, such as Atlanta, Denver, and San Francisco.
The MMC snap-in Exchange System Manager is used to create, modify, and delete Address Lists. (See Figure 3.3.)
Subordinate Address Lists, residing below the main Accounting Address List, appear as an indented list below the main Accounting Address List when viewed from a messaging client, such as Outlook 2000.
Figure 3.3 Notice the hierarchical structure of the Address Lists. In this example, the main Accounting Address List's subordinate Address Lists are named after cities.
Right-clicking the All Address Lists causes a menu to appear.
From this menu, select New, and then select Address List.
After selecting New-Address List, the dialog box will appear, from which the new address list can be configured. (See Figure 3.4.)
Figure 3.4 Clicking Finish without setting any filter rules will result in a new, nonconfigured address list. Clicking Filter Rules will open the dialog box used to configure the filter rules.
Use right-clicks to open context menus for the individual objects. Just about any task to be performed can be done by right-clicking the correct object. Remember to try the right mouse button on every occasion.
It is possible to go back and create or change the filter rules after the Address List has been created.