Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4716
  • Last Modified:

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.
0
sailci
Asked:
sailci
  • 3
1 Solution
 
suriyaehnopCommented:
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.
0
 
sailciAuthor Commented:
Let me clarify the issue as the response has nothing to do with the problem, I stated originally the permissions already existed. Hopefully this will be more clear:

The exchange environment is in a coexistant state between 2007 and 2013. I essentially have two issues so far.

Issue #1: User migrated from Exchange 2007 to Exchange 2013 cannot access other mailboxes using OWA; however access to those same mailboxes is fine using Outlook 2010 client. On the one "other" mailbox I am trying to access I get error - account has been disabled. This happens both when I try to connect to the mailbox from within my OWA session and when I try to connect to the mailbox by appending the url with the email address for that mailbox. In this test, both mailboxes (mine and the other) were migrated to Exchange 2013 (I will be testing other mailbox combinations after I get this working).

Issue #2: This is an issue with redirection from what I can tell. The user enters the owa url and appends it with the mailbox they want to access. From there it get redirected to the 2007 legacy namespace, but without the appended mailbox information. Thus the mailbox that opens in OWA is the user's mailbox and not the one they originally requested. I tested and if the user uses the legacy namespace url and appends that, it works fine. However, this is not what I was expecting behavior-wise.
0
 
sailciAuthor Commented:
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.
0
 
sailciAuthor Commented:
I have included a workaround for one of the issues at hand. Unfortunately, no one out there has any other ideas.
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now