sailci
asked on
Unable to access other mailboxes via OWA, Exchange 2013
I am in the middle of migrating from Exchange 2007 to Exchange 2013. I have moved the first pilot group over to 2013. I have full access to one of the mailbox including send-as, but when I try to access it via OWA it fails. I have tried two ways: 1. Type the full path i.e. my.domain.com/owa/share@do main.com and 2. Logging into OWA and myself and using the Open Another Mailbox option. Neither method works. Both yeild the same result: Something Went Wrong - Your Account Has Been Disabled.
I was expecting to be presented with a logon screen, but wasn't. I Thought the account in question was disabled, thats the way I normally set up non-user type mailboxes, but when I looked it is not disabled. So I can't figure out what to do, logs somewhere I am missing?
Also, another thing I am seeing is that 2013 can't access 2007 shared mailboxes either. When I type in the full path the the 2007 shared mailbox, it just gives me the box to click a link to open OWA. The address bar reflects the legacy namespace for 2007, but the tab reflects the Name on my 2013 mailbox. When I click the link it goes to the 2013 namespace and opens my OWA and not the 2007 shared mailbox I need.
I was expecting to be presented with a logon screen, but wasn't. I Thought the account in question was disabled, thats the way I normally set up non-user type mailboxes, but when I looked it is not disabled. So I can't figure out what to do, logs somewhere I am missing?
Also, another thing I am seeing is that 2013 can't access 2007 shared mailboxes either. When I type in the full path the the 2007 shared mailbox, it just gives me the box to click a link to open OWA. The address bar reflects the legacy namespace for 2007, but the tab reflects the Name on my 2013 mailbox. When I click the link it goes to the 2013 namespace and opens my OWA and not the 2007 shared mailbox I need.
Do you have a Full Access right on the share mailbox?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I am closing this out since it is just sitting here. Unfortunately, I was unable to resolve and have to just use a workaround. My end users are not going to be pleased once they are migrated over to Exchange 2013.
ASKER
I have included a workaround for one of the issues at hand. Unfortunately, no one out there has any other ideas.