Link to home
Start Free TrialLog in
Avatar of sailci
sailciFlag for Afghanistan

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@domain.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.
Avatar of suriyaehnop
suriyaehnop
Flag of Malaysia image

Do you have a Full Access right on the share mailbox?

You can use the following permissions with a shared mailbox.
Full Access   The Full Access permission lets a user log into the shared mailbox and act as the owner of that mailbox. While logged in, the user can create calendar items; read, view, delete, and change email messages; create tasks and calendar contacts. However, a user with Full Access permission can’t send email from the shared mailbox unless they also have Send As or Send on Behalf permission.
Send As   The Send As permission lets a user impersonate the shared mailbox when sending mail. For example, if Kweku logs into the shared mailbox Marketing Department and sends an email, it will look like the Marketing Department sent the email.
Send on Behalf   The Send on Behalf permission lets a user send email on behalf of the shared mailbox. For example, if John logs into the shared mailbox Reception Building 32 and sends an email, it look like the mail was sent by “John on behalf of Reception Building 32”. You can’t use the EAC to grant Send on Behalf permissions, you must use Set-Mailbox cmdlet with the GrantSendonBehalf parameter.
ASKER CERTIFIED SOLUTION
Avatar of sailci
sailci
Flag of Afghanistan image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of sailci

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.
Avatar of sailci

ASKER

I have included a workaround for one of the issues at hand. Unfortunately, no one out there has any other ideas.