Do you have 2 mailboxes with the same mailbox alias or LegacyExchangeDN. I get it quite often when there's a new hire with the same first initial last name combo. Two entries in our GAL their name would show, but their properties would be the legacy DN.
We had to change our policy on building new mailboxes to use a different format. (Department+Firstname+lastName). To fix, you need to change one of the duplicate users Mailbox alias (ADUC) and MSExchangeLegacyDN (in ADSI Edit) to the new Alias. It should look something like: /o=<site>/ou=First Administrative Group/cn=Recipients/cn=<alias> On Tue, Dec 1, 2009 at 10:55 AM, Jay Dale <[email protected]> wrote: > That did not help, so I’m Exmerging the mailbox and deleting/recreating > the user account to see if that makes a difference. > > > > Interestingly, while doing Exmerge, the mailbox showed up as the wrong > mailbox name, so that was probably the problem. Hopefully re-creation will > fix it. > > > > Thanks, > > > > Jay > > > > *From:* Chris Orovet [mailto:[email protected]] > *Sent:* Monday, November 30, 2009 2:28 PM > *To:* NT System Admin Issues > *Subject:* RE: Outlook does not recognize > > > > “C:\Documents and Settings\*your-profile*\Application > Data\Microsoft\Outlook” > > Delete or rename all **.nk2 *files at this location > > http://support.microsoft.com/?kbid=287623 > > > > then search for the user and see if it comes up. > > > > Regards, > > > > Chris Orovet Technical Support > > [image: ATSI] > O: (727)812-0276 Ext. 125 > > F: (727)812-0278 > > Email: *[email protected]* > > Web: *http://www.atsi-inc.com* > > * * > > * * > > “Whatever relationships you have attracted in your life at this moment, are > precisely the ones you need in your life at this moment. There is a hidden > meaning behind all events, and this hidden meaning is serving your own > evolution.” ~Chopra > > > > Confidentiality Notice: This e-mail message and any attachments are for the > sole use of the intended recipient and may contain proprietary, > confidential, trade secret or privileged information. Any unauthorized > review, use, disclosure, or distribution is prohibited and may be a > violation of law. If you are not the intended recipient or a person > responsible for delivering this message to an intended recipient, please > contact the sender by reply e-mail and destroy all copies of the original > message immediately. > > > > *From:* Jay Dale [mailto:[email protected]] > *Sent:* Wednesday, November 25, 2009 11:25 PM > *To:* NT System Admin Issues > *Subject:* RE: Outlook does not recognize > > > > I tried that, still came up. It brings up the Check Name, Microsoft > Office does not recognize and then gives the person's name as an option to > add. When I click on the name and choose Properties, it gives the following > LDAP query: > > > > /ou=Domain/o=Netbios name/cn=Recipients/cn=jsmith > > > > jsmith is nowhere to be found on either DC, in AD Find or in adsiedit. So > where does it keep bringing this up - in the OAB? > > > > Jay > > > ------------------------------ > > *From:* Benjamin Zachary - Lists > *Sent:* Tue 11/24/2009 10:10 PM > *To:* NT System Admin Issues > *Subject:* RE: Outlook does not recognize > > You may get this if you have hide the user from the organization checkbox > because when you goto setup the account outlook cannot find the username in > the GAL. > > > > What you can do is goto the user account, right click and exchange features > and remove all exchange attributes, this will orphan the mailbox. Then go > into exchange, drill down to mailboxes, do an update and you should see her > mailbox with an X on it, then right click and re-associate it with the user > > > > > > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
<<image001.jpg>>
