So we have Exchange 2013 and Server 2012 R2 Remote collections setup. A user logs into the remote collection and can open outlook. If it's the first time they get the usual detecting account and everything works fine. But for one user, it just doesn't find his account. No matter if you enter it manually or automatically. It just can't see his account. I can type in another user's name and it pops right up.

So I figured I'd export his pst, disable the mailbox, create him a new mailbox and import the .pst.

Well that didn't work either. Should I go ahead and delete the User in AD? Then recreate it? I've already tested creating a new user and logging into outlook, importing his pst to the test user. So I know that would work. BUT is there anything left hanging after I delete the existing user(only been tested with a brand new user) from the Exchange Admin Console? Is it better to delete it directly in AD or from the exchange console?

Thank you.

I wouldn't delete the user.  Can you try running:

Get-CASMailbox user | select name, *OWA*

OWA was working fine.

These were the steps I just did to get it working with Outlook...

1. Backup .pst

2. Backup old UDP

3. Disable mailbox in exchange admin console

4. Deleted user in AD

5. Created new user/mailbox through exchange console

6. Verified outlook could login with the new user(same name as old)

7. Imported old pst

8. Mounted old UPD and copied over the few files he had.

9. Removed old UPD.

Everything is working fine now.

• Marked as answer by DCDeez Friday, January 30, 2015 7:35 PM