wrenmott
asked on
Cached Address Lists Causing NDRs after Cross-Forest Migration/x500 confusion
Hi all -
If you've been following I am in the middle of a 2010->2010 cross-forest move. Unfortunately, I have inherited migration that has been left in dissarray and I am forced to fight issues as they crop up.
Here's the latest:
We're dealing with source forest/org A & target forest/org B.
Once we migrate a user's mailbox from A to B using the prepmove scripts, etc., we then create a contact in the source forest/org so that users who have not been moved can still reach the user through the GAL. A kind of poor man's co-existence between the two infrastructure.
On that contact we paste the following assuming:
/o=sldc/ou=exchange administrative group (fydibohf23spdlt)/cn=recip
/o=african-minerals/ou=Exc
The first entry represents his old x500 address and the other one his new one. We have two problems:
1) Cached address in the NK2 file (or XML file) in Outlook 2010. When people who have already been moved and used the cahce address we get an NDR. ANyone know a way around this?
2) If I reply to an old email from him I get an NDR.
This is the error message:
<mailto:IMCEAEX-_O%3DConto
It's maddening because I don't fully understand what is giong on even though I am vaguely familiar with legacyDN stuff. Plus, we have 700 users to migrate and manually editing contact information is going to be a nightmare.
Can anyone shed some light on our issue or suggest a smarter way of doing this other than using Quest?
If you've been following I am in the middle of a 2010->2010 cross-forest move. Unfortunately, I have inherited migration that has been left in dissarray and I am forced to fight issues as they crop up.
Here's the latest:
We're dealing with source forest/org A & target forest/org B.
Once we migrate a user's mailbox from A to B using the prepmove scripts, etc., we then create a contact in the source forest/org so that users who have not been moved can still reach the user through the GAL. A kind of poor man's co-existence between the two infrastructure.
On that contact we paste the following assuming:
/o=sldc/ou=exchange administrative group (fydibohf23spdlt)/cn=recip
/o=african-minerals/ou=Exc
The first entry represents his old x500 address and the other one his new one. We have two problems:
1) Cached address in the NK2 file (or XML file) in Outlook 2010. When people who have already been moved and used the cahce address we get an NDR. ANyone know a way around this?
2) If I reply to an old email from him I get an NDR.
This is the error message:
<mailto:IMCEAEX-_O%3DConto
It's maddening because I don't fully understand what is giong on even though I am vaguely familiar with legacyDN stuff. Plus, we have 700 users to migrate and manually editing contact information is going to be a nightmare.
Can anyone shed some light on our issue or suggest a smarter way of doing this other than using Quest?
I don't think there is anything at the server end you can do, it is just an NK2 issue. You could also reset everyones NK2 by renaming the file with a group plicy but from experiece that could cause a war with your users.
Tony
Tony
In the past we have only had this issue on cmall clients so we have advised that they do not reply to old emails.
ASKER
Thanks, Tony. The tool does us no good as most users are in the mining fields in South Africa. :) Plus, there are hundreds. Politically, it will be nightmare, you are right. We may need to force delete them through GPO as you suggest. But in Outlook 2010 I don't think it is an NK2 file anymore is it?
it is a dat file in outlook 2010.
Looks like you can clear it with a switch though:
http://aspoc.net/archives/2010/05/04/how-to-clear-the-autocomplete-list-in-outlook-2010/
Method 2
1.Click Start, and then click Run.
2.Start Outlook by using the /CleanAutoCompleteCache switch.
For example: Outlook.exe /CleanAutoCompleteCache
Note If Outlook is not installed in the default location, you will need to point to the path of Outlook.exe.
http://aspoc.net/archives/2010/05/04/how-to-clear-the-autocomplete-list-in-outlook-2010/
Method 2
1.Click Start, and then click Run.
2.Start Outlook by using the /CleanAutoCompleteCache switch.
For example: Outlook.exe /CleanAutoCompleteCache
Note If Outlook is not installed in the default location, you will need to point to the path of Outlook.exe.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Thanks, Tony. That's brilliant. Definitely giving you some points.
However, I'd like to leave this open for a bit in case anyone has an idea of how we can get around it. For instance maybe there is another address we can add to the user object/mailbox or something simialr so that even the old cahced addresses get properly routed. There has to be a way. Or maybe not. Who knows?!
However, I'd like to leave this open for a bit in case anyone has an idea of how we can get around it. For instance maybe there is another address we can add to the user object/mailbox or something simialr so that even the old cahced addresses get properly routed. There has to be a way. Or maybe not. Who knows?!
As the incorrect path is actually held in the cache on the machine I don't think you will have any luck, but no problem, I would be very interested if someone can come up with a server level fix for this, as it would save me the same hassel every time we migrate a system.
cheers, Tony
cheers, Tony
ASKER
ah. I see what you mean. well, let's see.
So, you're focused on Exchange migrations? I may have some more questions for you later. :) If you have a sec check out my other posts. Its a tricky scenario in that we're dealing with VSAT links which absolutely kill us. Especially when OSTs start to regenerate.
So, you're focused on Exchange migrations? I may have some more questions for you later. :) If you have a sec check out my other posts. Its a tricky scenario in that we're dealing with VSAT links which absolutely kill us. Especially when OSTs start to regenerate.
ASKER
Solution for clearing Outlook cached addresses accepted.
Use this tool from nirsoft on each machine to clear the incorrect entries.
http://www.nirsoft.net/utils/outlook_nk2_autocomplete.html