Managing Full Mailbox Access from Exchange 2007 EMS and Exchange 2013 EAC ( Calendar access)

Managing Full Mailbox Access from Exchange 2007 EMS and Exchange 2013 EAC ( Calendar access)

  • Comments 3
  • Likes

As we all know that Exchange is evolving and new versions and new roll-up updates are releasing with new set of features, however there is still in need of co-existence between each versions.

co-existence between Exchange 2007 SP3 RU12 and Exchange 2013 SP1(In the event of amending mailbox user object from corresponding versions)

Basically while trying to provide Full mailbox access to an Exchange 2007 mailbox user via the Exchange admin centre (EAC) we may not be able to do that as it would fail with errors.

Here are the below scenarios for mailbox full access possibilities.

  • Exchange 2013 mailbox managing an Exchange 2013 mailbox is possible.

  • Exchange 2013 Mailbox managing a 2007 mailbox is possible

  • Exchange 2007 mailbox managing a 2007 mailbox is not possible

  • Exchange 2007 Mailbox managing a 2013 mailbox is not possible.

Basically you cannot administer a 2007 mail object from Exchange admin center likewise cannot manage a 2013 object from Exchange 2007 management console.

Below are the errors which are encountered during those scenarios.

From An Exchange admin center.

 From Exchange management console

  • Exchange 2013 mailbox object couldn’t be amended.

  • Exchange 2013 mailbox gaining full access to an Exchange 2007 mailbox is not supported and will fail with below error.

From Exchange management console.


From the above we can see the error.

 “Error on proxy command 'Add-MailboxPermission -Identity:'BrittaSimon' -User:'LITWAREINC\tcook' -AccessRights:'(FullAccess)' -InheritanceType:'All'' to server Server version 1912832083, Proxy method RPS: Connecting to remote server failed with the following error message : The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troubleshooting Help topic

The above error can be occurred because if The HTTP binding on the Default Web Site in Internet Information Services (IIS) is either missing or is invalid.

The below can be verified however that also will not resolve the issue.

    • Open IIS Manager, and then navigate to Default Web Site.
    • Right-click Default Web Site, and then click Edit Bindings.
    • If a binding exists for HTTP, clear the host name value.
    • If no binding exists for HTTP, create a new binding that has no host name and a value of All Unassigned for the IP address.
    • Restart IIS.

 Up on testing its confirmed that the following behavior is by design and it is expected to be resolved in Exchange 2013 CU5.

At the present moment it is not possible to manage a 2007 object or a 2013 object vice versa from different versions they could only be managed at their own versions which is a limitation.

Apart from the above there is another concern with calendar access.


When an Exchange 2013 mailbox is set with default rights on all the calendars to “Reviewer”, able to read Full details.


When using an Outlook 2013 client and login with a Exchange 2013 mailbox  accessing a 2007 mailbox is not possible when performing a right click on an Exchange 2007 mailbox user’s calendar and view the properties we get the following error.


From this same Outlook 2013 client, when trying to access a meeting in the Outlook 2007 person’s calendar in order to see the meeting details we get the following message

Using the same Exchange 2013 mailbox with the same Reviewer default access will allow without issues.

From Outlook 2010 Client:

We can see the properties of the same Exchange 2007 mailbox user’s calendar (confirming default rights of “Reviewer”)

When clicking on a meeting entry from that same 2007 user’s calendar the details are visible.

Using the same Exchange 2013 mailbox with the same default Reviewer access to everyone’s calendar.

From OWA client:

We wouldn’t be able to see the same meeting entry of the same Exchange 2007 mailbox user no specific error messages but the connection is not made and the calendar doesn’t open.

From testing it’s the same behavior basically accessing legacy user 2007 calendar is not possible via outlook 2013.

  • good one....

  • Very Helpful

  • Was this resolved with CU5? I'm seeing the same issue with CU8.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment