Litigation Hold Mailbox Migration to Exchange 2013

Hello,
We have in our organization few mailboxes (Exchange 2010) which are enabled for Litigation Hold for a purpose. Now since we are moving to Exchange 2013, need to understand what happens to those mailboxes after migration.
Neilesh

Hi Neilesh,
Below cmdlet would give you the actual mailbox size including the deleted items(changed hold items etc)
Get-MailboxFolderStatistics -Identity contoso\chris | Select Name,FolderSize,ItemsinFolder
Recoverable Items 127.5 KB (130,553 bytes) 54
Deletions 0 B (0 bytes) 0
Purges 0 B (0 bytes) 0
Versions 0 B (0 bytes) 0
Reference:
Reporting Mailbox Folder Sizes with PowerShell
Regards,
Satyajit
Please“Vote As Helpful”
if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

Similar Messages

Free/Busy not working after mailbox migration to Exchange 2013

I'm in the process of migrating user mailboxes from Exchange 2007 to Exchange 2013
It seems that many of the users (not all) are having problems seeing free/busy once they have been migrated. If we remove the Outlook profile and recreate it, all is good. Problem is that this is happening to more and more people. Everyone
is on Outlook 2010
Test-OutlookWebServices -ClientAccessServer Ex2013 -identity MyName -MailboxCredential $cred    Results in:
Autodiscover: Outlook Provider Failure
Exchange Web Services          Failure
Availability Service           Skipped
Offline Address Book           Failure
The same if I run that command against the Exchange 2007 server.
What am I doing wrong?

I should have mentioned that. Yes, OWA works perfectly for the affected users. Just as deleting their Outlook profile and recreating a new one does.
Results of Get-WebServicesVirtualDirectory:
Identity    : Exch2007Srvr\EWS (Default Web Site)
InternalUrl : https://legacy.company.com/EWS/Exchange.asmx
ExternalUrl : https://legacy.company.com/EWS/Exchange.asmx
Identity    : Exch2013Srvr\EWS (Default Web Site)
InternalUrl : https://mail.company.com/ews/exchange.asmx
ExternalUrl : https://mail.company.com/ews/exchange.asmx
The URL you reference above is actually the site I used to perform migration.
What's interesting (at least to me) is that on my machine I did not have any issues with seeing calendars. The Test E-mail AutoConfiguration (without Guessmart), I get prompted for my password over and over; however, after clicking on cancel I
get:
Attempting URL
https://mail.company.com/autodiscover/autodisconver.xml found through SCP
Autodiscover to
https://mail.company.com/autodiscover/autodisconver.xml starting
GetLastError=0;httpStatus=401
GetLastError=0;httpStatus=401
GetLastError=0;httpStatus=401
GetLastError=0;httpStatus=401
GetLastError=0;httpStatus=401
Autodiscover to
https://mail.company.com/autodiscover/autodisconver.xml Failed (0x80040413)
Attempting URL
https://autodiscover.company.com/autodiscover/autodisconver.xml found through SCP
Autodiscover to
https://autodiscover.company.com/autodiscover/autodisconver.xml starting
GetLastError=0; httpStatus=200.
Autodiscover to
https://autodiscover.company.com/autodiscover/autodisconver.xml Failed (0x800C8203)
Autodiscover to https://company.local/autodiscover/autodiscover.xml starting
GetLastError=12029; httpStatus=0
Autodiscover to https://company.local/autodiscover/autodisconver.xml Failed (0x80004005)
Autodiscover to
https://autodiscover.company.local/autodiscover/autodisconver.xml starting
GetLastError=0; httpStatus=0
GetLastError=0; httpStatus=200
Autodiscover to
https://autodiscover.company.local/autodiscover/autodisconver.xml Failed (0x800C8203)
Local autodiscover for company.local starting
Local autodiscover for company.local Failed (0x8004010F)
Redirect check to
https://autodiscover.company.local/autodiscover/autodisconver.xml starting
Redirect check to
https://autodiscover.company.local/autodiscover/autodisconver.xml Failed (0x800C820D)
Srv Record lookup for hydraforce.ads starting
Srv Record lookup for hydraforce.ads Failed(0x8004010F)
However, when I did this on a system that cannot see any calendars, it all works perfectly.
Browsing to
https://autodiscover.hydraforce.com/autodiscover/autodiscover.xml does result in Error Code 600

Mailboxes migrated to Exchange 2013 - some Outlook profiles do not auto-update

** EDIT WITH SIMPLIFIED QUESTION:
Should I be able to manually create a profile in my Exchange 2013 environment without knowing the
GUID@DOMAIN server name? When I specify the Ex2010 server name and Outlook Anywhere settings, the server name does not auto-resolve to the GUID as other threads suggest. I am curious whether others are able to manually
create a profile without knowing the GUID@domain.
Hi all,
Our computers have Outlook configured to automatically configure a profile without any intervention. The profile is pointing to Exchange 2010, which is still running in our environment with Exchange 2013. When a user logs into a computer and
launches Outlook for the first time, Outlook fails to connect and a "Cannot open your default-email folders" error occurs.
I have verified that the Outlook Anywhere settings are configured correctly.
If I delete the profile and create a new one using Autodiscover, everything works fine.
Occurs on all clients - 2007, 2010, 2013, fully patched).
To troubleshoot, I attempted to manually create a new profile. I supplied the Exchange 2010 server name, and configured Outlook Anywhere. When hitting "Check Name", the server name stays to Exchange 2010 (does not switch to
[email protected]). When I launch Outlook, the connection fails. Again, an autodiscovery succeeds.
From my reading, it appears that Outlook should be updating the profile with the new GUID server name when it attempts to connect. The RPCClientAccessServer setting on the Exchange 2013 databases points to the Exchange 2010 CAS Array names.
Any ideas?
Thanks for your hel

Thanks for the reply .
AutodiscoverInternalURI is pointing to the Exchange 2013 environment, and is working fine when auto creating the profile. The Test Autodiscover function returns the correct URL for the mailboxes. The problem comes when manually creating
a profile. Other threads indicate that a manually created profile should auto change the server name when the Check Name option is selected, but mine remains with the Ex2010 cas name listed on the database, and the creation fails.
However, if the user had previously connected to Ex2010 prior to the mailbox move, the profile successfully changes to Ex2013. Only during manual creation does it fail, which is a problem because our existing PCs are configured to create
profiles without autodiscover.

Exchange 2010 dag migration to exchange 2013 help

If I want to use the Same mailbox servers and upgrade them to exchange 2013, what is the recommended way? I have a 4 member exchange 2010 DAG.
I was thinking (where A,B,C,D are mailbox servers, A,B are in one site and C,D another active directory site):
A B -------------- C D
Remove A and C from the 2010 DAG, Format and install Exchange 2013 on both, and create a 2013 dag :
A1 ----------- C1
B ------------- D
Then move across all mailboxes from B to A1. Upgrade B and D to exchange 2013 and put them in the DAG
A1 B1 ----------- C1 D1
Does this make sense ? I am trying to do this while having as much high availability as possible during the transition. I have no extra servers so I have to use the existing server hardware.
Anand_N

Hi,
When you want to migrate a DAG from Exchange 2010 to Exchange 2013, you should first remove the mailbox server from the DAG in Exchange 2010 and then move mailboxes from database in this mailbox server to Exchange 2013. After all mailboxes have been migrated
to the Exchange 2013 mailbox server, when the new server is ready, it can become a member of the Exchange 2013 DAG.
Here is an article about migration DAG from Exchange 2010 to Exchange 2013 for your reference.
Migrating an Exchange 2010 DAG to Exchange 2013
http://windowsitpro.com/blog/migrating-exchange-2010-dag-exchange-2013
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Migrating AD Exchange 2013 Objects to a new AD Domain

I have a client 'new company' (NC) who is splitting from the 'parent company' (PC). They are using a 3rd party tool to conduct the AD migration/split.
The PC AD domain is on Windows 2012 Servers and has trust relationship with the NC AD domain also running on windows 2012 server. The users and computers have been successfully migrated/stubbed to the NC domain, however, the Exchange 2013 objects
are not migrating over to the NC AD domain using the 3rd party AD migration tool.
Question, does any one have suggestions on how to migrate the exchange 2013 objects from the PC AD to the NC AD ?
What techniques can be used ?
Thanks in advance
RK

What 3rd party tool are you using and have you contacted their support already? You can use the native tools to migrate mailboxes (I do all the time) but I wouldn't try and mix the native tools and a 3rd party tool on the same migration unless I was sure
what the end result would be.

Configure legacy public folders where user mailboxes are on Exchange 2013 servers

Hello all,
I have mailboxes on an exchange 2013 server than need access to public folders on a 2010 server before I migrate them over. I followed the commands in the TechNet article with the subject "Configure legacy public folders where user mailboxes
are on Exchange 2013 servers" (sorry, I wasn't allowed to insert a link because I wasn't verified?). The problem is when I run the last command of "Set-OrganizationConfig -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes ProxyMailbox1,ProxyMailbox2,ProxyMailbox3"
on the 2013 server, using the mailbox name I had created, it says it cannot be found. Of course I checked and the mailbox exists, is configured properly, and so is the new database. The 2013 EAC also sees the mailbox with no issues.
Can someone tell me why I am getting this error?
Thanks,
Shaibal

Hi Mavis,
Thank you for your response. I am the full domain admin, and check and was part of both groups mentioned above. Also, I have only one 2010 server with public folder, and so the command I am running on the 2013 looks like this: Set-OrganizationConfig
-PublicFoldersEnabled Remote -RemotePublicFolderMailboxes PFMailbox1. I even just created a second user and mailbox using the console instead of the shell, and still no luck.
Below is the error I get:
[PS] C:\Windows\system32>Set-OrganizationConfig -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes PFMailbox2
Couldn't find object "PFMailbox2". Please make sure that it was spelled correctly or specify a different object.
    + CategoryInfo          : NotSpecified: (:) [Set-OrganizationConfig], ManagementObjectNotFoundException
    + FullyQualifiedErrorId : [Server=ZOR-EXCHANGE01,RequestId=cc567b2f-34d8-41ba-9261-143223566e06,TimeStamp=3/5/2015
    4:36:10 PM] [FailureCategory=Cmdlet-ManagementObjectNotFoundException] 2EF24201,Microsoft.Exchange.Management.Sys
temConfigurationTasks.SetOrganizationConfig
    + PSComputerName        : zor-exchange01.zubatkin.lan

Outlook 2007 on Terminal Server cannot manage Public Folder Favorites after Migration to Exchange 2013

Hi,
we are running a Server 2008 R2 as a Terminal Server with Outlook 2007 SP3 (incl Nov 2012 Update 12.0.6665.5000) which is known as fully supported with Exchange 2013.
With Exchange Server 2007 we did not have any issues. But after having successfully migrated to Exchange 2013 we cannot manage our public folders favorites from these clients anymore.
As we are running Outlook 2007 on a WTS we can not use Exchange Cache Mode and so we can also not download Public-Folders-Favorites as an option. Whenever we try to delete existing favorites or when we try to delete public folders with content or subfolders
there will be an error msg that says that it cannot be deleted and that there may be no sufficient permissions. But this IS NOT the issue NOR the solution as I have full admin rights and am owner of the public folders.
On single fat clients with Outlook 2007 with Exchange Cache Mode enabled we can manage the favorites and the public folders without problem.
We need to be able to manage the favorites of all users (circa 50-60 users) from the WTS with Outlookm 2007. I have no more ideas right now. Does anyone know how to get this settled?
Thanks, Paula

Hi,
Based on the description, users could access public folders successfully, but when they tried to manage public folder favorites or wanted to remove specified folders, they got error message of no sufficient permissions.
Is it right?
You mentioned on single fat clients with Outlook 2007 with Exchange Cache Mode enabled, user can operate normally. Is this a WTS with Outlook 2007 installed?
If possible, please switch this Outlook client from cached mode to online mode to check result.
Best regards,
Belinda Ma
TechNet Community Support

Cutover Migration to Exchange 2013 On-premises

I have two clients who will be merging their on-prem Exchange
organizations. Different forests. I've done many cutover migrations to
Office 365 for other clients so I'm familiar with the process. My
question is: Is it possible to do an O365-style cutover migration (create migration endpoint, cutover batch, etc.) from
an on-prem Exchange 2010 server to an on-prem Exchange 2013 server using
the same steps?
Thanks in advance for any input.
Steve

Hi,
Based on my knowledge, the Cutover Migration is used for migration to Exchange online. There is no related document about
Cutover Migration from Exchange 2010 to Exchange 2013.
To perform Exchange 2010 corss-forest migration to Exchange 2013, you need to use Active Directory Migration Tool (ADMT) migrate user accounts.
Here is a related blog which may help you. (Even though this article is for Exchange 2010 corss-forest migration, it's also applies to cross-forest migration from Exchange 2010 to Exchange 2013.)
http://blogs.technet.com/b/meamcs/archive/2011/06/10/exchange-2010-cross-forest-migration-step-by-step-guide-part-i.aspx
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

After migration to Exchange 2013 the old outlook clients do not automatically reconfigure

After migration to Exchange 2013 the old outlook clients do not automatically reconfigure
we use outlook 2013

Hi ,
I hope you would be having exchange 2013 coexistence environment with exchange 2010 or 2007.
Autodiscover is the feature which will make the outlook profiles to configure automatically.So please make sure the following things are in place.
1.Autodiscover record on the internal dns need to be configured and it has to be resolved properly to the cas servers or else to the LB if you have.
2.Please check the autodiscover internal url.
get-clientaccessserver -identity "server name" | fl *internaluri*
3.Make sure the name used for the autodisocver and internal outlook anywhere are available on the SAN certificate installed in exchange.Same time we need to enable the installed SAN certificate for the exchange services like iis,pop,imap,smtp.
4.You need to have the autodicover name and internal outlook anywhere name on the internet explorer proxy exceptions when you have proxy servers available on your network for internet access.
Note : moreover we need an additional information's from your side about your environment.
Thanks & Regards S.Nithyanandham

Mailbox sizes increase dramatically after migration to exchange 2013

After I migrate mailboxes from exchange 2010 mailbox to 2013, the size increases.
For example -
On exchange 2010 I run get-mailboxstatistics: TotalItemSize : 6.706 GB
On exchange 2013: TotalItemSize : 9.374 GB
Anand_N

Hi Anand,
Please note that the actual space used by the mailbox database will not increase. This only refers to the attribution of space used by each individual mailbox. Actually, this happens due to the inclusion of all item properties into quota calculations, providing
a more accurate computation of space consumed by items within their mailbox. However, you can adjust mailbox size and increase mailbox quota by 40% before moving.
You can follow below cmdlet in order to increase "ProhibitSendQuota" value for all users that are not using the database quota defaults:
Get-Mailbox -ResultSize Unlimited -Filter {UseDatabaseQuotaDefaults -eq $False} |
Where {$_.ProhibitSendQuota -ne "unlimited"} | ForEach {Set-Mailbox $_ -ProhibitSendQuota "$($($_.ProhibitSendQuota).Value.ToMB() * 1.4)MB" -WhatIf}
You can have a look on this link to prevent the cause :
Mailbox migration from 2010 to 2013
Hope, this will be helpful for you.

Exchange 2007 migrate to Exchange 2013

Dear MS Support,
I did migrate Exchange 2007 to Exchange 2013
The install complete, the exchange 2007 and 2013 can work together successful
DAG has created and work fine
Below is capture on exchange group after migrate
The exchange 2007 work fine with outlook anywhere, all the users can connected and send and receive mail in 5 year
The cerificate enroll with
Alternative Names: mail.biendongpoc.vn
The autodiscover on exchange 2007:
[PS] C:\Windows\system32>Get-ClientAccessServer | ft Identity,*uri* -AutoSize
Creating a new session for implicit remoting of "Get-ClientAccessServer" command...
Identity AutoDiscoverServiceInternalUri
BDPOC-SERVER1 https://mail.biendongpoc.vn/Autodiscover/Autodiscover.xml
I have created new certificate for Two exchange 2013
The certificate enroll with
Alternative Names: cas.biendongpoc.vn
I have create cname cas point to dag on DNS server
I have create A record autodiscover.biendongpoc.vn point to IP of dag.biendongpoc.vn
I did migrate mailbox from exchange 2007 to exchange 2013, the migrate successful , the outlook can
connected to Exchange 2013 and working perfectly
Our problem, the account exchange 2007 work not stable ,
sometime it connect to mail.abc.com, sometime it connect to cas.abc.com
If the outlook connect to cas.biendongpoc.vn, the request put password and i can't connect to exchange 2007, if outlook connect to mail.biendongpoc.vn i can connect
It is not stable for current exchange 2007
Anyone who can help me ?
Thanks

Hi
huynhtrongnhatminh,
I suggest you please go through this article.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Please check this for step by step guide.
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
Please point your autodiscover and commonname to Exchange2013 CAS
Please configure your URLs. There is no CAS array in Exchange2013 but the concept of single name space remains.
You need to have an A record (e.g. legacy.domain.com) in yout external DNS and add that name (legacy.domain.com) in your certificate for exchange 2007 users to have access externally.
Configure your commonname URLs in Exchange2013. Point commonname and autodiscover to exchange2013 in both external and internal DNS servers
Configure URLshttp://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
No CASARRAY in 2013http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/
Please configure splitdns or pinpoint DNS in your internal DNS server if not configured
http://exchange.sembee.mobi/network/split-dns.asp
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Unable to access public folders on Exchange 2007 when user mailbox is on Exchange 2013

Hi
I have coexistence with Exchange 2007 and Exchange 2013. I've moved a mailbox to Exchange 2013 and now cannot view the public folders on Exchange 2007. The error message I get is "could not connect to the public folder server. microsoft exchange is
not available. either there are network problems or the exchange server is down for maintenance."
Mailboxes on Exchange 2007 do not have any problems viewing public folders. I can't migrate users to Exchange 2013 until this issue is resolved.
The IIS permissions to the Public virtual directory on Exchange 2007 is set to Intergrated Windows and Basic authentication.

Hi northerly,
I recommend you follow the steps below for troubleshooting:
1. Please run the Get-OutlookAnywhere cmdlet to verify the Outlook Anywhere settings on Exchange Server 2013 Client Access servers.
2. If "ExternalHostName" is set, and "ExternalClientAuthenticationMethod" is Negotiate, change "ExternalClientAuthenticationMethod" to something other than Negotiate.
3. If "InternaClientlAuthenticationMethod" is set to Negotiate, and "InternalRequireSSL" is True, change "InternalClientAuthenticationMethod" to something other than Negotiate, or change "InternalRequireSSL" to False.
What's more, here is a helpful KB for your reference.
Users of Exchange Server 2013 or Exchange Online can't open public folders or shared mailboxes on an Exchange 2010 or Exchange 2007 server
http://support.microsoft.com/kb/2834139/en-us
Hope my clarification is helpful.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Exchange 2007 migration to Exchange 2013

Hello Exchange experts,
I’m Planning an Exchange migration (EX07 to EX13) and despite to have read many many tutorials and technet opinions, I cannot see the correct path to migrate. I hope someone can help me.
- Actual Infrastructure:
     1 Physical server (SERVER_08): DC + Exchange 2007. IP: 192.168.1.10
- Future Infrastructure:
     1 Physical Server (SERVER_2012R2): DC, GC, FS. IP: 192.168.1.50
    1 Physical Server (EX2013): CAS,Mailbox. IP: 192.168.1.51
My questions come once I’ve prepared the squema and I have to start with the Exchange Migration. As far as I know, I think the steps and infrastructure behavior will flow in this way:
Initial State: Only one Exchange2007 installed and all the clients point to this server, and thus in this moment the value of SCP is the initial Exchange Server SERVER_08.
In SERVER_08 there is one self-certificate with this names: SERVER_08.test.local and SERVER_08 and all the Outlook clients and Windows Phones use this certificate. This works perfectly.
I install a secondary Exchange (EX2013) in a new server but in the same internal domain (test.local).
Once the second Exchange server is installed, the SCP is automactly updated with the new SCP pointing to this Exchange 2013 (EX2013).
      So that the clients don’t give them
a prompt message, the SCP must be changed with PowerShell to point the initial    Exchange Server (SERVER_08). (Right?)
Create a A register (mail.test.local) pointing to the new Exchange 2013 (EX2013 - 192.168.1.51).
        At this point, I understand that the clients can coexist with both Exchange Servers (EX07/EX13) and no one will be prompted with new certificate issues. Right?
Once the Mailbox Databases/Connectors are migrated to the new exchange 2013, I need to modify again through PowerShell the SCP value with the new EX2013
(mail.test.local).
When the clients open again the Outlook client, will be prompted to agree the new Exchange 2013 certificate and
everything will work fine during the next 5 years (Exchange 2013 self-certificate lifetime).
I’ve been reading many tutorials and I want to make sure the steps until coexist both Exchange works fine, and obviously
if the experts can suggest me something.
Thanks in advance
Best Regards
Tecnico Superior de Sistemas

There a few things missing in here like the legacy URL specifics, and Outlook client version requirements (do not overlook Outlook, or it will bite you).
I'm curious about this bit "When the clients open again the Outlook client, will be prompted to agree the new Exchange 2013 certificate and
everything will work fine during the next 5 years (Exchange 2013 self-certificate lifetime). "
You should not be advocating the use of self signed certs, they are not supported for Outlook Anywhere. Even if this is testing, install a Windows CA and use that to issue certs of
get a cheap commercial one.
Training users it is OK to click here to see the dancing pigs never bodes well :)
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Cross-forest migration to Exchange 2013 SP1 and Outlook 2013 SP1

Hello! I have two forest: Exchange 2010 SP2 RU5 - resource forest and Exchange 2013 SP1 - account forest. I make cross-forest migration from resource forest (linked mailboxes with account forest) to forest with Exchange 2013 SP1.
I have moved mailbox from resource forest exchange 2010 to exchange 2013 sp1 forest.
Outlook 2010 connect to migrated mailbox without any problem, but outlook 2013 sp1 cannot connect to migrated mailbox.
Error look like - cannot find exchange server.
I created new mailbox in Exchange 2013 organization and can connect to it with outlook 2010 and outlook 2013 sp1.
Someone have the same problem with migrated mailbox? How to solve it?
Truly, Valery Tyurin

You can use New-MoveRequest to perform a cross-forest move. Here is a well post and step-wise explanation you can check for cross forest migration from exchange 2010 to exchange 2013(http://msexchangeguru.com/2013/11/03/e2013crossforestmigration/).
Moreover, you can try this utility (
http://www.exchangemigrationtool.com/ ) to accomplish this task.

OWA still redirects to Exchange 2007 (legacy) after mailbox-move to Exchange 2013

Hi,
I am in the process of implementing Exchange 2013 in coex with 2007. I am testing now in a copy of the production environment and have installed the Exchange 2007 SP3 RU11 prior to installing Exchange 2013 using the SP1 media.
We use a wildcard certificate and I prepared the Exchange 2007 internal/external URLs for OWA/OAB/etc to use the legacy.domain.com names and in Exchange 2013 I set them all to email.domain.com. Exchange 2013 has Outlook Anywhere configured.
All tests like autodiscover (internally via SCP) run fine and for a new Exchange 2013 mailbox the Outlook and OWA functionality is as expected. A mailbox still on 2007 also connects fine via Outlook and while connecting to OWA (using the htps://email.domain.com/owa
url) also redirects me to https://legacy.domain.com/owa just fine.
HOWEVER: after a successfull mailbox-move from 2007 to 2013 my OWA logon-request STILL get's redirected to the 2007 legacy URL. When I then logon again on the 2007 OWA I get the message that I should connect to the 2013 URL and end-up in a loop.
Anyone any tips where to search?
Many thanks in advance.
Best regards and many thanks in advance, Eric Vegter

This seems to be an outstanding issue.
We just performed a fresh install of Exchange 2013 on a Windows Server 2012 R2 operating system. We're migrating from our existing Exchange 2007 server. At the moment we have everything properly setup in a co-existence state. All we lack is to complete the
migration of our mailboxes from the 2007 DB to the 2013 DB.
In performing the first mailbox move, to test the migration process and make certain mail flows as expected, we noticed this same problem. Before reading through this thread, I was able to assign Full Access to a delegate user and then perform the "Open
Mailbox" feature from a 2013 user's account. This was successful in opening the mailbox within OWA 2013. However, I still could not access the account by simply logging into the Outlook Web App. It would login, then proxy back to OWA 2007 with the message,
"Use the following link to open this mailbox with optimal performance:
http://mail.domainname.com/"
After reading about cycling the OWA app pool, I immediately tried it as a workaround and it worked. It is a little frustrating going about it in this way. Hoping to see more activity on this thread.
-Lorne

Litigation Hold Mailbox Migration to Exchange 2013

Similar Messages

Maybe you are looking for