OWA Error after Exchange 2010 Mailbox move to 2013

Hello,
We have been experiencing an issue when we move a users mailbox from Exchange 2010 on-prem to Exchange 2013 on-prem. As a domain admin I was able to access the users mailbox via OWA 2010 with out issues. However, now that they have been
moved over to 2013 I am getting the following error message:
X-OWA-Error: SDServerErr;Microsoft.Exchange.Data.Storage.AccessDeniedException
X-OWA-Version: 15.0.995.28
X-FEServer: CASServer
X-BEServer: Mailboxserver.domain.com
Date: 1/29/2015 5:27:38 PM
Full Access permissions appear on the mailbox still via the 2013 ECP console for my account. I have tried running the
Set-Mailbox UserName -ApplyMandatoryProperties command but receive a message that no settings have been modified.
I have also tried to remove/re-add inheritable permissions on the users AD account to no avail.
I have a large group of mailboxes to move over to 2013 and hoping their is a decent solution out there to prevent this from happening.
Greatly appreciate any feedback on this request.
Cheers

Hi,
Please re-add the full access permission for the administrator:
Get-Exchange Server "servername" | Get-Mailbox | Add-MailboxPermission -User Administrator -AccessRights FullAccess
If Administrator is still located in Exchange 2010 and has the full access permission to an Exchange 2013 mailbox ([email protected]) which is moved from Exchange 2010, please use the following URL to open the mailbox:
https://Exch13.domain.com/owa/[email protected]/
Then check whether the issue persists.
Regards,
Winnie Liang
TechNet Community Support

Similar Messages

Exchange 2010 mailbox moves get stalled

I am Experiencing an issue with Exchange 2010 SP3 UR2 two node DAG environment (server01 and server02). While moving mailboxes from old Exchange 2007 environment I get following errors.
Move for mailbox xxxxxxxxxxxx is stalled because DataMoveReplicationConstraint is not satisfied for the database 'MDB01' (agent MailboxDatabaseReplication). Failure Reason: Database does not satisfy constraint SecondCopy. Throttling completion as database copies
are falling behind.
Get-MailboxDatabaseCopyStatus informs me that server02 Copy and ReplayQueue length on the passive copy are getting big (from 10-500) while moving and the throttling will always pause the move for a while and then start again until it stops again because the
second copy is falling behind. This only happens when I move mailboxes to databases that have active copy of the database on my server01 and passive on server 02. If the active copy is moved to server02 and server01 is the passive copy this does not happen.
So this leads to a conclusion that there is something wrong with server02 replication from server01.
I've traced the replication network and there are no issues. What could be the reason that only the second node suffers from falling back during moves? I would not like to se the datamovereplicationconstraint value to none since this is the only Exhchange
2010 DAG environment where I am facing this issue and the replication should keep up while mailbox moves.

Hello,
" I would not like to see the datamovereplicationconstraint value to none". Do you mean you set
DataMoveReplicationConstraint to SecondCopy? If so, I recommend you use test-replicationhealth cmdlet to check all aspects of the replication and replay status.
Please check if you
configure a lagged database copy.
Please check if there is a witness server, and whether the witness is online.
If not, please set DataMoveReplicationConstraint to SecondCopy.
Besides, please check if there is any error in application log.
Here are some articles for your reference.
http://technet.microsoft.com/en-us/library/dd335158(v=exchg.150).aspx
http://blogs.technet.com/b/exchange/archive/2011/05/06/exchange-2010-mailbox-moves-and-mailbox-resiliency.aspx
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Exchange 2010 Mailbox move issue

Hi
I have moved around 100 mailboxes from DB to other DB in the same server.
Now all these mailboxes are in Disconnected state.
The problem is, these mailboxes are appearing twice under disconnected mailbox window. One is from old db and other is from New DB.
The reason for the same shows for Old DB is Soft Deleted and for new DB is Disabled.
IS this a general behaviour? Currently when the user access the mailbox, it says its locked for moving.
How can renable these mailboxes and make user accessible? Do i need to wait till retention period over?
I have set the deleted mailboxes rentention to 2 days. Will this make mailboxes active after 2 days?
regards Sundaresan.C

Yes this is general behavour; Soft Deleted mailboxes - introduced in Exchange 2010 SP1
more info can be found here; http://technet.microsoft.com/en-us/library/dd298174(v=exchg.141).aspx
This example purges the soft-deleted mailbox for Phil from mailbox database MBD01.
Remove-StoreMailbox -Database MBD01 -Identity Phil -MailboxState SoftDeleted

Exchange 2010 Mailbox move error - Property Expression "Jim Smith" Isn't vaild - FQE=A169C2C1

I have moved 120 mailboxes from our exhange 2003 server to the new 2010 Exchange server
Only this ONE account is having this issue - we have checked the account and it seems normal - no strange formats for alias
I have Searched all over - and have found NO results for this kind of error
Have tried moving with the GUI and Shell
Here is the complete error
Error:
Property expression "Jim Smith" isn't valid. Valid values are: Strings formed with characters from A to Z (uppercase or lowercase), digits from 0 to 9, !, #, $, %, &, ', *, +, -, /, =, ?, ^, _, `, {, |, } or ~. One or more periods may be embedded in an alias, but each period should be preceded and followed by at least one of the other characters. Unicode characters from U+00A1 to U+00FF are also valid in an alias, but they will be mapped to a best-fit US-ASCII string in the e-mail address, which is generated from such an alias.
Exchange Management Shell command attempted:
'www.nerc.net/Jim Smith' | New-MoveRequest -TargetDatabase 'Database Two'
Elapsed Time: 00:00:00
FullyQualifiedErrorId - A169C2C1

Hi, I found myself in the same situation.
I didn't have to use ADSIedit, I simply used the AD Users and Computers on the Exchange 2003 Server to correct the error.
Right-Click on the user whose mailbox is displaying error - Go into properties and select "EXCHANGE GENERAL" tab - modify the "ALIAS" - click Apply.
I used hyphen to bridge the space. After that all the mailboxes affected moved with any problem.
That should do it.

Exchange 2010 mailbox prompts for authentication to Exchange 2013 mailbox

I am in the process of a 2010 to 2013 migration. The only issue I can't seem to manage is an authentication issue with Outlook 2010. My Outlook profile consists of my Exchange 2013 mailbox and a shared mailbox on Exchange 2010. Initially, Outlook was prompting
for authentication to the Exchange 2010 mailbox. Regardless of whether I entered the correct credentials or simply cancelled the prompt, I still had full access to both mailboxes (including Public Folders on 2010). The authentication prompt was removed with
the following command:
Get-OutlookAnywhere -Server my2013exchserver | Set-OutlookAnywhere -InternalClientsRequireSsl $true
The second issue I now have is the reverse of the above: an Exchange 2010 user is prompted for authentication to an Exchange 2013 mailbox. How do I begin to troubleshoot this problem - should I run the same command (above) on 2010? I don't quite understand
how Outlook communicates with Exchange but I am thinking there is an incorrect setting on one of the Virtual Directories(?).
Many thanks.

Hi Dennis,
Please open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar –Connection Status to check the connection for your Exchange 2010 mailbox with shared 2013 mailbox. The following example in my test results:
Please check your connection authentication. We can run the following command to set your Outlook Anywhere for Exchange 2013:
Set-OutlookAnywhere -Identity "E15-01\Rpc (Default Web Site)" -InternalClientAuthenticationMethod Ntlm -ExternalClientAuthenticationMethod Basic -ExternalClientsRequireSsl $True -InternalClientsRequireSsl $true
In Outlook side, please ensure the following settings in Account Settings:
In Security tab, make sure Always prompt for logon credentials is unchecked and Logon network security is set to Negotiate Authentication.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2010 Mailbox automapping issues after updated to Rollup 5 for Exchange Server 2010 SP3

Hi,
i have problem with Outlook Uses who have Full Access on other mailbox.
An authentication window pop up very time a user start Outlook.
If i remove the access everything is ok.
if i insert manual the mailbox everything is ok
The System was for 3 days ago updated to Rollup 5 for Exchange Server 2010 SP3
Before the update, was no issue.
i will appreciated any help
Thanks

Same issue here. Ever since we installed Update Rollup 5 for SP3 Exchange 2010 mailboxes that were auto mapped are not accessible. They all get the same error.
Cannot expand the folder. The set of folders cannot be opened. The attempt to log on to the Microsoft Exchange has failed.
What I have been doing is removing the users permission, then adding them back using the noautomap switch in Powershell. After doing that, the user manually adds the mailbox and all is well.
Just a note here, I suspect it may have something to do with the version of Outlook 2010. We are running an older version here. I think only SP1 with no other incremental updates. Office is up to SP2. Also, one of the users I was working with could not access
the mailbox no matter what we tried but she can walk over to another workstation and open Outlook and access the very same mailbox so that pretty much proves its software related particularly with Outlook.
I cannot reproduce the problem on a workstation (XP) with a newer version of Outlook.
This has been wearing me out and I suspected the Update Rollup all long. Now I am confident as others are having the same problem. If you find out anything on how to fix this other than the steps above, let me know.

Exchange 2013 / 2010 co-existence - Outlook won't connect to Exchange 2010 mailboxes

Greetings! I have a lab set up at home where I have been testing co-existence of Exchange 2013 and 2010 for a future corporate upgrade project.
I am running into some odd behavior. Any mailbox that has been migrated to Exchange 2013 works just fine, however, when I try to set up Outlook for a mailbox still on Exchange 2010 I receive errors. OWA works just fine for these Exchange
2010 mailboxes, it is just Outlook that has the problem. This is what I am running into:
1. Outlook uses autodiscover to locate server settings. It fails at the 'logging on to mail server' step saying that Exchange isn't available; Outlook must be connected, etc.
2. It then gives me the settings box for Exchange server and Mailbox. This is auto populated with one of the Exchange 2013 servers (there are 3 of them, all have both MBX and CAS role). If I then change the server to the Exchange 2010 CAS server,
and hit 'check names', it underlines the very same entries (like it found them this time) that were there initially and goes on to finish the configuration.
3. When I launch Outlook with this Exchange 2010 user, it fails to open with the error message that the set of folders couldn't be opened.
I've been doing as much research on this as I can. I've tried disabling IPv6 to no avail. It seems as if perhaps the issue is with Exchange 2013 proxying the request back to the Exchange 2010 servers but I am not sure what to check in that regards.
Any suggestions? Thanks in advance!

Hi,
Don´t disable IPV6 on an Exchange Server, it is, in my opinion not necessary - also applies for AD.
You can use your original SSL Cert for your new Ex 2013 environment.
In dns you want two host A records: mail.domain.com and autodiscover.domain.com
On your 2013 set your internal and external virtual directories to mail.domain.com
leave autodiscover and Powershell alone.
Also set the autodiscover URI to your Certificate name ie. mail.domain.com
Set-ClientAccessServer -Identity "YourCASServer" -AutoDiscoverServiceInternalUri "https://mail.domain.com/autodiscover/autodiscover.xml"
Thanks. I wanted to give some additional info before I run any commands. I currently have an A record for autodiscover and it is pointed to the Exchange 2013 DAG/cluster IP. I have a 3 entries for mail.domain, for DNS round robin; basically
it is listed 3 times for the IP of each of my Exchange 2013 servers. Does any of this sound problematic?

Moving Exchange 2010 Mailbox replicated databases path in DAG environments.

Hi there,
I’m trying to get some feedback on the topic of moving Exchange 2010 Mailbox replicated databases path in DAG environments.
Here is the situation: I currently have a 3-Node DAG (Node 1 and Node 2 are in my main datacenter, and Node 3 in my Disaster Recovery (DR) site in a remote location.
I have DB copies in Node 2 and Node 3. The thing is that the DB copies in Node 2 are in an older storage box and since we got a new storage box, I need to move the DBs and related logs of Node 2 to the new storage box
I have found some information about how to deal with this (below I’m listing a KB link) but I would like to reconfirm a couple of things to make sure I’m understanding this correctly
Move the Mailbox Database Path for a Mailbox Database Copy:
https://technet.microsoft.com/en-us/library/dd979782%28v=exchg.141%29.aspx
According to the KB: “If the mailbox database being moved is replicated to one or more mailbox database copies, you must follow the procedure in this topic to move the mailbox
database path”
Would this apply to my case even when I’m moving the BDs copies and Logs on Node 2 as opposed to Node 1 where the source DBs are?
On step #3 in the procedure, you are supposed to “Remove all mailbox database copies for the database being moved. After all copies are removed, preserve the database and transaction log files from each server from which the database copy is being removed
by moving them to another location. These files are being preserved so the database copies do not require re-seeding after they have been re-added.”
Then in Step # 7, you are supposed to “Add all of the database copies that were removed in Step #3”
As far as I know, when you add a copy of a database, Exchange creates the copy DB and starts to seed the replica servers with an up to date copy of the DB and all the current transaction logs at that point…according to the instructions
above, you are supposed to re-add the DB copied we preserved...does it mean that we need to wait for the DBs seed process to finish after “adding the DB copy” and then replace the new DBs copies and logs created by the “Add database copy” function with the
DB and logs preserved in Step #3?
Thanks in advance for your feedback!
FT
FT

Hi there,
What the article is stating is that once you have removed the copies you can keep the existing transaction log files and database edb file to allow you not to have to do a full seed. You can do this by using the -seedingpostponed parameter in
Add-MailboxDatabaseCopy
However, and quite honestly, if your database isn't that big and your are not worried about performing a full copy of the database again to the other DAG members once you have moved your database to its preferred new location, just add the copy in the normal
way and remove the legacy files afterwards.
Oliver Moazzezi | Exchange MVP, MCSA:M, MCITP:Exchange 2010,Exchange 2013, BA (Hons) Anim | http://www.exchange2010.com | http://www.cobweb.com | http://twitter.com/OliverMoazzezi

Relay issue from Unix across Exchange 2003 OWA server in Exchange 2010 environment

Hi,
I'm trying to resolve an issue. We have one Exchange 2003 server left in our environment. The rest is now Exchange 2010. We are working to decommission this server. Monitoring the SMTP logs, I am working with the various groups to get the traffic
off this server and onto the Exchange 2010 environment.
The issue we are finding is with a work flow. This Java app for eBis sends email to users. This is done correctly through Exchange 2010 and gets delivered from our HUB/CAS servers to the target user mailbox. This email has several links the user must click
for approving or rejecting requests. Upon clicking Approve, a new email window opens (we use Outlook 2010). The TO address is in the format of [email protected] Upon clicking Send, our Exchange 2010 HUB/CAS servers accept the
email, because one of our send connectors has, as address space, *.domain.corp. However, the email address being used it not an alias on any Exchange 2010 mailbox, so it appears Exchange 2010 is sending this email on to the Exchange 2003 server, which
also is an SMTP server. I *think* this server is looking at the address after @ to determine where to send it (ebisserver.domain.corp, which is valid in our DNS), and sends it on to that server, where the java "listener" program intercepts
the mail, processes it and then saves it to a file somewhere.
We are at a loss as to how to get Exchange 2010 to do this instead of Exchange 2003... once this traffic is eliminted from Exchange 2003, I can proceed with decommission of this server. Any help troubleshooting this issue is appreciated.

The only reason the Exchange 2010 server would route outbound mail through an Exchange 2003 server is that you have an SMTP Connector defined on the Exchange 2003 server that has a more specific domain than you have on the Exchange 2010 server. You
should be able to see all your Send Connectors (an SMTP Connector on Exchange 2003 looks like a Send Connector in Exchange 2010) by running Get-SendConnector.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Outlook 2007 Clients Cannot Access Free/Busy Calendar info. for Exchange 2010 Mailbox

Hi:
I have Outlook 2007 clients that cannot access Free/Busy Calendar info. for Exchange 2010 mailboxes. They receive error like "...you do not have appropriate permissions..."
If those same users logon to a machine running Outlook 2010 then they can view the free/busy info. of the other user's mailbox, so I believe the permissions are set correctly on the mailbox to allow the viewing.
Any insights are greatly appreciated!
Thank you!
Bob Herman IT Tropolis

Hi Herman,
As you said, it seems users have proper permissions on mailbox.
Please make sure users has Reviewer permission on Outlook 2007.
Please try to run Outlook 2007 under safe mode or re-create profile.
Also try to turn Outlook 2007 to Exchange Online mode from Cached mode.
Thanks
Mavis Huang
TechNet Community Support

Auto-Mapping Exchange 2013 Mailboxs in an Exchange 2010 Mailbox

We're in the middle of migrating mailboxes from Exchange 2010 to Exchange 2013. Many of our users have Auto-Mapped mailboxes as well. In my testing, I've found that I cannot Auto-Map a mailbox that's on Exchange 2013 in a Exchange 2010 mailbox. I can manually
add it and it works fine. Is this by design with this type of coexistence or is there a fix for it? Our current Exchange 2010 environment is at SP3 with UR2.
Orange County District Attorney

This issues is fixed in UR5 so suggest you to upgrade Exchange 2010 to SP3 UR5.
Reference Thread: http://social.technet.microsoft.com/Forums/exchange/en-US/a2aa4163-f74b-401f-aec5-13324e6b29c8/exchange-2010-mailbox-not-able-to-access-automapped-exchange-2013-cu3-mailbox?forum=exchangesvradmin
Blog |
Get Your Exchange Powershell Tip of the Day from here

How to monitor particular individual Exchange 2010 mailbox

Hi
Is it possible to monitor a particular individual Exchange 2010 mailbox? If so please send me the script or steps to to accomplish this
Donald D'souza (http://donald-scom.blogspot.com/)

The Exchange 2010 MP has had some issues of late and is once again unavailable. Hopefully this should be rectified soon. Keep an eye on the Management Pack forum and someone should post there once it is back.
I appreciate the Exchange team are looking for ways to get extra monitoring from SCOM and I'm certainly not saying you can't do mailbox monitoring with SCOM. I'm just saying be careful. I have seen one enterprise write a discovery to discover the
mailboxes they wanted to monitor. The discovery captured data that changed every iteration that the discovery ran. They then wondered why SCOM stopped working, ignoring the fact that they had discovered thousands of objects whose properties changed every
time discovery ran, causing huge numbers of state change events and massive database growth.
If you are looking for in-depth exchange mailbox monitoring then SCOM is not the tool for it. Quest and Sirana do dedicated enterprise tools. If you take a look at the links and say that is what your team want then I'd suggest evaluating those
products. Developing SCOM to deliver that would not be cost efficient.
Hope you don't mind but I'll ask again - what specifically do you want to monitor? Mailbox Size? Number of emails sent \ received? size of message sent? destination? number of attachments? size of attachments? blocked messages? If you need deep detail
along the lines of the following then you really need to evaluate the following:
http://www.sirana.com/exchange/reporting
If you end up writing scripts to do all the above then you will likely severely impact performance of either SCOM or your Exchange server or possibly both.
Sadly (for budgeting) SCOM doesn't necessarily replace specialist tools - it just complements them. Likewise, if you want deep dive SQL then you'll still need Quest or Idera based tools. Probably fewer licenses and better targetted at servers with known
issues.
Cheers
Graham
Regards Graham New System Center 2012 Blog! -
http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/

Unable to remove orpahned Exchange 2010 mailbox databse server permantely offline

Greetings,
I am having great problems removing and Exchange 2010 mailbox Database, the server that the database resided upon is permanently offline and gone,
Under Organization Configuration / mailbox
The orphaned database is listed there however I cannot delete it under Database Copies a copy of the orphaned database is listed as offline.
How can I remove this database if the server is offline?

run ADSIEDIT.msc
Select Configuration well-known naming configuration -> CN=Configuration -> CN=Services -> CN=Microsoft Exchange -> CN=<YourExchOrgName> -> CN=Administrative Group -> CN=Exchange Administrative
Group (FYDIBOHF23SPDLT) -> CN=Servers > CN=Databases -> Select Exchange 2010 database name and delete
MCP, MCSE 2000 , MCSA 2000 ,MCSA 2003 , MCITP , MCTS , MCT

Is it possible to monitor a particular Exchange 2010 mailbox via SCOM if 30 or more emails trigger in 30 minutes in the inbox and alert should be generated

Is it possible to monitor a particular Exchange 2010 mailbox via SCOM if 30 or more emails trigger in 30 minutes in the inbox and alert should be generated for that.
If this is not possible in SCOM. Is there another way we can do it via power shell or any thing.
Gautam.75801

Hi,
We may need to create script based rule using PowerShell or VBScript.
Please go through the below links for command get-mailboxstatistics:
Exchange 2010 : http://community.spiceworks.com/topic/122241-scripting-to-count-all-of-the-messages-in-a-mailbox
Regards, Yan Li

Exchange 07 to 13 OWA Error after mailbox move.

I have an Exchange 2007 – Exchange 2013 Sp1 environment set up and coexistence is working properly. The issue I am seeing is sometimes when we do a migration from 07 to 2013 sporadic users cannot access OWA on 2013, they get an error..
X-OWA-Error: ClientError;exMsg=_u is not defined;file=_y.$LE@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.1.mouse.js:1:155BootViewModelsComponent.prototype.$1XA/<@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.1.mouse.js:1:305920_js.$Zn.prototype.$8J@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:60174_js.$Zn.prototype.$E@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:59797$4pj@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:57816_js.$2.prototype.$6JC@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:58309BootViewModelsComponent.prototype.$1XA/<@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.1.mouse.js:1:306788_js.$Zn.prototype.$8J@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:60174_js.$Zn.prototype.$E@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:59797$4pj@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:57816_js.$2.prototype.$6JC@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:58309ApplicationAppComponent.prototype.$1XA/r<@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.1.mouse.js:1:1141362_js.$Zn.prototype.$8J@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:60174_js.$Zn.prototype.$E@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:59797$4pj@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:57816_js.$2.prototype.$6JC@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:58309Program.main@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:663573invokeMain@https://XXXXX/owa/:549:17owastart/<@https://XXXXX/owa/:601:15:1
X-OWA-Version: 15.0.847.32
X-FEServer: SERVER1
X-BEServer: null
Date: 1/2/1601 3:14:04 PM
It doesn’t happen for everyone just a few people, if we move them to different database in the same DAG on a different server they can access OWA.
What logs can I look at to help find the root cause of this error?
Or has anyone seen this before?
Thanks!
Joe
Joseph Noga MCITP, MCSE, MCSA, MCTS CCNA,CCDA,CCVP Practice Manager Artemis Technology LLC

Hi Winnie,
Thank you for responding. The mailbox and cas servers are separate, and I have rebooted and reset IIS multiple times.
What I have come to find out is if I access the OWA from an older browser it doesn’t switch to OWA light, a newer browser will not have this problem and can get in with the problem mailbox.
If I specify the light directory
owa/?layout=light I can get in to the problem mailbox with no issues.
It seems like the local client can’t process the script that will force the client to use OWA light.
Thanks!
Joe
Joseph Noga MCITP, MCSE, MCSA, MCTS CCNA,CCDA,CCVP
Hi Joe,
According to youe further description, the issue seems to be related to browser. Please update your browser to the latest version or set the Internet Explore to Compatibility view to have a try.
Regards,
Winnie Liang
TechNet Community Support

OWA Error after Exchange 2010 Mailbox move to 2013

Similar Messages

Maybe you are looking for