NK2 files point to deleted AD accounts, instead of the new AD accts for users with a new name (marriage, etc).

When a user changes their name (marriage, etc), we try to keep things clean by creating a new AD acct with previous eml adrs added as secondary. But, NK2 files internally seem to point to the deleted AD account.  
Is there a way to mimick the old deleted account so that users can reply to emails addressed before the name/account change and so the NK2 file won't refer to the incorrect old deleted account? (perhaps by adding a secondary X400 adress?)
The problem only manifests for internal email, since the new account has the old email address listed as a secondary SMTP address.
Thanks!         Joel            
JHCompVerdeAsked:
Who is Participating?
 
ee_autoConnect With a Mentor Commented:
Question PAQ'd, 500 points refunded, and stored in the solution database.
0
 
gupnitCommented:
Hi,
WHy not just delete the NK2 file and let them recreate themselves
Thanks
Nitin
0
 
Exchange_GeekCommented:
It is simple, delete .nk2 files and have new ones created on their behalf - i know it sounds a bit odd for us to refer for deletion - but that is a trusted solution - definitely.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
JHCompVerdeAuthor Commented:
I'm with ya, deleting the old NK2, or just deleting the reference to the particular user as it pops up does the trick.  I'm just hoping there's a different solution that requires nothing from the users.  Something transparent to them would be great.
You know how it is, even if you send out an email notifying everyone in the company that a name has changed, and how to delete NK2 references to them, and that they now need to re-address previous email chains that they are replying to - you still get a dozen or more calls from people saying "My email to X is bouncing back?!"
If I can find a solution that doesn't include users, it would just all be smoother.
Thanks for your suggestions!  I'm hoping there's a different trick up someone's sleeve.
0
 
Exchange_GeekCommented:
Well, as i love to comment stating "look, when such accounts are deleted AD replication will help GAL remove such accounts" - i cannot.

When, there are hundreds of such cases which gets stacked day-in-day-out yelling what do i do when such issues takes place. So, easiest of all delete those files.

But, those are troubleshooting steps for affected guys not all. Some users might be able to sync correctly.

It is more of assuming the assumption, however no definite answers - if you find any please post. I am restricted until here. LOL
0
 
gupnitCommented:
Hi,
  • A suggestion, go ahead and use Group Policies with Script to remove the NK2 files from user profiles....that should be one way !
  • There is no way NK2 will get updated until and unless the users manually keep on using new accounts and that way in NK2 the old ones will go in order of preference, but thats it.
Hence the only way is delete....now objective has to think how to go about deleting NK2
Cheers
Nitin
 
0
 
JHCompVerdeAuthor Commented:
Looks like there aren't any other ideas for this issue.  It looks like with a name change, all other users must be notified that they'll have to delete the old address from the "To" filed popup (NK2 file), and if forwarding or replying to emails sent before the name change, to delete previous entry and retype the new one.

I was hoping there would be some way to take care of this where the users wouldn't have to do anything, but apparently there isn't such a solution.

If anyone comes up with one, please post it here.  Thanks!

Joel
0
 
JHCompVerdeAuthor Commented:
Unless I missed something, all the solutions offered so far revolve around deleting the users NK2 file so that it can be recreated with updated and correct addresses.  

This wouldn't work in my company because users have many contacts that are outside of the company and thus outside our GAL.  Our users would be upset if their NK2s were deleted to "update" them because the "outside" contacts would be lost in the NK2.  (They probably have the info in their contacts file, but often they don't.  File this in the "can't lead a horse to water" category, over reliance on the NK2).

Even though there I don't feel this thread has a solution that would work for my company, it might work for others.  Also, other people trying to find an answer to this question would at least benefit from finding that others have asked this question and basically found no solution.

I recommend saving this thread.  If I need to "accept" one of the above offered solutions to have the thread saved, please let me know.  Thanks...
0
 
gupnitCommented:
No you need not accept a solution just for the sake of it. Until and unless you feel the answers have helped you, there is no reason for you to do that.
Cheers
Nitin Gupta (gupnit)
0
 
gupnitCommented:
I just realised that you had closed the question and Exchange_Geek had objected to it. To be honest I would agree with Exchange_Geek that it is not about points, it is about appreciation an effort we put in.
Thought of letting you know
Thanks
Nitin
 
0
 
JHCompVerdeAuthor Commented:
I definitely appreciate all who have commented and devoted their time to giving me suggestions for how to solve my problem.  The solutions offered might not work for my case, but other people might find them useful.
This is the first question that I've posted, so I'm not familiar with how things go.  I'd be happy to assign points (however that gets done) to people who've contributed.  I just didn't want to "accept a solution" when it seemed like the very narrow question I asked had some answers, just not answers that would work in my situation as I (somewhat narrowly) defined it.
Nitin and Exchange_Geek, thanks very much for your help.  If NOBODY responded, I would still feel like there was some amazing solution out there waiting to be found.  Now I'm OK with the fact that when this sort of situation happens, scrapping users NK2 file is the easiest way to correct it, and when the user doesn't want to do that they just need to be instructed how to delete individual inaccurate listings.
Thanks everybody!  It's nice to throw a question out to the world and actually have people respond.  I appreciate it.  Cheers... Joel
0
 
gupnitCommented:
Sure Sure :-)
Cheers
Nitin Gupta (gupnit)
0
 
JHCompVerdeAuthor Commented:
Sounds fine to me.  Thanks everyone!
Joel
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.