Outlook Nickname-Cache after new AD Domain
I have had to deal with this issue for a few smaller networks, but I now have to find a way to automate this issue as I am not about to do the same for 100 Users :)
We are setting up a new AD Domain, and manually migrating User Profiles, setting up new Exchange Mailboxes and importing in from Exmerged PST.
Outlook 2010 and Exchange 2010 is being used, and data is coming from Outlook 2003 and Exchange 2003. We will also be migrating Nickname-Cache into Outlook 2010.
Issue is that when a User goes to send to an internal User from their NK2 (Suggested Contacts) in Outlook they will receive a NDR as I believe the entry will be looking for old distinguished domain name or email address.
Is there a way I can ensure this does not occur? Like editing new AD User accounts to include legacy user accounts?
We are setting up a new AD Domain, and manually migrating User Profiles, setting up new Exchange Mailboxes and importing in from Exmerged PST.
Outlook 2010 and Exchange 2010 is being used, and data is coming from Outlook 2003 and Exchange 2003. We will also be migrating Nickname-Cache into Outlook 2010.
Issue is that when a User goes to send to an internal User from their NK2 (Suggested Contacts) in Outlook they will receive a NDR as I believe the entry will be looking for old distinguished domain name or email address.
Is there a way I can ensure this does not occur? Like editing new AD User accounts to include legacy user accounts?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
agonza07
Also make sure to delete the X400 entries. Those can be a pain too.
ASKER
But that means editing everyone's NK2 file? I can't afford to spend time doing that for every User.
Surely there is a way to use ADSI Edit and add legacy distinguished name in?
Surely there is a way to use ADSI Edit and add legacy distinguished name in?
Its got a command line so you can just set up a batch program or something. Just put it out as a GPO.
You can go ahead and edit everyone's account to include the old domain, but you are also going to have to add the X400 stuff too.
Here's a script to add an SMTP address to every account.
http://www.activedir.org/Articles/tabid/54/articleType/ArticleView/articleId/32/Default.aspx
You can go ahead and edit everyone's account to include the old domain, but you are also going to have to add the X400 stuff too.
Here's a script to add an SMTP address to every account.
http://www.activedir.org/Articles/tabid/54/articleType/ArticleView/articleId/32/Default.aspx
The problem with the nicknames files is going to be the old aliases. This article from the SBS team explains the problem and a solution quite clearly:
http://blogs.technet.com/sbs/archive/2009/05/21/cannot-reply-to-old-emails-or-modify-old-calendar-items-after-pst-mail-migration.aspx
Simon.
http://blogs.technet.com/sbs/archive/2009/05/21/cannot-reply-to-old-emails-or-modify-old-calendar-items-after-pst-mail-migration.aspx
Simon.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Awesome feedback all .... I went ahead with a script with nk2edit which has saved me a lot of time. I think admodify would be best to use next time round though.
Just be careful with old emails and if people reply to them. They will not go through and come back as NDRs because they will have X500 references that came from you Exchange 2003 setup.
ASKER
Ah yes of course ...... can you give me some more information around what is required with ADMod to update new AD Users?
Exactly what Sembee2's link shows.