Exchange 2013 transition from 2010

I have installed a single 2013 CAS server and a single 2013 MB server in my testlab. I already have a 2010 cas server, Hub Server, and mb server in the testlab. After installing 2013, and redirecting my mail to the 2013 CAS server, mail is flowing to
the 2013 MB server. In the Queue Viewer for the 2013 DB server, I see the message with the next hop being SITE:mysite; Version:14, Delivery Type is SMTP Relay to Mailbox Delivery Group; Status is Retry;
Error:
"Wednesday, June 19, 2013 12:11:19 PM" "[{LRT=6/19/2013 12:10:19 PM};{LED=451 4.4.0 Primary target IP address responded with: ""451 5.7.3 Cannot achieve Exchange Server authentication."" Attempted failover to alternate
host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was (IP of 2010 Hub:25};{FQDN=2010 Hub Server FQDN};{IP=2010 Hub Server}]"
Submission Undefined Ready 0
I am at a loss on how to correct this. Is there a jedi master out there that can help?

I know it has been a year since this thread, but I wanted to say thank you. This worked for me after many hours of troubleshooting. I thought just checking Anonymous users under the Permission Groups would work. But that isn't the case, I needed to add
"Exchange Server authentication" under the Authentication tab. I was able to telnet fine with the anonymous users, hence my hours of troubleshooting. Your post did it so THANK YOU!

Similar Messages

Exchange 2013 upgrade from 2010 and no mail flow and cannot move mailboxes

I am in the process of moving to Ex 2013 from 2010. I have installed Ex 2013 SP1 on a new server 2012 R2. All of my Ex 2010 servers are SP3 RU 5. Ex 2013 is running and I can connect through the EAC and see all other Exchange servers and connectors that
were already in existence. Several puzzling things are happening now that the servers are in coexistence:
1) As soon as Ex 2013 was installed on the network, many Outlook users are continuously being prompted to enter their domain credentials. They can cancel the prompt and Outlook still sends/receives email. No user mailboxes are on Ex 2013 yet.
Why is this happening?
2) I am following the Ex 2013 Deployment Assistant and I get to the step to move the Ex 2010 Arbitration mailbox to Ex 2013 and the move does not happen--it just says "syncing" and never completes. I tried moving a test mailbox from Ex 2010
to the 2013 database and I get the same result. I created the move request on the Ex2013 server and I see it as queued on the Ex2010 server, so I know they are "talking" to each other. However, when reviewing the status of the move I
see "MapiExceptionNoAccess: Unable to open message store".
3) There seems to be no mail flow on the same Ex2013 server or between the Ex 2010 and 2013 servers. I created two new test user mailboxes in Ex 2013. The Ex2013 mailboxes cannot send/receive to each other or to Ex 2010 users. This
seems strange, unless I am completely missing something in the Ex 2013 install?
I know this is a lot in one post, but following the Deployment assistant, I was hoping this would be something that others have faced. Thanks for any input here.

Does the below points already fit for you.
Exchange 2013 Supported with the following minimum versions of Exchange:
1) Exchange*** 2010 SP3 on all Exchange 2010 servers in the organization, including Edge Transport servers.
2) Exchange 2013 CU2 or later on all Exchange 2013 servers in the organization.
*** If you want to create an EdgeSync Subscription between an Exchange 2010 Hub Transport server and an Exchange 2013 SP1 Edge Transport
server, you need to install Exchange 2010 SP3 Update Rollup 5 or later on the Exchange 2010 Hub Transport server.
Thanks Prem P Rana MCSA Messaging 2003 MCSE 2003 Server MCTS MCITP Exchange 2007, 2010 Gurgaon, India http://blogs.msexchange-experts.com

Exchange 2013 Migration from 2010 Test (Shared split DNS)

Hi
Im testing a migration from Exchange 2010 to 2013. I have tried to run a single DNS name to both servers, so externally mail.test.com resolves to the external IP and that NAT's to the new Exchange 2013. Then internally mail.test.com resolves both to EXC13
and EXC10 ip adresses (Round Robin).
I have moved some mailboxes to 2013. If the IP resolves to the new Exchange and i try to login to a mailbox on the old server i get redirected as im supposed to. If the IP resolves to the old Exchange and i try to login with a mailbox on the new server i
get:
A server configuration change is temporarily preventing access to your account. Please close all Web browser windows and try again in a few minutes. If the problem continues, contact your helpdesk.
Should this be possible, or do i need to change the intarnal URL on all virtual directories on the old server to the local netbios name or what to do?

You should never use the server name in any of the URLs. You should use either a CNAME or a load-balanced VIP with a generic name like mail.company.com or webmail.company.com. Then you just point this name to the new server. If
you're currently using a server name, it's about time to change that first before trying to switch to Exchange 2013.
Curently im using a generic name, mail.test.com. But that's just a normal A record on the internal DNS. So i cannot use that on both?

Journaling mailbox - Exchange 2013 Migrations from 2010

hi guys
i am about to start mailbox movement from Exchange 2010 to 2013. my setup is working fine. i have enabled journaling from Exchange 2010 and as ii found, automatically journaling rules will be reflected to exchange 2013. i had very big journaling mailbox
and then newly created New Exchange 2010 journaling mailbox. now new journaling mailbox is configured for journaling and that also still on 2010(both Old and new journaling mailbox ), new mailx is couple of weeks old (6-8 GB) and old one is 2.6 TB. So i will
move old one at the end .
my questions is if i move new journaling mailbox to 2013 before start normal Mailboxes, it will cause some issues for journaling. i use premium journaling . is it okay to move journaling mailbox at the begin ??
thank you
Indunil

Hi,
Based on my test, journal rules will be synchronized in Exchange 2013 after you create in Exchange 2010. If you create in Exchange 2013, then the rule will be synchronized in Exchange 2010.
And I did create a rule to send message to a Exchange 2013 jounal mailbox for Exchange 2010 users. It worked.
So you can migrate journal mailbox to Exchange 2013 firstly based on this test.
Best regards,
Belinda Ma
TechNet Community Support

Outlook clients cannot connect Exchange 2013 cutover from 2010

Hello,
My company has been running an Exchange 2013/2010 coexistence. Currently, Exch 2013 (2mbx and 1 CAS) utilizes "mail2.domain.com" for the name space. Exch 2010 (1MBX 1 CAS) uses "mail.domain.com"
We recently attempted to cutover external and internal DNS to point "mail.domain.com" and "autodiscover.domain.com" to the Exch 2013 server.
We changed all virtual directories on 2013 to use "https://mail.domain.com/owa" (ECP, EWS, etc. were changed too) for the internal and external URL. The Exch 2010 virtual directories internal URL are set to "https://internalFQDN.domain.com/owa"
the external URLs are $null
Both CAS servers were setup to use Outlook Anywhere since this is how 2013 proxies to 2010. The internal URLs for both were set to "mail.domain.com" IIS authentication Methods (Basic, NTLM). ClientAuthenicsationMethod: NTLM.
For both servers the autodiscoverserviceinternaluri was set to: https://autodiscover.domain.com/autodiscover/autodiscover.xml
The 2013 server has two SSL certificates installed. One is a wildcard cert for "*.domain.com" and the other includes our SANs (mail.domain.com, mail2.domain.com, webmail.domain.com, autodiscover.domain.com) it also includes the FQDN for the 2010
and 2013 CAS servers.
I'm speaking in the past tense because we had to roll back. The problem was no Outlook user could connect. This goes for mailboxes hosted on the Exchange 2013 and 2010 servers. The error was: "Cannot
open your default e-mail folder" to "The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete".
Everything else worked fine during the cutover. OWA 2013 login page proxied 2010 logins properly, Outlook 2011 could connect with EWS fine, Active-Sync worked without issues too.
It was only the Outlook 2010 and 2013 clients that could not connect.
We rolled back and everything is working as it was before with the separate namespace. That leads me to think it's something with Outlook Anywhere (RPC/HTTPS)
but the settings seem correct unless I'm missing something. Any help is appreciated.
Thanks!

Hard to say. I've had to change the router to point to the old server as mail wasnt getting in. But OWA did seem ok, although I couldn't send messages... I could only see the inbox and contacts etc.

Exchange 2013 Issue: Outlook 2010 auto populating the From Tab when forwarding email

Exchange 2013 Issue: Outlook 2010 auto populating the From Tab when forwarding email
I am running Exchange 2013 and I have an end user who connects to it via Outlook 2010. All was going well till he went to forward an email and he noticed that the From button appeared and auto populated the sender's email address.
I have clicked the Empty Auto Complete List in Outlook's Send messages... still displayed the From tab when forwarding.
I recreated the profile in outlook... same thing.
I created the profile with outlook 2013... same thing.
There is only one user profile setup in Outlook.
(I know the from tab usually appears when you have multiple profiles setup in Outlook and/or when you configure the "From" tab.)
I opened the end user's email in Exch 2013's OWA... what was different here was when I clicked on the email and it opened, it did NOT have the Reply or Forward option... and it displayed as a "Draft" email.
Does anyone have any ideas?

So are you saying that the from button is filling the option with the original senders address (eg the person who sent the message to your user), or that it's filling in the your users address (in which case I don't understand what the issue is, since
it IS going from your user)?

Publish Exchange 2013 using UAG 2010 Sp4

Hi,
We need to publish Exchange 2013 through UAG 2010. But we are not getting any dedicated link for UAG 2010 to publish Exchange 2013. we have UAG 2010 with SP4.
Is there any Step by step UAG 2010 configuration link to publish Exchange 2013?
Thanks
jitender

Hi Jitender,
Based on my knowledge, publishing Exchange 2013 with UAG 2010 is similar with publishing Exchange 2010.
I find a related Blog and Guid for your reference:
1. Publishing Exchange Server 2010 with Forefront UAG and TMG
http://blogs.technet.com/b/exchange/archive/2010/07/16/publishing-exchange-server-2010-with-forefront-uag-and-tmg.aspx
2. Publishing Exchange Server 2010 with Forefront Unified Access Gateway 2010 and Forefront Threat Management Gateway 2010
http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=8946
Please also notice the System requirement of both Exchange 2013 and UAG 2010.
System Requirement
Exchange 2013
http://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
UAG 2010 SP4
Supported Operating System
Windows Server 2008 R2
Servers running Forefront UAG and SP4 require the following:
• Windows Server 2008 R2 Standard, Windows Server 2008 R2 Enterprise, or Windows Server 2008 R2 DataCenter.
• Microsoft Forefront Threat Management Gateway (TMG) 2010 Service Pack 2
Thanks
Mavis Huang
TechNet Community Support

Exchange 2013 with Outlook 2010 anywhere - Public Folders disappear from Outlook favourites

Hi,
we have a 3 server Exchange 2013 SP1 DAG published with Forefront TMG.
Outlook 2010 anywhere connection works fine (only anywhere connection is possible, there are no clients in the exchange server AD).
The users are adding public folders to their local Outlook favorites. In about 10% of the Outlook starts, those public folders are missing in the favorites. Local favorites folders are still there, public folders are connected.
After restarting the Outlook a few times, the favorites are back.
Deleting the outlook.xml brought no success, the favorites seem to be saved somewhere on the exchange server.
Outlook 2010 is up to date, all hotfixes are installed.
There are no related entries in servers or clients eventlogs, the logs of the TMG server are normal.
Does anyone have a simular behavior?
Thanks in advance!

Hi,
According to your description,it is clear that something got corrupted, but it is hard to say directly what caused it. However, there are a few troubleshooting steps to determine what caused it and you can also make a backup of your Favorite Folders list
so you can easily restore it when it still happens.
Pleaser refer to the following article:
Favorite Folders empty upon restart
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.
Hope this helps!
Thanks.
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Niko Cheng
TechNet Community Support

Server 2012 and Exchange 2013 Migration from SBS 2011

Server UpgradeI'm migrating an SBS 2011 server to a new machine with Server 2012 R2 and a Hyper-V server running Exchange 2013. I've set up the new machine, all is running well in a test environment. I now want to migrate the old server to new. These are the steps I'm going to take and I wanted advice for any modifications or errors. 1. Demote DC on Server 2012 that I set up to test. 2. Join new Server 2012 to existing SBS 2011 domain. 3. Promote Server 2012 to DC. 4. Join the Hyper-V Server 2012 to the Server 2012 domain.5. Migrate Exchange 2010 on the SBS 2011 Server to Exchange 2013. 6. Transfer FSMO role from SBS 2011 Server to Server 2012 DC. I'll copy shared data files using robocopy.The only things I'm not sure about is the FSMO order, when to do that and the fact that I already have Exchange 2013 installed in the test...
This topic first appeared in the Spiceworks Community

I recently acquired a SuperMicro chassis that has a SAS2 expander backplane. It has SFF-8087 ports on it.http://www.supermicro.com/manuals/other/BPN-SAS2-846EL.pdfI made a post on another forum and someone mentioned that the card couldn't be used with that backplane since it's a SATA controller, however, the backplane is both SAS and SATA device compliant, it's only the RAID controller, as far as I know, that is a "SATA II" controller, and not a SAS controller.So, I couldn't find anything in the official documentation of this controller on whether or not it was able to control SAS devices. The card itself has a 3 SFF-8087 ports though, couldn't this theoretically still be used with a SFF-8087 to SFF-8087 cable(seen below)since the backplane is a SAS/SATA backplane?...

Exchange 2013 Mailbox Using 2010 Public Folders

Firstly, we will not be migrating completely to Exchange 2013 public folders for quite a while. Our first Ex2013 server is in a small branch office and won't be appropriate to hose the PF's for the entire company. Our environment consists of
8 Ex2010 servers and now the one Ex2013. I setup a test mailbox on the 2013 server and it access a 2010 PF database on another server just fine. How is that server discovered, and can we specify which one it uses? I understand the way 2013
public folders are moving but is there a downside to leaving our configuration this way for a long period of time?

Yes, the procedure should be followed to move mailbox first. Once you have successfully moved all the mailbox to new exchange server, you can migrate public folder after that.
You can also checekout this thread related to public folder migration from exchange 2010 to 2013 :
http://social.technet.microsoft.com/Forums/exchange/en-US/b7a35a45-9b74-4910-9dc3-c997bc71f03f/migration-form-exchange2010-to-exchange2013?forum=exchangesvrdeploy
Further, for a better convenience, you can also take a look at this application (http://www.exchangemailboxmigration.com/) which would be a good approach while migrating mailboxes and public folders
between two exchange server. It ensures about the data security and email contents during the completion of entire migration process.

First Exchange 2013 server in 2010 Deployment - 2010 edge is routing SOME inbound mail to new server where it fails.

I have a Barracuda filter receiving all inbound internet mail which delivers to the edge server (both in DMZ). I have one 2010 edge server and one 2010 ht,cas,mailbox server. I have added a 2013 server and started working
on configuring virtual directories. This is a far as I have gotten. Goal is once new box is working to move all mailboxes to 2013 server and remove 2010 mail box server and keep Barracuda and 2010 edge server to pass mail to the 2013 box.
My issue is the edge server is already passing inbound internet mail to the new 2013 server. I see the mail being accepted by the Barracuda and message tracking on the edge shows it as delivered to the new 2013 server, but mailbox
users never receive.
Is my solution to simply create a new send connector from the 2013 server to the 2010 box or could this be something else?
And why is it delivering to a server with now mailboxes on it yet?
Thank you for any help
dean

Hello Dean,
I understand that the message tracking log indicates the email delivered to Exchange 2013 server. Please check the message tracking log on both Exchange 2013 server and Exchange 2010 server.
How about the result? Have you created new 2013 mailbox and tested if it works?
As for the send connector, actually an intra-org send connector will be involved for internal mail flow within an organization. So there is no need to create another send connector.
In addition, I’d like to share you an article about Edge Subscriptions:
Title:
Understanding Edge Subscriptions
Link:
http://technet.microsoft.com/en-us/library/aa997438(v=exchg.141).aspx
Regards,

Exchange 2013 coexistence with 2010

Who all has had problems with 2013 proxing requests to 2010? I tried a migration and couldn't even get OWA to proxy or redirect. I was receiving errors like this:
Autodiscover would fail for 2010 users but fine for 2013 users:
HTTP Response Headers:
request-id: d1e90875-53e1-4be5-ad64-24a9a5eb0c19
X-CasErrorCode: ServerNotFound
Persistent-Auth: true
X-FEServer: CPC8000-CAS01
Content-Length: 0
Cache-Control: private
Date: Sun, 01 Jun 2014 01:22:50 GMT
Server: Microsoft-IIS/8.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Elapsed Time: 153 ms
and
Created a new user on 2010 and login to OWA does this:
Microsoft.Exchange.Data.Storage.NotSupportedWithServerVersionException
I've tried it multiple ways and I've actually done this migration before. Either way this was the same AD site, and I checked/tried the following:
Checked AD Replication and it was fine
Exchange 2013 was at SP1
Exchange 2010 was at SP3 Rollup 6
Exchange 2010 was a single server with CAS/HUB/Mailbox
Exchange 2010 was not using a CAS Array
Exchange 2013 had two mailbox servers in a DAG and one CAS server
I've tried both setting all external URL's on 2010 to https://legacy.domain.com/* and also not setting External URL's. Neither fixed the issue
https://legacy.domain.com/autodiscover/autodiscover.xml worked fine (600 invalid request response) and https://owa.domain.com/autodiscover/autodiscover.xml worked fine too (2013) but Test Connectivity and Outlook didn't work
I checked for bad HTTP Redirections on new and old servers and made sure there were no HTTP redirections added
Would really love some input to see what I did wrong. Thank you!

Thanks for responding!
The internal URL's for 2010 I set to https://legacy.domain.com/*. So the OWA internal URL is https://legacy.domain.com/owa. The external URL was set to the same and I also tried not settings the external URL at all.
Just FYI.. legacy.domain.com pointed to the internal IP when using internal DNS servers and legacy.domain.com pointed to the external IP when external which all went to the 2010 server
The detailed error from ExRCA is listed above. It failed autodiscovered and wouldn't continue. The thing is autodiscover seemed to work fine going to 2010 and to 2013 but it failed when it tried to proxy to 2010. So if a mailbox was on 2013 then ExRCA was
fine. If I opened a url to https://legacy.domain.com/autodiscover/autodiscover.xml and logged in I got the XML 600 error like I should. This is what autodiscover said:
HTTP Response Headers:
request-id: d1e90875-53e1-4be5-ad64-24a9a5eb0c19
X-CasErrorCode: ServerNotFound
Persistent-Auth: true
X-FEServer: CPC8000-CAS01
Content-Length: 0
Cache-Control: private
Date: Sun, 01 Jun 2014 01:22:50 GMT
Server: Microsoft-IIS/8.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Elapsed Time: 153 ms

OWA problem Exchange 2013 coexistence with 2010

Hi all,
I am in the midst of a migration from a single Exchange 2010 server to a two-server Exchange 2013 environment (both servers are CAS and MBX with DAG). Everything seems to work fine. I can access OWA on 2013 for mailboxes already moved to 2013, I use ActiveSync
successfully but I cannot for the life of me figure out how to enable OWA 2010 proxying through 2013. I have checked many websites, forums etc. for it, I changed Authentication Methods back and forth and did everything I can think of but still... when trying
to access OWA with a mailbox that is still on 2010 it fails with the following error:
something went wrong
A problem occurred while you were trying to use your mailbox.
X-OWA-Error: Microsoft.Exchange.Data.Storage.NotSupportedWithServerVersionException
X-OWA-Version: 15.0.913.21
X-FEServer: <name of 2013 server>
X-BEServer: <name of 2013 server>
Maybe I should add that the new 2013 servers are installed in a completely different AD site which is connected through VPN to the 2010 site. In the new site I also have a loadbalancer in front of the 2013 servers.
Actually I am still not sure if I need a different address in Exchange 2013 for OA, OWA and so on then in Exchange 2010. If I understood correctly there is no need for a legacy namespace anymore so I used the same URL for OA, OWA ... in both environments.
This seems to be in conflict with the requirement that the OA URL in Exchange 2010 should point to the 2013 URL?!?
Any help is greatly appreciated!
Best regards
Daniel

Hi,
How do you configure your Exchange virtual directories in Exchange 2010 and Exchange 2013? Please run the following command to provide detailed information about it:
Get-OwaVirtualDirectory | Select Identity,name,Internalurl,ExternalUrl,*auth*
According to your description, I noticed that it is set the same URL for OWA using. If the ExternalUrl
for OWA 2010 is configured in your coexistence environment, please remove it. Then when external Users access OWA 2010, they can use OWA 2013 URL and be automatically proxy to Exchange 2010 and access their mailboxes.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 transition to Exchange Online

Hello all,
I'm needed to transition mine Exchange 2013 from on premises to Exchange online. I will use cutover migration, but I have question related to resource mailbox:
Will resource mailboxes, like rooms etc. will be migrated in same batch as everything else?
BR,
Janis

Hi,
As far as I know, Resource Mailboxes (Room, Shared, Equipment) is moved between on-premise Exchange servers in the exact same way as User Mailboxes:
http://social.technet.microsoft.com/Forums/exchange/en-US/f60d736d-0d45-4c27-adc8-a7e04afdb6e3/resource-mailboxes-and-contacts-move-during-transition-to-exchange-2013?forum=exchangesvrdeploy
Based on my research, there is nothing special for resource mailboxes in the transition from on-premise to Exchange online:
http://technet.microsoft.com/en-us/library/jj898486(v=exchg.150).aspx
And you’re welcomed to confirm it on our Exchange online forum:
http://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

OWA receives mail long before Outlook (Exchange 2013 with Outlook 2010 and 2013)

I recently upgraded my Exchange environment to Exchange 2013 SP1. The Outlook users are now experiencing a delay when receiving email. When they do arrive they appear in batches, often 20-45 minutes after they were sent, from a mailbox on the same server.
Additionally, the mail appears instantly when you monitor the inbox using OWA. The users are experiencing this on both Outlook 2010 and 2013 clients configured in both cached and non-cached modes. This appears to be a problem with Outlook connecting to Exchange.
Any suggestion about how to correct this would be greatly appreciated. Thanks!

Hi,
From your description, when users use OWA, they can receive emails normally. But if they use Outlook 2010 or Outlook 2013, there is a delay in receiving emails.
I recommend you use the Outlook safe mode to determine whether the problem is caused by add-ins. Also, please make sure users have installed the Outlook latest Service Pack.
If the issue persist, please create a new profile and check the result.
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Exchange 2013 transition from 2010

Similar Messages

Maybe you are looking for