The LegacyExchangeDN attributes for mail-enabled objects are incorrectly set in an environment that contains Exchange 2003 and Exchange 2007

In an environment that contains both Microsoft Exchange Server 2003 and Exchange Server 2007, an Exchange 2007 server provides mail attributes for a mail-enabled object. In this scenario, Exchange 2007 retrieves the available Administrative Group objects and puts them into an array. However, Exchange 2007 incorrectly selects the first Administrative Group object from the array when Exchange builds the legacyExchangeDN attribute.

Assume that you use the Transporter Suite tool to synchronize Free/Busy information. In this scenario, Exchange 2007 wants to retrieve the information for mail-enabled contacts. However, Exchange 2007 cannot use the legacyExchangeDN attribute to collect this information because the incorrect Administrative Group object was used to build the attribute.

To resolve this problem, install Update Rollup 7 for Exchange 2007 Service Pack 1. For more information about Update Rollup 7 for Exchange Server 2007 Service Pack 1, see the following Exchange Help topic: For more information about how to install the latest Exchange service pack or update rollup, see the following Exchange Help topic:Note After you apply the update rollup, the Exchange server queries the list of administrative groups and selects the Administrative Group (AG) object that contains a msExchDefaultAdminGroup attribute that is set to "TRUE." To change the msExchDefaultAdminGroup attribute to "TRUE" on the Exchange AG by using ADSIEDIT, follow these steps:

1. Open ADSIEDIT.
2. Drill down to locate the following container:
   CN=Administrative Groups,CN= <Organization name> ,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC= <domain name> ,DC=com
3. Check the msExchDefaultAdminGroup property on all the Administrative groups that are listed, and set the appropriate one to "TRUE."
4. Clear the attribute on all the other administrative groups that are listed.
5. Close the ADSIEDIT tool.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.