XADM: Hiding Address Book Views from Exchange Server Administrator and Clients During Address Book View Storms

If you create an Address Book view with multilevel containers, the directory service (or Dsamain process) on multiple servers may peak when the directory service populates these changes across your Exchange Server organization; you may experience slow connections, or there may be no connections at all to your Exchange Server computers during these Address Book view "storms."

This issue can occur because each Exchange Server computer builds the Address Book view based on Grouped by Attributes (GBA) that are replicated between sites and servers. If the Address Book views are poorly designed or frequently changed, the directory may use a large amount of the server's CPU to regenerate these views.

To resolve this problem, obtain the latest service pack for Exchange Server 5.5. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 4.

For additional information about the issue described in this article, click the article numbers below to view the articles in the Microsoft Knowledge Base: