Squan_JRP Posted April 9, 2015 Posted April 9, 2015 We moved a mailbox from exchange 2010 server to 2013 and now it is inaccessible to the user. When the user opens Outlook 2013, it gives the error that the Exchange Administrator has made a change that requires outlook to be restarted. This happens every time they open outlook, and despite saying it is "connected to exchange," it is not getting any new mail. When the user attempts to login to Outlook Web App, they get the error: "NegotiateSecurityContext failed with for host 'mail.domain.local' with status 'LogonDenied'. We migrated many users (even in the same batch as this one) and they are working fine. Any ideas what to look at here?
andydis Posted April 9, 2015 Posted April 9, 2015 Can you give the administrator or yourself full permission and open the mail box ? What's the size of the mailbox ?
Squan_JRP Posted April 9, 2015 Author Posted April 9, 2015 I gave myself full access rights to the mailbox and was able to open in through OWA (after logging in as myself). The mailbox is about 1.7 GB.
andydis Posted April 9, 2015 Posted April 9, 2015 Can y change the owner of the mailbox to another user and then give it back to the correct user ? , sounds like the link to the ad account or Sid is Brocken
Squan_JRP Posted April 10, 2015 Author Posted April 10, 2015 We actually migrated it back to the old (2010) database temporarily just to get it working again and it works fine now. Will try to migrate back to 2013 database (again) next week and we'll see what happens but will try that and let you know.
Squan_JRP Posted April 10, 2015 Author Posted April 10, 2015 We have another mailbox doing the same thing. What are the powershell cmdlets to see/change ownership of the mailbox?
Squan_JRP Posted April 11, 2015 Author Posted April 11, 2015 After seeing this in a few other mailbox, we realized it was happening to all of our "linked" mailboxes and not "user" mailboxes. The linked boxes had previously been moved to 2010 from 2007. We just needed to convert them to user mailboxes. The following did the trick, just using ADSI Edit on each of these accounts: delete the msExchMasterAccountSid set msExchRecipientTypeDetails=1
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now