Exchange 2007 to 2013 virtual directories

I'm gathering information before I do my transition to Exchange 2013. One thing I'm not sure about is the virtual directory for OWA. The information I have gathered states to change the internal/external URL to legacy.domain.com. However
my virtual directory for OWA are not defined. How do I approach that? do I just not set anything?
Thanks

I planned on configuring each like this below. I'm not using UM but that is also good to know. Outlook Anywhere is enabled on the 2007 side. This is also just a single exchange server
Internal DNS and Certificate will have these entries.
mail.mydomain.com - Points to Exchange 2013
autodiscover.mydomain.com - Points to Exchange 2013
legacy.mydomain.com - Points to Exchange 2007
Set the Virtual Directories on Exchange 2013
Set-OutlookAnywhere -Identity "EXC02\RPC (Default Web Site)" -IISAuthenticationMethods Basic,NTLM
Set-ECPVirtualDirectory -Identity "EXC02\ecp* -InternalURL
https://mail.mydomain.com/ecp -ExternalURL
https://mail.mydomain.com/ecp
Set-OWAVirtualDirectory -Identity "EXC02\OWA* -InternalURL $null -ExternalURL $null
Set-WebServicesVirtualDirectory -Identity "EXC02\ews* -InternalURL
https://mail.mydomain.com/ews/exchange.asmx -ExternalURL
https://mail.mydomain.com/ews/exchange.asmx
Set-OABVirtualDirectory -Identity "EXC02\oab* -InternalURL
https://mail.mydomain.com/oab -ExternalURL
https://mail.mydomain.com/oab
Set-ActiveSyncVirtualDirectory -Identity "EXC02\microsoft* -InternalURL
https://mail.mydomain.com/Microsoft-Server-ActiveSync -ExternalURL
https://mail.mydomain.com/Microsoft-Server-ActiveSync
Set-PowershellVirtualDirectory -Identity "EXC02\powershell* -InternalURL
https://mail.mydomain.com/Powershell -ExternalURL
https://mail.mydomain.com/Powershell
Set-ClientAccessServer -Identity EXC02 -AutoDiscoverServiceInternalURI
https://autodiscover.mydomain.com/autodiscover/autodiscover.xml
Set the Virtual Directories on Exchange 2007
Set-OutlookAnywhere -Identity "EXC01\RPC (Default Web Site)" -IISAuthenticationMethods Basic,NTLM
Set-OutlookAnywhere -Identity "EXC01\Rpc (Default WebSite)" -IISAuthenticationMethods Basic,Ntlm
Set-OWAVirtualDirectory -Identity "EXC01\OWA* -InternalURL https://legacy.mydomain.com/owa -ExternalURL
https://legacy.mydomain.com/owa
Set-WebServicesVirtualDirectory -Identity "EXC01\ews* -InternalURL
https://mail.mydomain.com/ews/exchange.asmx -ExternalURL
https://mail.mydomain.com/ews/exchange.asmx
Set-OABVirtualDirectory -Identity "EXC01\oab* -InternalURL
https://legacy.mydomain.com/oab -ExternalURL
https://legacy.mydomain.com/oab
Set-ActiveSyncVirtualDirectory -Identity "EXC01\microsoft* -InternalURL
https://mail.mydomain.com/Microsoft-Server-ActiveSync -ExternalURL $null
Set-PowershellVirtualDirectory -Identity "EXC01\powershell* -InternalURL
https://legacy.mydomain.com/Powershell -ExternalURL
https://legacy.mydomain.com/Powershell
Set-ClientAccessServer -Identity EXC01 -AutoDiscoverServiceInternalURI
https://autodiscover.mydomain.com/autodiscover/autodiscover.xml

Similar Messages

Free/Busy not working Exchange 2007 and 2013 co-existence

Hi,
I'm migrating our Exchange 2007 environment to Exchange 2013. Now I am in a co-existence environment where all the mailboxes except some test-users resides on Exchange 2007. Between Users on the same Exchange MBX Server athe FREE/BUSY Information sharing
works correctly, but between Exchange 2007 and 2013 it's not working.
I verified my settings and also the EWS virtual directory on 2007 CAS Servers using Get-WebServicesVirtualDirectory.
The internal and the external URLs are set to https://legacy.mydomain.com/....
What am I missing?
Thanks & Kind Regards,
Jürgen

Hi,
According to your description, I understand that the free/busy information between Exchange 2007 and Exchange 2013 is not available for your coexistence environment. To narrow down the issue, please check the following points:
1. Does the issue happen to all users or specific users?
2. Although a user on Exchange 2013 can't get free/busy information from a user on Exchange 2007, please confirm whether Exchange 2007 user can get free/busy information from Exchange 2013 users.
3. Close Outlook and only access user mailbox from OWA to check whether the issue persists. For Outlook client,
create a new Outlook profile
to have a try.
4. Please make sure the virtual directories settings are configured correctly in both Exchange 2013 and Exchange 2007.
Virtual directories settings in Exchange 2007:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
Certificate and Virtual directories settings in Exchange 2013:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-2-step-by-step-exchange-2007-to-2013-migration.aspx
5. Restart IIS service in Exchange server by running iisreset /noforce from a command prompt window.
If possible, please run Test E-mail AutoConfiguration in Outlook to check whether the autodiscover service can get correct Availability service URL in the results. If there is any event logs, please collect some for further analysis.
Regards,
Winnie Liang
TechNet Community Support

Legacy Namespace for Exchange 2007 to 2013 co-existence

We are migrating from Exchange 2007 to 2013, during the co-existence phase, where is the legacy.{domain.com} namespace used? We are at the point now that we want to move all services over to the Exchange 2013 CAS servers, however... GPO settings
are used to point outlook clients to mail.{domain.com} for Outlook Anywhere. If DNS is updated to point mail.{domain.com} to the Exchange 2013 servers, will there be an issue with connectivity for people still on the Exchange 2007 servers? Do these people
need to point to legacy.{Domain.com} or will mail.{domain.com} proxy the connection to the legacy namespace? I would like to know if the GPO settings will interfer with the settings that Autodiscovery provide back.
I have read a bunch or articles on the approach, but I am still fuzzy on where legacy.{domain.com} comes into play.
Thanks in advance for your help.

In coexistence with exchange 2013 and legacy version the request happens in 2 types.
For Exchange 2010 –
Exchange 2013 does a Proxy for owa and ews requests for users in exchange 2010.
For Exchange 2007 –
Exchange 2013 does redirection for owa and ews requests for users in Exchange 2007.
Certificates:
All the required SAN entries for UM,webservices and activesync should be created.
Add external owa legacy URL to the public certificate and install it on both Exchange 2007 and
Exchange 2013 only then owa redirection will work.
You need to Include internal Legacy. Domain.com on Exchange 2007 Certificate for OWA co-
Existence.
Following change needs to be done in Firewall
External OWA URL should be directed to exchange 2013 Internet Facing CAS.
External EWS URL should be directed to exchange 2013 Internet Facing CAS.
External Autodiscover URL should should be directed to Exchange 2013 CAS.
External ActivesyncVirtualDirectory should be directed to Exchange 2013 CAS.
External UMvirtualDirectory should be directed to Exchange 2013 CAS.
Create new NAT rule on firewall for Legacy.domain.com to Exchange 2007 CAS. You can do this as well.By doing this users will be able to log on directly using the URL https://legacy.domain.com/owa with
a mailbox on Exchange 2007.
External and Internal DNS settings
Public DNS - Map all of your external public DNS records (ews,owa,activesync etc.,) to your
exchange 2013 public IP if you have dedicated one for 2013 or FQDN of your internet facing CAS server.
Example:
Current external owa URL (contoso.domain.com) – point it to dedicated exchange 2013 public ip or internet facing exchange 2013 CAS FQDN.
Current External Autodiscover – point it to dedicated exchange 2013 public ip or internet
facing exchange 2013 CAS FQDN
Internal DNS – Configure the Exchange 2007 to point SCP AutoDiscoverURI to Exchange 2013 Client
Access FQDN by changing DNS entry for Autodiscover.domain.com to exchange 2013 CAS sever Ip
address
The internal DNS records should point to the internal host name and IP address of your Exchange
2013 Client Access server
Make sure that legacy.contoso.com resolves to CAS2007 in internal and external DNS.
Authentication Settings:
This part is little bit tricky. You need to plan according to your organization. If you have FBA configured in TMG or ISA server then you need to configure accordingly.
Set the owa virtual directory authentication only to Basic in exchange 2007.
In exchange 2013 set owa virtual directory to only (Windows Authentication) or only (form-based authentication) or only (Basic, No redirection, SSL Enabled) depends according to your setup.
Things to check:
If you have redirection configured in IIS on the Exchange 2007 Server Make sure that the above
Virtual Directories doesn’t have it configured.
If you have FBA enabled on ISA or TMG then disable FBA on Exchange 2013 CAS else users will be prompted twice for authentication
For further references you can refer my article below
http://exchangequery.com/2014/09/24/owaews-configuration-in-exchange-20132007-coexistence/
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish (MVP)

Can only access emails through OWA after migration from exchange 2007 to 2013

can only access emails through OWA after migration from exchange 2007 to 2013, in other words unable to access mails through outlook or from other Applications services.
needed RCA ... plz help..

Hi,
From your description, you can send and receive messages only when you use OWA after migration from Exchange 2007 to Exchange 2013. If I have misunderstood your concern, please let me know.
In your case, I recommend you create a new test mailbox in your Exchange 2013 and check if you can send and receive messages on Outlook. If yes, it is recommended to create a new profile to solve this issue.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Issue moving remote user from exchange 2007 to 2013

have moved over 60 people so far from exchange 2007 to 2013, it was going well with no major problems.
during migration I have created a DNS setting called legacy.mydomain.com, and it points to the old exchange server, while mail.mydomain.com points to the new exchange server.
outlook was working connecting to both servers, and OWA was working on both servers.
couple of remote users who connect via SSL-VPN and outlook 2010 had issues connecting, but as soon as I moved them to 2013 exchange they connected without vpn using outlook anywhere.
but - I have one remote user who even though the mailbox move to the new 2013 server was successful, their outlook still points to the 2007 exchange server.
if I try creating a new profile in outlook 2013, it fails because it cannot contact exchange server, even when ssl-vpn is running.
when I started troubleshooting I found lots of spyware on his laptop, symantec had been blocking some trojans, obviously he had downloaded something he shouldnt have.
could this have caused my outlook connectivity issue?
I ran malawarebytes, and it shows clean now, but still unable to get his outlook to connect.
I had thought about moving his mailbox back to the old server, seeing if it works on outlook, then moving it to the new one again.
any suggestions?

I had thought about moving his mailbox back to the old server, seeing if it works on outlook, then moving it to the new one again.
Hi,
Have you done this step? Sometimes moving mailbox to another database can auto-fix problems.
According to your description, I know that all migrated mailboxes work well except a specific user. I notice that the user's laptop has a lots of spyware, and symantec has been clocking some trojans.
Please try to logon OWA to check whether this user works.
If works in OWA, it seems that the mailbox has been migrated to 2013 successfully.
Generally, re-creating profile can fix this issue. Unfortunately, you have tried it and failed.
Please try to run Outlook under safe mode to avoid AVs and add-ins.
Thanks
Mavis Huang
TechNet Community Support

How to migrate from exchange 2007 to 2013 step by step tutorials please

Hi
I am running Windows Server 2008 standard, with exchange 2007 SP2 on it.
We have 800 mailbox in total
Our domain controllers are
Win2012 R2 and I would like to upgrade to Exchange 2013 on Windows server 2012 R2.
I am running a VM, on VMware environment, so my Windows 2012 R2 is a VM.
Is there a website or document that explains in detail, step by step how to upgrade from 2007 to 2013.
I currently only have 1 exchange server 2007, with all the roles on the one server. I would like to keep that same as
well with exchange 2013.
Thanks

Exchange server deployment assistant is always a good service provider to achieve this task as it simply ask few questions about your current environment and proceed further accordingly.
You can refer to this blog explained by technet team that will assist you further to gather more information in depth : http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
Moreover, to avoid the interruptions and proceed a hassle-free migration from exchange 2007 to 2013, this application (http://www.exchangemigrationtool.com/) could also be a good approach to accomplish
migration task in more secure way.

Migration from Exchange 2007 to 2013 gives error "Failed to communicate with the mailbox database'

I have been trying to migrate several databases from Exchange 2007 to Exchange 2013. The migration started successfully, and many of the mailboxes moved successfully (about 70). The remaining mailboxes, failed. Looking deeper, we found a few issues; The
two 2013 Mailbox servers were on different versions. The Server had run out of disk space, and the NIC drivers needed to be updated.
Now when we try to migrate a mailbox that had failed in the earlier batch, we get the following error:
Data migrated:
Migration rate:
Error:
MigrationTransientException: Failed to communicate with the mailbox database. --> Failed to communicate with the mailbox database. --> MapiExceptionNetworkError: Unable to make connection to the server. ‎(hr=0x80040115, ec=-2147221227)‎ Diagnostic
context:    ......    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 501    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0    Lid: 11672   dwParam:
0x0 Msg: EEInfo: NumberOfParameters: 4    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode string: <Server
FQDN>    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[2]: Long val: 3749909585    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662    Lid: 45169   StoreEc: 0x824
Lid: 50544   ClientVersion: 15.0.847.32    Lid: 52080   StoreEc: 0x824         Lid: 44273      Lid: 49064   dwParam: 0x1    Lid: 37288
StoreEc: 0x6AB         Lid: 49064   dwParam: 0x2    Lid: 59431   EMSMDB.EcDoConnectEx called [length=203]    Lid: 51239   EMSMDB.EcDoConnectEx exception [rpc_status=0x6D9][latency=0]
Lid: 62184      Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 3460    Lid: 12696   dwParam: 0x0 Msg: EEInfo:
Generation Time: 0414-04-07T16:32:03.2100000Z    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 2    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1753    Lid: 9624
dwParam: 0x0 Msg: EEInfo: Detection location: 501    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 4    Lid: 8856
dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode string: <Server FQDN>    Lid: 12952   dwParam: 0x0 Msg: EEInfo:
prm[2]: Long val: 2767313664    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662    Lid: 59505   StoreEc: 0x824         Lid: 50544   ClientVersion:
15.0.847.32    Lid: 52080   StoreEc: 0x824         Lid: 36081      Lid: 51152      Lid: 52465   StoreEc: 0x80040115
Lid: 60065      Lid: 33777   StoreEc: 0x80040115    Lid: 59805      Lid: 52487   StoreEc: 0x80040115    Lid: 19778      Lid: 27970
StoreEc: 0x80040115    Lid: 17730      Lid: 25922   StoreEc: 0x80040115
All of the issues listed above have been corrected, and all of the databases are mounted. Users are able to send and receive mail, but I can not migrate mail using the Migration Batch utility.
The destination server is a Hyper-V Guest running Server 2012, SP1, and Exchange 2013
The Source Server is Running Exchange 2007.
I have tried doing a test move to another destination server that is also Server 2012, and Exchange 2013, and the migration also failed.
I would appreciate any help you can give me!
Thanks,
Jon

Any update if you have resolved the issue.
Not similar, but this thread can be helpful while you migrate the mailboxes from exchange 2007 to 2013. Please check :http://social.technet.microsoft.com/Forums/exchange/en-US/721f0ae4-623a-4b02-adaf-f561d86c0426/move-mailboxes-and-public-folders-from-exchange-2007-to-exchange-2013?forum=exchangesvrdeploy&prof=required

ActiveSync in Exchange 2007 and 2013 Coexistence

Hi,
I have exchange 2007 and 2013 coexisting (exchange 2007 sp3 update rollup 13/exchange 2013 SP1)
owa works fine from inside and outside, only that it requires users to authenticate twice when connecting from the external.
autodiscover works well for users on both 2007 and 2013
I have a public SAN certificate from verisign with 2 names on it, mail.mydomain.com and legacy.mydomain.com
I have A records configured for both names on my public DNS and internal DNS
THE ISSUES
testing activesync from testconnectivity.microsoft.com works fine when i run the test using a mailbox on Exch2013 but fails for mailbox on Exch2007.
New users on exch2007 & exch2013 are not able to setup email on their devices (blackberry and windows mobile),
Existing users on exch2007 can no longer receive mails on their mobile devices
URLs
Exchange 2007
Exchange 2013
Internal owa
mydomain.com/owa
mail.mydomain/owa
External owa
legacy.mydomain.com/owa
mail.mydomain.com/owa
AutoDiscover
mail.mydomain.com
mail.mydomain.com
EWS
legacy.mydomain.com
mail.mydomain.com
ECP
mail.mydomain.com
Internal ActiveSync
legacy.mydomain.com
mail.mydomain.com
External ActiveSync
$null
mail.mydomain.com
OutlookAnywhere
legacy.mydomain.com
mail.mydomain.com
I expect that users on exch2013 would be able to setup their mobile devices as the connectivity test completes successfully but it still does not.
Any help on this would be much appreciated ..
Richard ..
..forever is just a minute away*

You don't need to use a legacy URL for ActiveSync in Exchange 2013. It will proxy ActiveSync for Exchange 2007 just fine. In fact, ActiveSync is usually the protocol that gives you the least amount of trouble in a transition. I recommend
you configure your URLs for the proxy configuration and point everything to Exchange 2013 CAS.
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange 2007 and 2013 coexistence

Hi,
we have exchange 2007 and 2013 coexistence. we have created a new url for 2007 legacy servers. Now, when using OWA url (now set for exchange 2013 server) i am getting OWA exchange 2007 login page for exchange 2007 mailboxs.
I was expecting exchange 2013 OWA page and then redirection to OWA 2007.
Thanks

Hello,
Please check your DNS configuration and ISA/TMG rules.
We recommend you use TMG or UAG.
You can refer to the "TMG rules" section in the following article:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
Cara Chen
TechNet Community Support

Exchange 2007 to 2013 coexistence Legacy access

I’ve successfully installed Exchange 2013 CU1 (in a cloned environment so I’m no harm done
J) and most thinks seems to work but OWA and Active Sync on EX2007 mailboxes give me some headache.
I’ve created a legacy.company.com DNS record, reconfigured the virtual directories on EX2007 and set OWA to FBA/basic.
OWA IS redirected to EX2007 legacy URL but authentication is not being passed through and you have to enter username password again at the EX2007 OWA site. Active Sync (tested on Iphone) works but you have to enter password at every sync.
What could I be missing?
/Søren Emig

Fiona,
Reading through the first technet link, it makes it seem as though redirection should happen silently and the FBA should be passed to the CAS2007 server seemlessly.
CAS2007 will consume that hidden form's data, authenticate the user and:
Retrieve and render the user's mailbox data from the Exchange 2007 mailbox server and provide the data view back to the user. The response will contain an FBA cookie for the legacy namespace, and from that point on all user activity within the session
will go to legacy CAS only.
Or proxy the request to the Exchange 2003 mailbox server and provide the data view back to the user. The response will contain an FBA cookie for the legacy namespace, and from that point on all user activity within the session will go to legacy CAS
only.
That sounds like the OWA page should render without the user logging in a second time. Also, if you look at the docs for Exchange 2010, the scenario is the same. http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
CAS-01 will look for an Exchange 2007 ExternalURL property
that has an ExternalAuthenticationMethods setting
that's identical to theInternalAuthenticationMethods setting
on the Exchange 2010 Client Access server. If the settings match, CAS-01 will redirect to this external URL. If source and target CAS have Forms Based Authentication (FBA) enabled, the source CAS issues a hidden form back to the browser that contains the user’s
credentials and FBA settings, along with the redirect URL. This is transparent to the user.
Now if the SSO code for Exchange 2013 is not ready, that is another matter. But there is no documentation that I could find explicitly stating this.

Exchange 2007 to 2013 Migration issues. Prompt for credentials, Public Folders inaccessible, Apps not working

Exchange 2013 Migration issues
I have three issues and decided to list them here. Please pick and choose to assist. Thanks in advance.
Environment:
Mixed 2007 SP3 R12 and 2013 CU3. 2007 Environment was webmail.domain.com. I installed new Exchange 2013 (1 CAS, 1 Mailbox) according to:
http://technet.microsoft.com/en-us/library/ff805032(v=exchg.150).aspx. Exchange 2007 is now legacy.domain.com and Exchange 2013 CAS is webmail.domain.com.
Machine 1: Windows 8.1, not domain joined, using Outlook Anywhere external. Outlook 2013
Machine 2: Windows 7, domain joined, using Outlook Anywhere internal. Outlook 2010 SP2
I have migrated 1 user so far to Exchange 2013. This user was a Domain Admin. I have removed that membership. I checked the box to inherit permissions of the security of the object and reset the AdminCount attribute in ADSIedit to 0 and verified this replicated
to all domain controllers. ( I originally thought this to be the issue with it prompting for the password. )
Here is a Get-OutlookAnywhere cmdlet...
ServerName                         : EXCHANGE2007SVR
SSLOffloading                      : False
ExternalHostname                   : legacy.domain.com
InternalHostname                   :
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Basic
IISAuthenticationMethods           : {Basic}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : False
MetabasePath                       : IIS://EXCHANGE2007SVR.domain.local/W3SVC/1/ROOT/Rpc
Path                               : C:\WINDOWS\System32\RpcProxy
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 8.3 (Build 83.6)
Server                             :
EXCHANGE2007SVR
AdminDisplayName                   :
ExchangeVersion                    : 0.1 (8.0.535.0)
Name                               : Rpc (Default Web Site)
DistinguishedName                  : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=EXCHANGE2007SVR,CN=Servers,CN=Exchange
                                     Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
                                     Groups,CN=DOMAIN,CN=Microsoft
                                     Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=local
Identity                           : EXCHANGE2007SVR\Rpc (Default Web Site)
Guid                               : 4901bb14-ab81-4ded-8bab-d5ee57785416
ObjectCategory                     : domain.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged                        : 12/31/2013 4:08:04 PM
WhenCreated                        : 7/18/2008 10:56:46 AM
WhenChangedUTC                     : 12/31/2013 9:08:04 PM
WhenCreatedUTC                     : 7/18/2008 2:56:46 PM
OrganizationId                     :
OriginatingServer                  : DC1.domain.local
IsValid                            : True
ObjectState                        : Changed
ServerName                         :
EXCHANGE2013SVR
SSLOffloading                      : True
ExternalHostname                   : webmail.domain.com
InternalHostname                   : webmail.domain.com
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm}
XropUrl                            :
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : True
MetabasePath                       : IIS://EXCHANGE2013SVR.domain.local/W3SVC/1/ROOT/Rpc
Path                               : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking    : None
ExtendedProtectionFlags            : {}
ExtendedProtectionSPNList          : {}
AdminDisplayVersion                : Version 15.0 (Build 775.38)
Server                             : EXCHANGE2013SVR
AdminDisplayName                   :
ExchangeVersion                    : 0.20 (15.0.0.0)
Name                               : Rpc (Default Web Site)
DistinguishedName                  : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=EXCHANGE2013SVR,CN=Servers,CN=Exchange
                                     Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
                                     Groups,CN=DOMAIN,CN=Microsoft
                                     Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=local
Identity                           : EXCHANGE2013SVR\Rpc (Default Web Site)
Guid                               : d983a4b1-6921-4a7f-af37-51de4a61b003
ObjectCategory                     : domain.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged                        : 1/7/2014 11:29:05 AM
WhenCreated                        : 12/31/2013 1:17:42 PM
WhenChangedUTC                     : 1/7/2014 4:29:05 PM
WhenCreatedUTC                     : 12/31/2013 6:17:42 PM
OrganizationId                     :
OriginatingServer                  : DC1.domain.local
IsValid                            : True
ObjectState                        : Changed
ISSUE 1
Issue: On Machine 1 (reference above) Windows Security prompt that says "Connecting to
[email protected]". Almost always prompts when Outlook is first opened. Afterwards (if it goes away) seemingly random on when it asks for it. I put in the credentials (absolutely correct) and it fails and prompts again.
I always check the box for it to save the password. To get rid of it, I click the Cancel button at which Outlook reports "NEED PASSWORD", but still acts fine sending and receiving emails. Eventually the "NEED PASSWORD" sometimes changes
to say "CONNECTED", but it works regardless.
No issues on Machine 2 so I don't know where the problem might be as there are a lot of variables in play here.
ISSUE 2
Migrated user is unable to open Public folders from Exchange 2007.
Cannot expan the folder. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance. (/o=...).
This error occurs on Machine 1, Machine 2 and from OWA, same error each time.
ISSUE 3
Apps. Installed by default are 4 apps (Bing Maps, Suggested Meetings, Unsubscribe, Action Items). I have made sure the apps are enabled in OWA and they show up in mail items on both Machine 1 (Outlook 2013) and OWA. They do not show up in Machine 2 (Outlook
2010). I'm assuming that isn't supported.
In OWA, when I go to the installed apps listing it shows all of the apps but has a broken link on the image describing the app.
When I click the app in either Outlook 2013 or in OWA, I get "APP ERROR, Sorry we can't load the app. Please make sure you have network and/or internet connectivity. Click "Retry" once you're back online.
Current workaround is just disabling them through OWA.

Hello,
In order to avoid confusion, we troubleshoot a issue per thread usually.
For your first isue, I agree with Ed's suggestion to check if your certificate name is correct.
Besides, I recommend you change ExternalClientAuthenticationMethod from Basic authentication to Negotiate authentication to check the result.
For the second issue and third issue, please create a new post.
If you have any feedback on our support, please click here
Cara Chen
TechNet Community Support

Exchange 2007 and 2013 Co-existnec - ActiveSync Issue

Hi
We have introduced Exchange 2013 servers in our existing Exchange 2007 environment. We have a customized Exchange 2007 ActiveSync setup i:e we created a custom separate website in IIS for ActiveSync to serve the ActiveSync devices. After the introduction
of Exchange 2013 CAS servers, when we installed the new certificate on them and configured the virtual directory with ActiveSync URLs, the Exchange 2013 servers seems to be receiving Activesync requests but they can't just proxy it to Exchange 2007 for some
reason. following Warning is logged on Exchange 2013 servers:
[Eas] Marking ClientAccess 2010 server MIA-EXCAS01.utg.uvn.net (https://mia-excas01.utg.uvn.net/Microsoft-Server-ActiveSync) as unhealthy due to exception: System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.Exchange.HttpProxy.ProtocolPingStrategyBase.Ping(Uri url)
We still need to install new Certificate on the Exchange 2007 servers. Wondering what could be the issue here, can Exchange 2013 proxy the connection to Exchange 2007 on a custom website ? or it looks for one under Default Website?
Can the absence of new certificate (meaning certificate mismatch) lead to this issue?
Thanks
Taranjeet Singh
zamn

Actually 2013 can proxy ActiveSync to 2007
Please follow this.
1. Set AutodiscoverInternalURL using this command for every CAS server
Set-ClientAccessserver -identity -CAS1 -AutodiscoverInternalURI
https://mail.yourcompany.com/autodiscover/autodiscover.xml (for FQDN , using your CAS NLB name if exist)
2. Set OWA virtualdirectoy (2013) via EAC
Internal URL : https://mail.yourcompany.com/owa External URL : https://mail.yourcompany.com/owa
3. Set ECP virtualdirectory (2013) via EAC
Internal URL : https://mail.yourcompany.com/ecp External URL : https://mail.yourcompany.com/ecp
4. Set OAB virtualdirectory (2013) via EAC
Internal URL : https://mail.yourcompany.com/OAB External URL :
https://mail.yourcompany.com/OAB
5. Set EWS virtualdirectory (2013) via EAC
Internal URL : https://mail.yourcompany.com/EWS/Exchange.asmx External URL :
https://mail.yourcompany.com/EWS/Exchange.asmx
6. Set ActiveSync virtualdirectory (2013) viaEAC
Internal URL : https://mail.yourcompany.com/Microsoft-Active-Sync
External URL : https://mail.yourcompany.com/Microsoft-Active-Sync
For 2007
1. Set AutodiscoverInternalURL using this command for every CAS server
Set-ClientAccessserver -identity -CAS1 -AutodiscoverInternalURI
https://mail.yourcompany.com/autodiscover/autodiscover.xml (for FQDN , using your CAS NLB name)
2. Create DNS record
legacy.yourcompany.com = your CAS2007 NLB (if exist)
3. Set OWA virtualdirectory (2007) via EMC
External URL = https://legacy.yourcompany.com/owa
4. Set ActiveSync (2007) via EMC
Internal URL = https://serverFQDN/Microsoft-Active-Sync <<<< Using for proxy
External URL =
https://legacy.yourcompany.com/Microsoft-Active-Sync <<<< Using for redirect
5. OAB via EMC
External URL = https://legacy.yourcompany.com/OAB
6. EWS via Exchange shell
External URL = https://legacy.yourcompany.com/EWS/Exchange.asmx
FYI

Public Folder Migration Fails from Exchange 2007 to 2013

I am attempting to sync public folders between Exchange 2007 and Exchange 2013. All the data has been copied over to the Exchange 2013 server but I am getting an error when creating the folders and their permissions.
I saw a previous thread which looked similar and I have set the bad item limit to one million as well as set mail-disable on the source public folders but I am still receiving these errors.
I set the following commands
Get-PublicFolderMigrationRequest | Set-PublicFolderMigrationRequest -baditemlimit 1000000
Get-PublicFolderMigrationRequest | Resume-PublicFolderMigrationRequest
and on the source mailbox server:
Get-publicfolder \Non_IPM_subtree -Recurse | Disable-MailPublicFolder
12/2/2013 12:56:18 PM [ex01] The Microsoft Exchange Mailbox Replication service
'ex01.domain.LOCAL' (15.0.712.11 caps:3F) is examining the request.
12/2/2013 12:56:18 PM [ex01] Connected to target mailbox
'f5f50f32-d256-4639-840e-cf161edfb538', database 'mdb01', Mailbox server
'ex01.domain.LOCAL' Version 15.0 (Build 712.0), proxy server 'ex01.domain.LOCAL'
15.0.712.11 caps:FFCB07FFFF.
12/2/2013 12:56:24 PM [ex01] Connected to source mailbox '', database
'01SRV\Second Storage Group\Public Folder Database', Mailbox server
'01SRV.domain.LOCAL' Version 8.3 (Build 327.0).
12/2/2013 12:56:25 PM [ex01] Request processing continued, stage LoadingMessages.
12/2/2013 12:56:34 PM [ex01] Copying messages is finished. Copying rules and
security descriptors.
12/2/2013 12:56:35 PM [ex01] A corrupted item was encountered: Folder ACL
"schema-root"
12/2/2013 12:56:36 PM [ex01] A corrupted item was encountered: Folder ACL
"microsoft"
12/2/2013 12:56:36 PM [ex01] A corrupted item was encountered: Folder ACL
"exchangeV1"
12/2/2013 12:56:36 PM [ex01] A corrupted item was encountered: Folder ACL "Default"
12/2/2013 12:57:06 PM [ex01] A corrupted item was encountered: Folder ACL "ORG
Contacts"
12/2/2013 12:57:08 PM [ex01] A corrupted item was encountered: Folder ACL "ORG"

Here we go again...
This the full text from the migration report
15.0.775.35 caps:07FFCB07FFFF.
12/13/2013 6:11:00 AM [ex01] Connected to source mailbox '', database
'DOMAINSRV\Second Storage Group\Public Folder Database', Mailbox server
'DOMAINSRV.DOMAIN.LOCAL' Version 8.3 (Build 327.0).
12/13/2013 6:11:00 AM [ex01] Request processing continued, stage LoadingMessages.
12/13/2013 6:11:34 AM [ex01] Messages have been enumerated successfully. 124813
items loaded. Total size: 69.88 GB (75,027,907,074 bytes).
12/13/2013 6:11:34 AM [ex01] Stage: CopyingMessages. Percent complete: 81.
12/13/2013 6:11:34 AM [ex01] Copy progress: 119253/124813 messages, 56.57 GB
(60,737,390,033 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
12/13/2013 6:16:34 AM [ex01] Stage: CopyingMessages. Percent complete: 81.
12/13/2013 6:16:34 AM [ex01] Copy progress: 119670/124813 messages, 56.78 GB
(60,967,399,787 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
12/13/2013 6:21:52 AM [ex01] Stage: CopyingMessages. Percent complete: 82.
12/13/2013 6:21:52 AM [ex01] Copy progress: 120208/124813 messages, 56.99 GB
(61,189,806,498 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
12/13/2013 6:26:55 AM [ex01] Stage: CopyingMessages. Percent complete: 82.
12/13/2013 6:26:55 AM [ex01] Copy progress: 120850/124813 messages, 57.19 GB
(61,401,994,205 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
12/13/2013 6:30:54 AM [ex01] Transient error TimeoutErrorTransientException has
occurred. The system will retry (1/60).
12/13/2013 6:31:27 AM [ex01] The Microsoft Exchange Mailbox Replication service
'ex01.DOMAIN.LOCAL' (15.0.775.35 caps:3F) is examining the request.
12/13/2013 6:31:28 AM [ex01] Connected to target mailbox
'543ef8dc-c797-44d4-b1f0-82c13ef9a8b3', database 'mdb01', Mailbox server
'ex01.DOMAIN.LOCAL' Version 15.0 (Build 775.0), proxy server 'ex01.DOMAIN.LOCAL'
15.0.775.35 caps:07FFCB07FFFF.
12/13/2013 6:31:31 AM [ex01] Connected to source mailbox '', database
'DOMAINSRV\Second Storage Group\Public Folder Database', Mailbox server
'DOMAINSRV.DOMAIN.LOCAL' Version 8.3 (Build 327.0).
12/13/2013 6:31:32 AM [ex01] Request processing continued, stage LoadingMessages.
12/13/2013 6:32:18 AM [ex01] Messages have been enumerated successfully. 127721
items loaded. Total size: 69.88 GB (75,027,907,074 bytes).
12/13/2013 6:32:18 AM [ex01] Stage: CopyingMessages. Percent complete: 82.
12/13/2013 6:32:18 AM [ex01] Copy progress: 120850/127721 messages, 57.19 GB
(61,401,994,205 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
12/13/2013 6:37:20 AM [ex01] Stage: CopyingMessages. Percent complete: 82.
12/13/2013 6:37:20 AM [ex01] Copy progress: 121456/127721 messages, 57.39 GB
(61,624,479,276 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
12/13/2013 6:42:23 AM [ex01] Stage: CopyingMessages. Percent complete: 82.
12/13/2013 6:42:23 AM [ex01] Copy progress: 122010/127721 messages, 57.59 GB
(61,841,264,369 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
12/13/2013 6:47:27 AM [ex01] Stage: CopyingMessages. Percent complete: 82.
12/13/2013 6:47:27 AM [ex01] Copy progress: 122471/127721 messages, 57.81 GB
(62,071,372,686 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
12/13/2013 6:52:28 AM [ex01] Stage: CopyingMessages. Percent complete: 83.
12/13/2013 6:52:28 AM [ex01] Copy progress: 122799/127721 messages, 58.03 GB
(62,313,820,476 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
12/13/2013 6:57:32 AM [ex01] Stage: CopyingMessages. Percent complete: 83.
12/13/2013 6:57:32 AM [ex01] Copy progress: 123165/127721 messages, 58.26 GB
(62,551,175,147 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
12/13/2013 7:02:47 AM [ex01] Stage: CopyingMessages. Percent complete: 83.
12/13/2013 7:02:47 AM [ex01] Copy progress: 123403/127721 messages, 58.48 GB
(62,788,359,363 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
12/13/2013 7:07:46 AM [ex01] Stage: CopyingMessages. Percent complete: 83.
12/13/2013 7:07:46 AM [ex01] Copy progress: 123578/127721 messages, 58.68 GB
(63,006,399,077 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
12/13/2013 7:12:49 AM [ex01] Stage: CopyingMessages. Percent complete: 83.
12/13/2013 7:12:49 AM [ex01] Copy progress: 123860/127721 messages, 58.89 GB
(63,236,856,689 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
12/13/2013 7:18:08 AM [ex01] Stage: CopyingMessages. Percent complete: 84.
12/13/2013 7:18:08 AM [ex01] Copy progress: 124003/127721 messages, 59.14 GB
(63,502,560,871 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
12/13/2013 7:23:16 AM [ex01] Stage: CopyingMessages. Percent complete: 84.
12/13/2013 7:23:16 AM [ex01] Copy progress: 124256/127721 messages, 59.37 GB
(63,748,493,498 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
12/13/2013 7:28:32 AM [ex01] Stage: CopyingMessages. Percent complete: 84.
12/13/2013 7:28:32 AM [ex01] Copy progress: 124324/127721 messages, 59.62 GB
(64,020,061,704 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
12/13/2013 7:33:34 AM [ex01] Stage: CopyingMessages. Percent complete: 84.
12/13/2013 7:33:34 AM [ex01] Copy progress: 124431/127721 messages, 59.85 GB
(64,264,685,207 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
12/13/2013 7:38:35 AM [ex01] Stage: CopyingMessages. Percent complete: 85.
12/13/2013 7:38:35 AM [ex01] Copy progress: 124708/127721 messages, 60.08 GB
(64,506,162,189 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
12/13/2013 7:43:40 AM [ex01] Stage: CopyingMessages. Percent complete: 85.
12/13/2013 7:43:40 AM [ex01] Copy progress: 125322/127721 messages, 60.31 GB
(64,754,561,945 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
12/13/2013 7:49:07 AM [ex01] Stage: CopyingMessages. Percent complete: 85.
12/13/2013 7:49:07 AM [ex01] Copy progress: 125707/127721 messages, 60.56 GB
(65,029,278,117 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
12/13/2013 7:54:13 AM [ex01] Stage: CopyingMessages. Percent complete: 85.
12/13/2013 7:54:13 AM [ex01] Copy progress: 125851/127721 messages, 60.82 GB
(65,302,611,480 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
12/13/2013 7:59:31 AM [ex01] Stage: CopyingMessages. Percent complete: 86.
12/13/2013 7:59:31 AM [ex01] Copy progress: 126373/127721 messages, 61.02 GB
(65,518,015,156 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
12/13/2013 8:04:41 AM [ex01] Stage: CopyingMessages. Percent complete: 86.
12/13/2013 8:04:41 AM [ex01] Copy progress: 126552/127721 messages, 61.16 GB
(65,674,209,110 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
12/13/2013 8:09:48 AM [ex01] Stage: CopyingMessages. Percent complete: 86.
12/13/2013 8:09:48 AM [ex01] Copy progress: 126895/127721 messages, 61.34 GB
(65,861,675,410 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
12/13/2013 8:14:49 AM [ex01] Stage: CopyingMessages. Percent complete: 86.
12/13/2013 8:14:49 AM [ex01] Copy progress: 127557/127721 messages, 61.53 GB
(66,063,603,306 bytes)/69.88 GB (75,027,907,074 bytes), 91/5034 folders completed.
12/13/2013 8:19:57 AM [ex01] Stage: CopyingMessages. Percent complete: 86.
12/13/2013 8:19:57 AM [ex01] Copy progress: 128005/128325 messages, 61.69 GB
(66,237,927,764 bytes)/69.88 GB (75,027,907,074 bytes), 192/5034 folders completed.
12/13/2013 8:25:13 AM [ex01] Stage: CopyingMessages. Percent complete: 86.
12/13/2013 8:25:13 AM [ex01] Copy progress: 128475/139047 messages, 61.86 GB
(66,421,418,453 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
12/13/2013 8:30:19 AM [ex01] Stage: CopyingMessages. Percent complete: 87.
12/13/2013 8:30:19 AM [ex01] Copy progress: 128835/139047 messages, 62.07 GB
(66,645,530,813 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
12/13/2013 8:35:26 AM [ex01] Stage: CopyingMessages. Percent complete: 87.
12/13/2013 8:35:26 AM [ex01] Copy progress: 129166/139047 messages, 62.25 GB
(66,842,856,718 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
12/13/2013 8:40:27 AM [ex01] Stage: CopyingMessages. Percent complete: 87.
12/13/2013 8:40:27 AM [ex01] Copy progress: 129621/139047 messages, 62.45 GB
(67,056,383,800 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
12/13/2013 8:46:30 AM [ex01] Stage: CopyingMessages. Percent complete: 87.
12/13/2013 8:46:30 AM [ex01] Copy progress: 129846/139047 messages, 62.65 GB
(67,268,508,177 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
12/13/2013 8:56:48 AM [ex01] Stage: CopyingMessages. Percent complete: 88.
12/13/2013 8:56:48 AM [ex01] Copy progress: 130475/139047 messages, 63.06 GB
(67,715,144,500 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
12/13/2013 9:01:58 AM [ex01] Stage: CopyingMessages. Percent complete: 88.
12/13/2013 9:01:58 AM [ex01] Copy progress: 130823/139047 messages, 63.28 GB
(67,942,071,073 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
12/13/2013 9:07:02 AM [ex01] Stage: CopyingMessages. Percent complete: 88.
12/13/2013 9:07:02 AM [ex01] Copy progress: 131336/139047 messages, 63.44 GB
(68,121,053,596 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
12/13/2013 9:12:18 AM [ex01] Stage: CopyingMessages. Percent complete: 88.
12/13/2013 9:12:18 AM [ex01] Copy progress: 131776/139047 messages, 63.63 GB
(68,323,645,651 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
12/13/2013 9:17:49 AM [ex01] Stage: CopyingMessages. Percent complete: 88.
12/13/2013 9:17:49 AM [ex01] Copy progress: 131940/139047 messages, 63.75 GB
(68,452,787,403 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
12/13/2013 9:23:02 AM [ex01] Stage: CopyingMessages. Percent complete: 89.
12/13/2013 9:23:02 AM [ex01] Copy progress: 132194/139047 messages, 63.9 GB
(68,614,192,595 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
12/13/2013 9:28:19 AM [ex01] Stage: CopyingMessages. Percent complete: 89.
12/13/2013 9:28:19 AM [ex01] Copy progress: 132405/139047 messages, 64.05 GB
(68,773,962,785 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
12/13/2013 9:33:22 AM [ex01] Stage: CopyingMessages. Percent complete: 89.
12/13/2013 9:33:22 AM [ex01] Copy progress: 132617/139047 messages, 64.17 GB
(68,906,275,781 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
12/13/2013 9:38:34 AM [ex01] Stage: CopyingMessages. Percent complete: 89.
12/13/2013 9:38:34 AM [ex01] Copy progress: 132865/139047 messages, 64.36 GB
(69,106,121,613 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
12/13/2013 9:43:53 AM [ex01] Stage: CopyingMessages. Percent complete: 89.
12/13/2013 9:43:53 AM [ex01] Copy progress: 133061/139047 messages, 64.56 GB
(69,316,087,375 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
12/13/2013 9:48:53 AM [ex01] Stage: CopyingMessages. Percent complete: 89.
12/13/2013 9:48:53 AM [ex01] Copy progress: 133269/139047 messages, 64.78 GB
(69,553,487,559 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
12/13/2013 9:53:59 AM [ex01] Stage: CopyingMessages. Percent complete: 90.
12/13/2013 9:53:59 AM [ex01] Copy progress: 133631/139047 messages, 64.98 GB
(69,772,059,026 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
12/13/2013 9:59:29 AM [ex01] Stage: CopyingMessages. Percent complete: 90.
12/13/2013 9:59:29 AM [ex01] Copy progress: 133853/139047 messages, 65.19 GB
(70,002,477,102 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
12/13/2013 10:04:33 AM [ex01] Stage: CopyingMessages. Percent complete: 90.
12/13/2013 10:04:33 AM [ex01] Copy progress: 134089/139047 messages, 65.36 GB
(70,179,472,038 bytes)/69.87 GB (75,027,615,351 bytes), 204/5034 folders completed.
12/13/2013 10:09:04 AM [ex01] Transient error TimeoutErrorTransientException has
occurred. The system will retry (1/60).
12/13/2013 10:09:40 AM [ex01] The Microsoft Exchange Mailbox Replication service
'ex01.DOMAIN.LOCAL' (15.0.775.35 caps:3F) is examining the request.
12/13/2013 10:09:43 AM [ex01] Connected to target mailbox
'543ef8dc-c797-44d4-b1f0-82c13ef9a8b3', database 'mdb01', Mailbox server
'ex01.DOMAIN.LOCAL' Version 15.0 (Build 775.0), proxy server 'ex01.DOMAIN.LOCAL'
15.0.775.35 caps:07FFCB07FFFF.
12/13/2013 10:09:48 AM [ex01] Connected to source mailbox '', database
'DOMAINSRV\Second Storage Group\Public Folder Database', Mailbox server
'DOMAINSRV.DOMAIN.LOCAL' Version 8.3 (Build 327.0).
12/13/2013 10:09:48 AM [ex01] Request processing continued, stage LoadingMessages.
12/13/2013 10:10:20 AM [ex01] Messages have been enumerated successfully. 139047
items loaded. Total size: 69.87 GB (75,027,615,351 bytes).
12/13/2013 10:10:20 AM [ex01] Stage: CopyingMessages. Percent complete: 90.
12/13/2013 10:10:20 AM [ex01] Copy progress: 134097/139047 messages, 65.39 GB
(70,216,735,350 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
12/13/2013 10:11:21 AM [ex01] Stage: CopyingMessages. Percent complete: 90.
12/13/2013 10:11:21 AM [ex01] Copy progress: 134133/139047 messages, 65.42 GB
(70,245,991,410 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
12/13/2013 10:11:22 AM [ex01] Stage: CopyingMessages. Percent complete: 90.
12/13/2013 10:11:22 AM [ex01] Copy progress: 134133/139047 messages, 65.42 GB
(70,245,991,410 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
12/13/2013 10:11:22 AM [ex01] The long-running job has been temporarily postponed.
It will be picked up again when resources become available.
12/13/2013 10:11:26 AM [ex01] The Microsoft Exchange Mailbox Replication service
'ex01.DOMAIN.LOCAL' (15.0.775.35 caps:3F) is examining the request.
12/13/2013 10:11:26 AM [ex01] Connected to target mailbox
'543ef8dc-c797-44d4-b1f0-82c13ef9a8b3', database 'mdb01', Mailbox server
'ex01.DOMAIN.LOCAL' Version 15.0 (Build 775.0), proxy server 'ex01.DOMAIN.LOCAL'
15.0.775.35 caps:07FFCB07FFFF.
12/13/2013 10:11:31 AM [ex01] Connected to source mailbox '', database
'DOMAINSRV\Second Storage Group\Public Folder Database', Mailbox server
'DOMAINSRV.DOMAIN.LOCAL' Version 8.3 (Build 327.0).
12/13/2013 10:11:32 AM [ex01] Request processing continued, stage LoadingMessages.
12/13/2013 10:11:49 AM [ex01] Messages have been enumerated successfully. 139047
items loaded. Total size: 69.87 GB (75,027,615,351 bytes).
12/13/2013 10:11:49 AM [ex01] Stage: CopyingMessages. Percent complete: 90.
12/13/2013 10:11:49 AM [ex01] Copy progress: 134097/139047 messages, 65.39 GB
(70,216,735,350 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
12/13/2013 10:17:02 AM [ex01] Stage: CopyingMessages. Percent complete: 90.
12/13/2013 10:17:02 AM [ex01] Copy progress: 134444/139047 messages, 65.61 GB
(70,448,693,136 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
12/13/2013 10:22:08 AM [ex01] Stage: CopyingMessages. Percent complete: 90.
12/13/2013 10:22:08 AM [ex01] Copy progress: 134729/139047 messages, 65.82 GB
(70,668,635,903 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
12/13/2013 10:27:16 AM [ex01] Stage: CopyingMessages. Percent complete: 91.
12/13/2013 10:27:16 AM [ex01] Copy progress: 135103/139047 messages, 66 GB
(70,867,621,766 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
12/13/2013 10:32:27 AM [ex01] Stage: CopyingMessages. Percent complete: 91.
12/13/2013 10:32:27 AM [ex01] Copy progress: 135380/139047 messages, 66.19 GB
(71,070,869,590 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
12/13/2013 10:39:14 AM [ex01] A large item was encountered: Item (IPM.Note)
Subject:"Ellicott Barge Models", Size: 77.95 MB (81,733,960 bytes), Folder:"x 7)
Ellicott Filed"
12/13/2013 10:39:14 AM [ex01] Stage: CopyingMessages. Percent complete: 91.
12/13/2013 10:39:14 AM [ex01] Copy progress: 135611/139047 messages, 66.44 GB
(71,343,628,026 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
12/13/2013 10:44:44 AM [ex01] Stage: CopyingMessages. Percent complete: 91.
12/13/2013 10:44:44 AM [ex01] Copy progress: 135911/139047 messages, 66.63 GB
(71,544,181,750 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
12/13/2013 10:51:00 AM [ex01] Stage: CopyingMessages. Percent complete: 91.
12/13/2013 10:51:00 AM [ex01] Copy progress: 136252/139047 messages, 66.85 GB
(71,779,294,348 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
12/13/2013 10:56:06 AM [ex01] Stage: CopyingMessages. Percent complete: 92.
12/13/2013 10:56:06 AM [ex01] Copy progress: 136462/139047 messages, 67.05 GB
(71,995,944,420 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
12/13/2013 11:01:11 AM [ex01] Stage: CopyingMessages. Percent complete: 92.
12/13/2013 11:01:11 AM [ex01] Copy progress: 136594/139047 messages, 67.26 GB
(72,223,775,275 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
12/13/2013 11:06:15 AM [ex01] Stage: CopyingMessages. Percent complete: 92.
12/13/2013 11:06:15 AM [ex01] Copy progress: 136726/139047 messages, 67.43 GB
(72,406,316,662 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
12/13/2013 11:11:17 AM [ex01] Stage: CopyingMessages. Percent complete: 92.
12/13/2013 11:11:17 AM [ex01] Copy progress: 136801/139047 messages, 67.6 GB
(72,586,529,915 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
12/13/2013 11:16:32 AM [ex01] Stage: CopyingMessages. Percent complete: 92.
12/13/2013 11:16:32 AM [ex01] Copy progress: 136879/139047 messages, 67.8 GB
(72,801,385,018 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
12/13/2013 11:21:34 AM [ex01] Stage: CopyingMessages. Percent complete: 93.
12/13/2013 11:21:34 AM [ex01] Copy progress: 136953/139047 messages, 67.98 GB
(72,993,383,384 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
12/13/2013 11:26:47 AM [ex01] Stage: CopyingMessages. Percent complete: 93.
12/13/2013 11:26:47 AM [ex01] Copy progress: 137103/139047 messages, 68.19 GB
(73,218,959,998 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
12/13/2013 11:31:57 AM [ex01] Stage: CopyingMessages. Percent complete: 93.
12/13/2013 11:31:57 AM [ex01] Copy progress: 137533/139047 messages, 68.39 GB
(73,429,774,999 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
12/13/2013 11:37:01 AM [ex01] Stage: CopyingMessages. Percent complete: 93.
12/13/2013 11:37:01 AM [ex01] Copy progress: 137720/139047 messages, 68.58 GB
(73,633,221,526 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
12/13/2013 11:42:15 AM [ex01] Stage: CopyingMessages. Percent complete: 93.
12/13/2013 11:42:15 AM [ex01] Copy progress: 137812/139047 messages, 68.74 GB
(73,809,270,838 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
12/13/2013 11:47:27 AM [ex01] Stage: CopyingMessages. Percent complete: 94.
12/13/2013 11:47:27 AM [ex01] Copy progress: 138129/139047 messages, 68.95 GB
(74,030,024,926 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
12/13/2013 11:52:32 AM [ex01] Stage: CopyingMessages. Percent complete: 94.
12/13/2013 11:52:32 AM [ex01] Copy progress: 138322/139047 messages, 69.17 GB
(74,265,630,831 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
12/13/2013 11:57:36 AM [ex01] Stage: CopyingMessages. Percent complete: 94.
12/13/2013 11:57:36 AM [ex01] Copy progress: 138505/139047 messages, 69.36 GB
(74,471,042,974 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
12/13/2013 12:03:18 PM [ex01] Stage: CopyingMessages. Percent complete: 94.
12/13/2013 12:03:18 PM [ex01] Copy progress: 138696/139047 messages, 69.52 GB
(74,643,441,657 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
12/13/2013 12:10:25 PM [ex01] A large item was encountered: Item (IPM.Note)
Subject:"Walkway Hose Mystery", Size: 93.98 MB (98,540,300 bytes), Folder:"Sent
Items"
12/13/2013 12:10:25 PM [ex01] Stage: CopyingMessages. Percent complete: 94.
12/13/2013 12:10:25 PM [ex01] Copy progress: 138848/139047 messages, 69.71 GB
(74,851,776,952 bytes)/69.87 GB (75,027,615,351 bytes), 30/5034 folders completed.
12/13/2013 12:14:42 PM [ex01] Copying messages is finished. Copying rules and
security descriptors.
12/13/2013 12:14:52 PM [ex01] A corrupted item was encountered: Folder ACL
"schema-root"
12/13/2013 12:14:52 PM [ex01] A corrupted item was encountered: Folder ACL
"microsoft"
12/13/2013 12:14:53 PM [ex01] A corrupted item was encountered: Folder ACL
"exchangeV1"
12/13/2013 12:14:53 PM [ex01] A corrupted item was encountered: Folder ACL "Default"
12/13/2013 12:15:11 PM [ex01] A corrupted item was encountered: Folder ACL "DOMAIN
Contacts"
12/13/2013 12:15:13 PM [ex01] A corrupted item was encountered: Folder ACL "DOMAIN"
12/13/2013 1:41:05 PM [ex01] Initial seeding completed, 139047 items copied, total
size 69.87 GB (75,027,615,351 bytes).
12/13/2013 1:41:06 PM [ex01] Stage: CopyingMessages. Percent complete: 95.
12/13/2013 1:41:06 PM [ex01] Copy progress: 139047/139047 messages, 69.87 GB
(75,027,615,351 bytes)/69.87 GB (75,027,615,351 bytes), 47/5034 folders completed.
12/13/2013 1:41:06 PM [ex01] Fatal error TooManyLargeItemsPermanentException has
occurred.
ObjectState : New
[PS] C:\Windows\system32>Get-PublicFolderMigrationRequest | Get-PublicFolderMigrationRequestStatistics
Name StatusDetail SourceDatabase PercentComplete
PublicFolderMigration FailedOther DOMAINSRV\Second Storage Group\Public... 95
[PS] C:\Windows\system32>

Public Folder Migration from Exchange 2007 to 2013

Hi Guys,
I have a general Exchange 07-13 migration question about migrating the PF's and System Folder Information, I read somewhere that the SystemFolder info doesn't come across, can someone shed some light on this for me please?
Thanks,
Ray

Hi Ray,
Free/Busy information is stored in system public folder. If you want to decommission the Exchange 2007 Server, you need to add the replicas to Exchange 2013 Server.
What's more, if the users use Outlook 2003, they will rely on the Free/Busy folders. If the users are using Outlook 2007 or newer, then Outlook utilizes something called the Availability Service and no longer relies on the Free/Busy folder.
Please refer to the following article to migrate public folders from Exchange 2007 to Exchange 2013.
Migrate Public Folders to Exchange 2013 From Previous Versions
http://technet.microsoft.com/en-us/library/jj150486.aspx
Besides, here is a helpful thread for your reference.
move/migrate Public Folder from Exchange 2007 to Exchange 2010
http://social.technet.microsoft.com/Forums/exchange/en-US/44b29a93-0149-4734-8e19-6679ad7701ce/movemigrate-public-folder-from-exchange-2007-to-exchange-2010?forum=exchange2010
Hope it helps.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Public Folder Migration from Exchange 2007 to 2013 fails RelinquishedWlmStall budget limitations

I have been trying to migrate approx 50 public folders from Exchange 2007 to Exchange 2013 for several months. I have followed every link I can find on how to do the migration properly. It will stay in a queued state for hours until the MRS is
restarted. It will then start copying messages. After reaching 28% I get RelinquishedWlmStall as Status Detail. Running the Get-PublicFolderMigrationRequestStatistics -IncludeReport | fl command I get the following: (truncated)
Status : InProgress
FailureTimestamp :
IsValid : True
ValidationMessage :
OrganizationId :
RequestGuid : ff4af794-f31e-4334-959f-7d6c4ccbe310
RequestQueue : PublicFolders
ExchangeGuid : b12c1f83-c4ae-46bb-a26a-0422d90800e4
Identity : eddf983d-5827-4a2a-98ef-820321ebebd0\ff4af794-f31e-4334-959f-7d6c4ccbe310
DiagnosticInfo :
Report
4/23/2015 8:49:37 AM [pionexxxx] Request processing started.
4/23/2015 8:49:37 AM [pionexxxxx] Cleared sync state for request
00000000-0000-0000-0000-000000000000 due to 'CleanupOrphanedMailbox'.
4/23/2015 8:49:38 AM [pionexxxxxx] Stage: CreatingFolderHierarchy. Percent complete:
10.
4/23/2015 8:49:38 AM [pionexxxxxx] Initializing folder hierarchy from mailbox '': 50
folders total.
4/23/2015 8:49:38 AM [pionexxxx] Folder creation progress: 0 folders created in
mailbox 'b12c1f83-c4ae-46bb-a26a-0422d90800e4'.
4/23/2015 8:49:38 AM [pionexxxxx] Warning: Failed to find or link recipient object
'FF-D5-EF-1A-0A-95-D7-4B-89-02-A6-9E-DA-4D-23-4B' in active directory for mail
enabled public folder 'Public Root/IPM_SUBTREE/AccountingFaxes' with EntryId '00-00
00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-C3-C1-30-22-E0-BE-4E
98-03-B9-14-4F-B4-12-C1-00-00-00-0F-C3-4C-00-00'. This folder can be linked
manually by running Enable-MailPublicFolder cmdlet after the migration completes.
4/23/2015 8:49:39 AM [pionexxxx] Warning: Failed to find or link recipient object
'D8-46-09-BE-0B-3D-6E-4A-95-10-8F-C5-AA-0B-88-50' in active directory for mail
enabled public folder 'Public Root/IPM_SUBTREE/AccountingFaxes/CashRec/Inventory'
with EntryId '00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-
3-C1-30-22-E0-BE-4E-98-03-B9-14-4F-B4-12-C1-00-00-00-12-6A-F5-00-00'. This folder
can be linked manually by running Enable-MailPublicFolder cmdlet after the
migration completes.
4/23/2015 8:49:39 AM [pionexxxx] Warning: Failed to find or link recipient object
'A6-12-DA-05-7D-21-DE-44-90-61-64-23-8C-62-41-F4' in active directory for mail
enabled public folder 'Public Root/IPM_SUBTREE/AccountingFaxes/CashRec/Ulysses'
with EntryId '00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-
3-C1-30-22-E0-BE-4E-98-03-B9-14-4F-B4-12-C1-00-00-00-0F-C3-7C-00-00'. This folder
can be linked manually by running Enable-MailPublicFolder cmdlet after the
migration completes.
4/23/2015 8:49:40 AM [pionexxxx] Warning: Failed to find or link recipient object
'96-76-90-F1-A5-B7-DB-41-A7-A3-D6-8D-86-AE-45-A5' in active directory for mail
enabled public folder 'Public Root/IPM_SUBTREE/CSR Schedule' with EntryId '00-00-00
00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-C3-C1-30-22-E0-BE-4E-98
03-B9-14-4F-B4-12-C1-00-00-00-0E-34-FF-00-00'. This folder can be linked manually
by running Enable-MailPublicFolder cmdlet after the migration completes.
4/23/2015 8:49:40 AM [pionexxxx] Warning: Failed to find or link recipient object
'82-72-47-AA-D7-68-85-4C-91-92-41-45-8A-20-EA-6D' in active directory for mail
enabled public folder 'Public Root/IPM_SUBTREE/DC 24 Hr Schedule' with EntryId '00-
0-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-85-62-89-2A-52-C3-92-
5-93-F8-5A-6F-56-5D-D1-D4-00-00-00-00-27-37-00-00'. This folder can be linked
manually by running Enable-MailPublicFolder cmdlet after the migration completes.
4/23/2015 8:49:41 AM [pionexxxx] Folder hierarchy initialized for mailbox
'b12c1f83-c4ae-46bb-a26a-0422d90800e4': 46 folders created.
4/23/2015 8:49:41 AM [pionexxxx] Stage: CreatingInitialSyncCheckpoint. Percent
complete: 15.
4/23/2015 8:49:41 AM [pionexxxx] Initial sync checkpoint progress: 0/50 folders
processed. Currently processing mailbox 'b12c1f83-c4ae-46bb-a26a-0422d90800e4'.
4/23/2015 8:49:42 AM [pionexxxx] Initial sync checkpoint completed: 46 folders
processed.
4/23/2015 8:49:42 AM [pionexxxx] Stage: LoadingMessages. Percent complete: 20.
4/23/2015 8:49:43 AM [pionexxxx] Messages have been enumerated successfully. 40607
items loaded. Total size: 149 MB (156,253,810 bytes).
4/23/2015 8:49:43 AM [pionexxxx] Stage: CopyingMessages. Percent complete: 25.
4/23/2015 8:49:43 AM [pionexxxx] Copy progress: 0/40607 messages, 0 B (0
bytes)/149 MB (156,253,810 bytes), 11/50 folders completed.
4/23/2015 9:04:37 AM [pionexxxx] Stage: CopyingMessages. Percent complete: 28.
4/23/2015 9:04:37 AM [pionexxxxx] Copy progress: 3660/40607 messages, 7.015 MB
(7,355,409 bytes)/149 MB (156,253,810 bytes), 11/50 folders completed.
4/23/2015 9:04:37 AM [pionexxxx] Relinquishing job because of large delays due to
unfavorable server health or budget limitations.
ItemsTransferred : 3660
PercentComplete : 25
4/23/2015 9:04:37 AM [pionexxxx] Relinquishing job because of large delays due to
unfavorable server health or budget limitations.
It never tries to restart. Can anyone please help? The server checks for health all come back ok. I will be more than glad to include further information.

Hi,
Basic on the error message, I notice that public folder migrate slow and display that “Relinquishing job because of large delays due to unfavorable server health or budget limitations” .
If I misunderstand your concern, please do not hesitate to let me know.
Since it is just slow and not failing, please do not stop the batch, it might connect to another server for sync.
Meanwhile, please refer to below link so that get details about Exchange Online migration performance and best practices:
https://technet.microsoft.com/library/dn592150(v=exchg.150).aspx
If the issue persists, please collect the relevant migration report for further troubleshooting.
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support

Exchange 2007 to 2013 virtual directories

Similar Messages

Maybe you are looking for