Tip

Fixing mismatched Active Directory accounts

This tip was submitted to the SearchWin2000.com tip exchange by member Randy Brown. Please let other users know how useful it is by rating it below.

If you run an Exchange 2000 Server in a mixed mode environment (meaning you still have Exchange 5.x servers hanging around), you are likely to run into the problem of mismatched accounts at some point. A mismatched account happens when an Exchange 5.x mailbox gets 'tied' to an incorrect Active Directory account. Here are instructions on how to correct the mismatched account.

  1. Stop the Active Directory Connector. This is important because if you forget to do this, once you make the changes below, the ADC will likely do its job and re-match the account with the incorrect mailbox before you get a chance to complete all of the steps below. Another option is to set the replication schedule of the Connection Agreement that affects the mismatched user(s) to Never, but I think it's easier to just stop the ADC.
  2. Remove the Exchange attributes of the Active Directory user account. Do this from an Exchange 2000 Server that has Exchange Service Pack 2 or higher and has the AD Users and Computers MMC.
    --Open AD Users and Computers, click on View and choose Advanced Features.
    --Right-click on the user object that you want to fix and choose "Exchange Tasks." You may have to click Next if you get an informational message about this feature.
    --Choose the "Remove Exchange Attributes" option.

    Requires Free Membership to View

  1. After removing the Exchange Attributes from the user object, use ADSI Edit (from the Windows 2000 Resource Kit) to delete the msExchADCGlobalNames attribute from the affected user account(s).
  2. Open the Exchange 5.x Administrator application in raw mode (admin /r) and remove all values for the ADC-Global-Names attribute on the mismatched mailbox(es). To do this, you will need to select the mailbox and press +. This will open the raw properties of the mailbox. Scroll to the top of the object attributes list and select ADC-Global-Names. In the Attribute Values box select each attribute and remove it until there are no values remaining.
  3. Exit the raw mode Administrator program and open the Exchange 5.x Administrator program in normal mode. For each mailbox that you do not want matched to its associated Active Directory account, add NTDSNoMatch to the Custom Attribute 10 field (on the Custom Attributes tab) for the mailbox(es).
  4. Before restarting the ADC, be sure to allow some time for (or force) replication in your Exchange 5.x and Active Directory environments. Once you are certain that replication has occurred, you can precede to the last step.
  5. Restart the Active Directory Connector.

Once replication occurs, you should notice that the proper AD user account is now matched with the proper Exchange 5.x mailbox.

NOTE: Microsoft warns that using ADSI Edit and/or the Exchange 5.x Admin tool in raw mode can cause serious problems if used incorrectly. Use these tools at your own risk.

This was first published in October 2003

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.