Jump to content

Exchange problems and local users PST/NK2

Pydrex
Go to solution Solved by Pydrex,

Ok, I fixed this by adding the old x500 to the user on the Exchange server and internal users can now find the mailbox.

 

Strange

Hello LTT forums,

 

Over the last couple of days one of our admin accounts emails corrupted, luckly we had a backup of the .pst and imported all the email in and remade the exchange account.

 

The problem we have now is all of our users are on "Cached" mode (150+ users) meaning they're sitll getting the old link back to that email for example the username used to be support but now it is support3 so if a user emails support@ourdomain.com internally they get a bounce back, If we delete the NK2/PST (Using a Office 2003/2010 mix) then they can send email to the right user or if they select this user from the global book that will work too.

 

We have found if we email a user they can then reply and communication between the two partys will be fixed as the NK2/PST would have updated with the new path back.

 

Does anyone know of a way to force everyone to update to the newest paths? We have tried updating the GAB but that doesn't work as it is the stored email which drops down when you type "Sup" it suggests "support@ourdomain.com" but infact that is a old exchange string and doesn't have a way back.

 

 

If anyone has any idea's how we could resolve this without emails each user and getting them to reply.

 

 

Thanks

Link to comment
Share on other sites

Link to post
Share on other sites

IMCEAEX-_O=OURDOMAIN_OU=First+20administrative+20group_cn=recipients_cn=support@ourdomain.com

 

This route should be IMCEAEX-_O=OURDOMAIN_OU=First+20administrative+20group_cn=recipients_cn=support3@ourdomain.com as thats how the exchange string now has it.

Link to comment
Share on other sites

Link to post
Share on other sites

I have officially seen the first intimidating (to me) post on here... Unfortunately, I don't start my Windows Mail and Web Server course until Sept. 2nd, so I will be utterly useless for this issue until then... Congrats on making me a tad afraid of that course now though, lol.

"Any sufficiently advanced technology is indistinguishable from magic" - Arthur C. Clarke
Just because it may seem like magic, I'm not a wizard, just a nerd. I am fallible. 


Use the quote button or @<username> to reply to people | Mark solved troubleshooting topics as such, selecting the correct answer, and follow them to get replies!

Community Standards | Guides & Tutorials Troubleshooting Section

Link to comment
Share on other sites

Link to post
Share on other sites

Why don't you add an alias into exchange to do it? So even if they do email support, it's still routed to support3. This is how I would do it in exchange. Which exchange server you running?

System/Server Administrator - Networking - Storage - Virtualization - Scripting - Applications

Link to comment
Share on other sites

Link to post
Share on other sites

  • 1 month later...

Ok, I fixed this by adding the old x500 to the user on the Exchange server and internal users can now find the mailbox.

 

Strange

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×