We recently upgraded our domain and in the process changed domain names. This
was a small office so it made sense for us to simply export the user's
outlook data in .pst files and import them under their new profile.

Since we did this, I have had a number of people reporting that when they
use the autocomplete function when typing in an email address the email is
not being delivered.
It seems that outlook fills in the Display Name such as "John Doe" but when
you mouse over the name there is no email address associated with it, just an
empty name.

On two of these users machines I have replaced the .n2k (nickname) file with
the one from their old profile. They are still having the same issues. Has
anyone seen this before?

Ryan Biddle wrote:

We recently upgraded our domain and in the process changed domain
names. This was a small office so it made sense for us to simply
export the user's outlook data in .pst files and import them under
their new profile.

Since we did this, I have had a number of people reporting that when
they use the autocomplete function when typing in an email address
the email is not being delivered.

Mail doesn't ever get delivered while you're still typing in the recipient
fields. You have to first resolve the addresses, then click Send before
messages will be delivered.

It seems that outlook fills in the Display Name such as "John Doe"

Does it get underlined at that point as well?

but when you mouse over the name there is no email address associated
with it, just an empty name.

No version of Outlook I can access at this moment will show the properties
of a resolved name in a compose window with nothing more than a mouse-over.
One must right-click and choose Properties.

There seems to be some discrepancies between what you describe and how
Outlook seems to work (at least for me). Can you be more precise about what
you're doing and what you see when?

On two of these users machines I have replaced the .n2k (nickname)
file with the one from their old profile. They are still having the
same issues.

I don't think the autocompletion cache has anything to do with what you're
seeing.
--
Brian Tillman