Article ID: 328799
Article Last Modified on 2/28/2007
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition
This article was previously published under Q328799
SUMMARY
Mailboxes and user accounts are represented differently in the Exchange Server 5.5 directory and in the Microsoft Windows 2000 Server Active Directory directory service. If your migration plan involves synchronizing the two directories with Active Directory Connector, first run the NTDSNoMatch tool to make sure that mailbox and user objects synchronize correctly.
MORE INFORMATION
In Exchange 2000, each mailbox is associated with a single Active Directory user account. In Exchange Server, multiple mailboxes can be associated with a user account, and multiple user accounts can share a common mailbox. This structural difference can make it difficult for Active Directory Connector to match Exchange Server mailboxes to Active Directory user accounts.
In Exchange Server, if multiple mailboxes are associated with a user account, the primary mailbox is the only correct match to an Active Directory user account. However, Active Directory Connector processes Exchange Server mailboxes alphabetically and might associate one of the resource mailboxes with the Active Directory user account. If you identify each resource mailbox by setting Custom Attribute 10 (which is located in the DS Site Configuration Custom Attributes properties) to NTDSNoMatch, Active Directory Connector does not match the mailbox to a user account; instead it represents the mailbox as a new disabled user account in Active Directory.
You may find it time consuming to manually identify resource mailboxes and to manually set Custom Attribute 10. You can automate this process by running NTDSNoMatch on your Exchange 2000 server. NTDSNoMatch identifies user accounts that have multiple mailboxes and determines whether a mailbox is the primary mailbox or a resource mailbox. For each Exchange Server site, it creates a comma-separated value (.csv) file that contains a list of the resource mailboxes that NTDSNoMatch identifies. You can import the .csv file directly into the Exchange Server directory to set Custom Attribute 10 to NTDSNoMatch for each resource mailbox in the list.
IMPORTANT: Make sure that the Exchange 2000 server on which you plan to run NTDSNoMatch has the latest service pack installed.
REFERENCES
For additional information about NTDSNoMatch, click the article number below to view the article in the Microsoft Knowledge Base:
280354 XADM: NTDSNoMatch Does Not Work with SID History
For additional information about using NTDSNoMatch, click the article number below to view the article in the Microsoft Knowledge Base:
274173 XADM: Documentation for the NTDSNoMatch Utility
Additional query words: NTDSNoMatch, csv
Keywords: kbinfo KB328799
