Exchange 2010 & 2013 coexistence mail flow between servers

Hi Everyone,
I have an exchange 2010 server which I am trying to move away from. I have installed 2013 and it seems to be working well. I have successfully moved a mailbox over to 2013 without any issues.
The problem i have at the moment is that a user who has their mailbox on the 2010 server can send to the user on the 2013 server. However the 2013 user cannot reply.
Any ideas?

Yes, some issues with client connectivity are related to Outlook.
Exchange Blog:
www.ntweekly.com
MCSA, MCSE, MCITP:SA, MCITP:EA, MCITP:Enterprise Messaging Administrator 2010,MCTS:Virtualization

Similar Messages

Outlook client requirements and Exchange 2010/2013 coexistence

Good morning!
A question regarding Exchange 2010/2013 coexistence and the Outlook client requirement. I am upgrading and about to install Exhange 2013 into an existing Exchange 2010 Org. The current 2010 Org is patched to SP-3 and Outlook Anywhere is currently disabled.
I have Outlook clients that do not yet meet the minimun requirements for 2013 (Outlook 2007/2010). When I install my first 2013 server will it effect the current downlevel clients? The mailboxes are still in 2010 so my thoughts were since the Office upgrade
including Outlook has not yet taken place I didn't want to wait for them to at least get 2013 into the Org. The 2013 server should effect the clients until I configure the CAS on 2013 and only when they are at the proper version, is this correct? Does Outlook
Anywhere need to be first enabled and configured on the 2010 CAS before I attempt the confgiuration on the 2013 CAS? I just dont want to install 2013 and have Outlook connectivity issues right out of the gate...
Thanks in advance!

Outlook 2007 and 2010 are supported for Exchange 2013, you just need to push out the latest patches.
http://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
If you configure the URLs properly in Exchange 2013 to URLs that point to the Exchange 2010 servers, your clients shouldn't try to talk to the Exchange 2013 server.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange 2010 - 2013 Coexistence Issues

I am migrating from Exchange 2010 to Exchange 2013, the Exchange 2013 is built in a different Geo-location site with its dedicated domain controllers in the new site. I have confirmed the mail flow between Exchange 2010 and 2013 mailboxes. I am able to discover
Exchange 2010 servers from 2013 environment via Get-ExchangeServer shell command. However, I am not to discover Exchange 2013 servers from 2010 environment.
I need to configure Outlook Anywhere and Service Connection Point (Autodiscover) on Exchange 2010 to accept connections from Exchange 2013 servers.
Any suggestions would be much appreciated, thanks!

Hi ,
Please have a look in to the below mentioned blog after reading that blog i came to know few things .
I am not sure ,i thought exchange 2013 servers will not be displayed in exchange 2010 management shell.
Better and advisable method is to configure your exchange 2010 and 2013 servers via EAC or Shell in exchange 2013.
http://exchangeserverpro.com/exchange-server-2010-2013-migration-managing-co-existence-environment/
Taken from the above blog :
You can’t use the Exchange 2010 EMC to manage Exchange 2013 objects and servers. While customers upgrade to Exchange 2013, we encourage them to use the EAC to:
Manage Exchange 2013 mailboxes, servers, and corresponding services.
View and update Exchange 2010 mailboxes and properties.
View and update Exchange 2007 mailboxes and properties.
We encourage customers to use Exchange 2010 EMC to create Exchange 2010 mailboxes.
We encourage customers to use Exchange 2007 EMC to create Exchange 2007 mailboxes.
Customers can continue to perform management tasks using the Exchange Management Shell and script tasks.
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Exchange 2010/2013 coexistence: OWA proxy not working properly ":-( Something went wrong"

Hi
Exchange 2010 users are NOT able to connect to their mailboxes when they go through exchange 2013 OWA address. We get a message that says following ---> "Something went wrong"
Following is our URL. The address is pointing to 2013 CAS loadbalancer VIP. Outlook anywhere is working fine. What is going on?
Important: All my exchange 2010 / 2013 URIs are the same as suggested by Microsoft (Owa, ecp, activesync, ews, autodiscover): --> mail.domain.com/XXX

Hello Rawa,
Can you log on Exchange 2010 OWA using its localhost address?
Please make sure the intenralurl value is set to Exchange 2010’s local host name and set the Externalurl to Null.
http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Search-Mailbox not attaching the infected emails in target folder and deleting the contents in exchange 2010 & 2013 coexistence

Dear All,
I have an issue with deleting circulated spam emails in my environment through search-mailbox
We have Exchange 2010 & 2013 CU5 environment
I followed the search and destroy document for exchange 2010
http://windowsitpro.com/exchange-server-2010/search-destroy-email-content-exchange-2010
Added the user to Discovery Management group
Created a new role group as below
New-RoleGroup "Mailbox Import-Export Management" -Roles "Mailbox Import Export"
Add-RoleGroupMember "Mailbox Import-Export Management" -Member Administrator
I ran the below commands
Search-Mailbox -Identity "[email protected]" -SearchQuery "Subject:'report'" -TargetMailbox "Administrator" -TargetFolder "Filter" -LogOnly -LogLevel Full
The above command gets completed successfully and sends the log report however im unable to see any attachments
Similarly the deletecontent also gets completed successfully and logs result. But it does not delete the infected emails
Search-Mailbox -Identity "[email protected]" -SearchQuery "Subject:'report'" -TargetMailbox "administrator" -TargetFolder "filter" -deletecontent -LogLevel Full
Any idea why it is not fetching the infected emails in zip file and why it is not deleting but it is able to log in the target folder
Any help much appreciated
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)

Hi All
I managed to find the solution. Below command helped me in solving the issue
get-mailbox -ResultSize unlimited -IgnoreDefaultScope | search-mailbox -SearchQuery ‘Subject:"virus infected"’ -LogOnly -TargetMailbox administrator -TargetFolder filter -LogLevel Full
get-mailbox -ResultSize unlimited -IgnoreDefaultScope | search-mailbox -SearchQuery ‘Subject:"virus infected"’ -TargetMailbox administrator -TargetFolder filter -deletecontent -LogLevel Full
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)

Exchange Server 2013 OAB Web Distribution Configuration in Exchange 2010 & 2013 Coexistence.

Hi,
We have OAB Issue for Exchange 2010 Users in our Organization.
We have Exchange 2010 and Exchange 2013 Coexistence.While Checking in Exchange Server 2010 Server OAB properties in Org Configuration--> Mailbox-->OAB Properties -->Distribution we are not seeing any CAS servers and Its Grayed Out.
Please let us know How to add Exchange 2010 CAS in Exchange 2013 Web distribution.

They made alot changes with the OAB in Exchange 2013, and it doesn't really function in the same manner as it did in 2010. It might be best to take a look at the following blog posts from the Exchange Team, they should give you a better understanding
on how it works and how to manage it going forward.
http://blogs.technet.com/b/exchange/archive/2012/10/26/oab-in-exchange-server-2013.aspx
http://blogs.technet.com/b/exchange/archive/2013/01/14/managing-oab-in-exchange-server-2013.aspx
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

Missed Call Notification in Exchange 2010/2013 coexistence mode

Dear all,
Context:
Lync 2013 Enterprise Voice, Exchange 2010 and Exchange 2013 in coexistence mode
Waiting complete migration, some users are always on exchange 2010
UM role is installed on both exchange server
The exchange servers UM are attached to only one UM Dial Plan
Scenario :
A call to a lync user. The caller hang-up before user announcement
Problem: Missed call notification doesn't work for user on Exchange 2010 (it's work fine for user on Exchange 2013)
Voice Messaging works fine
Troubleshooting / SIP Traces:
SIP Info is always send to Exchange 2013 even if user is on exchange 2010
SIP Info sent from Lync FE to Exchange 2013 UM :
TL_INFO(TF_PROTOCOL) [0]6330.3AE8::02/12/2015-12:25:23.575.015c018e (S4,SipMessage.DataLoggingHelper:sipmessage.cs(774))[1718622663]
>>>>>>>>>>>>Outgoing SipMessage c=[<SipTlsConnection_13ECA29>], 192.168.5.110:49786->192.168.5.203:5061
INFO sip:outlook.mydomain.com:5061;ms-fe=exchange2013-UM.mydomain.localdomain;transport=Tls SIP/2.0
FROM: <sip:A410AA79-D874-4e56-9B46-709BDD0EB850>;epid=8C75BE2D95;tag=35c2d8a65a
TO: <sip:exchange2013-UM.mydomain.localdomain;opaque=app:rtcevent;transport=tls>;epid=C4C2F4F6BA;tag=ac126413f
CSEQ: 43 INFO
CALL-ID: 535a07e2-8e82-4d13-8e03-bf43ad97602d
MAX-FORWARDS: 70
VIA: SIP/2.0/TLS 192.168.5.110:49786;branch=z9hG4bKd66442be
CONTACT: <sip:LyncFE-2013.mydomain.localdomain;transport=Tls>
CONTENT-LENGTH: 454
USER-AGENT: RTCC/5.0.0.0 Inbound Routing (Microsoft Lync Server 2013 5.0.8308.726)
CONTENT-TYPE: application/ms-rtc-usernotification+xml
- <UserNotification>
       <User>sip:[email protected]</User>
       <EumProxyAddress>EUM:[email protected];phone-context=UMDialPlan.mydomain.localdomain</EumProxyAddress>
       <Time>2015-02-12 12:25:23Z</Time>
       <Template>RtcDefault</Template>
    + <Event type="missed">
</UserNotification>
------------EndOfOutgoing SipMessage
Answer from Exchange 2013 UM
TL_INFO(TF_PROTOCOL) [1]6330.2DF4::02/12/2015-12:25:23.642.015c2481 (S4,SipMessage.DataLoggingHelper:sipmessage.cs(774))[1718622663]
<<<<<<<<<<<<Incoming SipMessage c=[<SipTlsConnection_13ECA29>], 192.168.5.110:49786<-192.168.5.203:5061
SIP/2.0 200 OK
FROM: <sip:A410AA79-D874-4e56-9B46-709BDD0EB850>;tag=35c2d8a65a;epid=8C75BE2D95
TO: <sip:exchange2013-UM.mydomain.localdomain;opaque=app:rtcevent;transport=tls>;tag=ac126413f;epid=C4C2F4F6BA
CSEQ: 43 INFO
CALL-ID: 535a07e2-8e82-4d13-8e03-bf43ad97602d
VIA: SIP/2.0/TLS 192.168.5.110:49786;branch=z9hG4bKd66442be
CONTENT-LENGTH: 0
SUPPORTED: ms-dialog-route-set-update
SERVER: RTCC/5.0.0.0 MSExchangeUM/15.00.0995.028
ms-diagnostics-public: 15642;reason="Lync SIP INFO notifications are not supported for legacy users. User: EUM:[email protected];phone-context=UMDialPlan.mydomain.localdomain"
------------EndOfIncoming SipMessage
Gerald Cheminant

Hi,
This behavior is by design. Exchange 2010 server is not going to accept any SIP messages from Exchange 2013 server because it is not listed as UM IP Gateway. Therefore, even if Exchange 2013 redirected the SIP INFO packet to Exchange 2010, it will fail.
During migration\coexistance scenario, this feature (Missed call notifications from Lync server) will not work for legacy users whose mailbox is still in Exchange 2010.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Exchange 2010 to 2003 mail flow failing

Scenario: Just installed exchange 10 to coexist with an existing exchange 03 organization with two 03 servers
Problem: Mail flow fails from 10 to 03 but for just one of the 03 servers (slave). Mail flow works from 10 to 03 (master) just fine.
Variables:
Single forest, single domain
Exchange 2003 master – Ex03A (AD site A)
Exchange 2003 slave – Ex03B (AD site B)
Exchange 2010 – Ex10Z (AD site A)
Current mail flow:
Ex03A <-> Ex03B
Ex03A <-> Ex10Z
Ex03B -> Ex10Z
Ex10Z -fails> Ex03B
Output from get-routinggroupconnector | fl ran from Ex10Z
RunspaceId : 4d5dc855-1b62-4d39-9aa7-fb027f25edda
TargetRoutingGroup : First Routing Group
Cost : 1
TargetTransportServers : {Ex03A}
ExchangeLegacyDN : /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuratio
n/cn=Connections/cn=Ex10Z-Ex03A
PublicFolderReferralsEnabled : True
SourceRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)
SourceTransportServers : {Ex10Z}
HomeMTA : Microsoft MTA
HomeMtaServerId : Ex10Z
MaxMessageSize : unlimited
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : Ex10Z-Ex03A
DistinguishedName : CN=Ex10Z-Ex03A,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routin
g Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=
First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=company,DC=c
om
Identity : Ex10Z-Ex03A
Guid : ae599ccb-bdfb-4765-b846-a9066ad8dcfb
ObjectCategory : company.com/Configuration/Schema/ms-Exch-Routing-Group-Connector
ObjectClass : {top, msExchConnector, msExchRoutingGroupConnector}
WhenChanged : 2/7/2015 7:40:30 AM
WhenCreated : 2/7/2015 7:40:30 AM
WhenChangedUTC : 2/7/2015 3:40:30 PM
WhenCreatedUTC : 2/7/2015 3:40:30 PM
OrganizationId :
OriginatingServer : DC.company.com
IsValid : True
RunspaceId : 4d5dc855-1b62-4d39-9aa7-fb027f25edda
TargetRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)
Cost : 1
TargetTransportServers : {Ex10Z}
ExchangeLegacyDN : /o=First Organization/ou=First Administrative Group/cn=Configuration/cn=Connections/cn=G
JL2-Ex10Z
PublicFolderReferralsEnabled : True
SourceRoutingGroup : First Routing Group
SourceTransportServers : {Ex03A}
HomeMTA : Microsoft MTA
HomeMtaServerId : Ex03A
MaxMessageSize : unlimited
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : Ex03A-Ex10Z
DistinguishedName : CN=Ex03A-Ex10Z,CN=Connections,CN=First Routing Group,CN=Routing Groups,CN=First Adm
inistrative Group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,C
N=Services,CN=Configuration,DC=company,DC=com
Identity : Ex03A-Ex10Z
Guid : 382fae0f-beed-4003-adaf-237a2dddd91b
ObjectCategory : company.com/Configuration/Schema/ms-Exch-Routing-Group-Connector
ObjectClass : {top, msExchConnector, msExchRoutingGroupConnector}
WhenChanged : 2/7/2015 7:40:30 AM
WhenCreated : 2/7/2015 7:40:30 AM
WhenChangedUTC : 2/7/2015 3:40:30 PM
WhenCreatedUTC : 2/7/2015 3:40:30 PM
OrganizationId :
OriginatingServer : DC.company.com
IsValid : True
Output from get-message | fl on Ex10Z where the queue is filling up:
RunspaceId : 4d5dc855-1b62-4d39-9aa7-fb027f25edda
Subject : Test
InternetMessageId : <[email protected]>
FromAddress : [email protected]
Status : Ready
Size : 5.982 KB (6,126 bytes)
MessageSourceName : FromLocal
SourceIP : 255.255.255.255
SCL : -1
DateReceived : 2/7/2015 3:57:10 PM
ExpirationTime : 2/9/2015 3:57:10 PM
LastError : There is currently no route to the mailbox database.
RetryCount : 0
Recipients :
ComponentLatency :
MessageLatency : 15:52:27.3487757
DeferReason : None
Priority : Normal
MessageIdentity : ex10Z\Unreachable\103
Queue : ex10Z\Unreachable
Identity : ex10Z\Unreachable\103
IsValid : True
Proposed solution:
In order to fix mail flow from Ex10Z -> Ex03B, run the following command in Ex10Z EMS
New-RoutingGroupConnector -Name "Ex10Z-Ex03B" -SourceTransportServers "Ex10Z.company.com" -TargetTransportServers
"Ex03B.company.com" -Cost 100 -Bidirectional $true
Restart transport service on Ex10Z, restart smtp service on Ex03A and Ex03B
Will this proposed solution work or should I be looking elsewhere?

That didnt work.
Here is the new get-routinggroupconnector | fl. Interesting that it created two Ex10Z-Ex03B identities despite
me issuing the Bidirectional flag. Shouldnt there be one for Ex03B-Ex10Z?
RunspaceId : 4d5dc855-1b62-4d39-9aa7-fb027f25edda
TargetRoutingGroup : First Routing Group
Cost : 1
TargetTransportServers : {Ex03A}
ExchangeLegacyDN : /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuratio
n/cn=Connections/cn=Ex10Z-Ex03A
PublicFolderReferralsEnabled : True
SourceRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)
SourceTransportServers : {Ex10Z}
HomeMTA : Microsoft MTA
HomeMtaServerId : Ex10Z
MaxMessageSize : unlimited
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : Ex10Z-Ex03A
DistinguishedName : CN=Ex10Z-Ex03A,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Routin
g Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=
First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=company,D C=c
om
Identity : Ex10Z-Ex03A
Guid : ae599ccb-bdfb-4765-b846-a9066ad8dcfb
ObjectCategory : company.com/Configuration/Schema/ms-Exch-Routing-Group-Connector
ObjectClass : {top, msExchConnector, msExchRoutingGroupConnector}
WhenChanged : 2/7/2015 7:40:30 AM
WhenCreated : 2/7/2015 7:40:30 AM
WhenChangedUTC : 2/7/2015 3:40:30 PM
WhenCreatedUTC : 2/7/2015 3:40:30 PM
OrganizationId :
OriginatingServer : DC.company.com
IsValid : True
RunspaceId : 4d5dc855-1b62-4d39-9aa7-fb027f25edda
TargetRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)
Cost : 1
TargetTransportServers : {Ex10Z}
ExchangeLegacyDN : /o=First Organization/ou=First Administrative Group/cn=Configuration/cn=Connections/cn=G
JL2-Ex10Z
PublicFolderReferralsEnabled : True
SourceRoutingGroup : First Routing Group
SourceTransportServers : {Ex03A}
HomeMTA : Microsoft MTA
HomeMtaServerId : Ex03A
MaxMessageSize : unlimited
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : Ex03A-Ex10Z
DistinguishedName : CN=Ex03A-Ex10Z,CN=Connections,CN=First Routing Group,CN=Routing Groups,CN=First Adm
inistrative Group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,C
N=Services,CN=Configuration,DC=company,DC=com
Identity : Ex03A-Ex10Z
Guid : 382fae0f-beed-4003-adaf-237a2dddd91b
ObjectCategory : company.com/Configuration/Schema/ms-Exch-Routing-Group-Connector
ObjectClass : {top, msExchConnector, msExchRoutingGroupConnector}
WhenChanged : 2/7/2015 7:40:30 AM
WhenCreated : 2/7/2015 7:40:30 AM
WhenChangedUTC : 2/7/2015 3:40:30 PM
WhenCreatedUTC : 2/7/2015 3:40:30 PM
OrganizationId :
OriginatingServer : DC.company.com
IsValid : True
RunspaceId : 4d5dc855-1b62-4d39-9aa7-fb027f25edda
TargetRoutingGroup : First Routing Group
Cost : 100
TargetTransportServers : {Ex03B}
ExchangeLegacyDN : /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuratio
n/cn=Connections/cn=Ex10Z-Ex03B
PublicFolderReferralsEnabled : True
SourceRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)
SourceTransportServers : {Ex10Z}
HomeMTA : Microsoft MTA
HomeMtaServerId : Ex10Z
MaxMessageSize : unlimited
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : Ex10Z-Ex03B
DistinguishedName : CN=Ex10Z-Ex03B,CN=Connections,CN=Exchange Routing Group (DWBGZMFD01QNBJR),CN=Rout
ing Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,C
N=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=company,D C
=com
Identity : Ex10Z-Ex03B
Guid : 37a9f53c-2166-440c-b54b-23b165323ae3
ObjectCategory : company.com/Configuration/Schema/ms-Exch-Routing-Group-Connector
ObjectClass : {top, msExchConnector, msExchRoutingGroupConnector}
WhenChanged : 2/8/2015 8:09:08 AM
WhenCreated : 2/8/2015 8:09:08 AM
WhenChangedUTC : 2/8/2015 4:09:08 PM
WhenCreatedUTC : 2/8/2015 4:09:08 PM
OrganizationId :
OriginatingServer : DC.company.com
IsValid : True
RunspaceId : 4d5dc855-1b62-4d39-9aa7-fb027f25edda
TargetRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR)
Cost : 100
TargetTransportServers : {Ex10Z}
ExchangeLegacyDN : /o=First Organization/ou=First Administrative Group/cn=Configuration/cn=Connections/cn=G
JLSRVLVMX1-Ex03B
PublicFolderReferralsEnabled : True
SourceRoutingGroup : First Routing Group
SourceTransportServers : {Ex03B}
HomeMTA : Microsoft MTA
HomeMtaServerId : Ex03B
MaxMessageSize : unlimited
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : Ex10Z-Ex03B
DistinguishedName : CN=Ex10Z-Ex03B,CN=Connections,CN=First Routing Group,CN=Routing Groups,CN=First A
dministrative Group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange
,CN=Services,CN=Configuration,DC=company,DC=com
Identity : Ex10Z-Ex03B
Guid : c8cd8eea-4ad6-47b4-bef5-9fb93288bca3
ObjectCategory : company.com/Configuration/Schema/ms-Exch-Routing-Group-Connector
ObjectClass : {top, msExchConnector, msExchRoutingGroupConnector}
WhenChanged : 2/8/2015 8:09:08 AM
WhenCreated : 2/8/2015 8:09:08 AM
WhenChangedUTC : 2/8/2015 4:09:08 PM
WhenCreatedUTC : 2/8/2015 4:09:08 PM
OrganizationId :
OriginatingServer : DC.company.com
IsValid : True

Exchange 2010/2013 coexistence published in TMG 2010

Environment:
Two Windows 2008 R2, Exchange 2010 SP3 servers, currently holding all mailboxes
Two Windows 2012 R2, Exchange 2013 SP1 servers, setup in progress
Two Windows 2008 R2, TMG 2010, V7.0.9193.540 publishing both Exchange 2010 servers.
Scenario:
I need to continue having Exchange 2010 setup in TMG as is as the mailbox migration to 2013 will take weeks if not months and I have a project requirement to have Exchange Database Availability Group (DAG) functionality for all mailboxes throughout the project,
so 4 servers are an absolute must. So I need to add Exchange 2013 in TMG and not just replace the 2010 setup with the 2013 setup and I cannot run one 2010 and one 2013 server.
Questions:
1. I currently only have 2 public IP addresses available to SMTP, mapped to the external interfaces of TMG, to allow my environment to be able receive emails on 4 Exchange servers (two 2010 and two 2013) I need to have 4 public IP addresses, is that correct?
2. Does anyone have a good general guide/blog for doing this (setting up Exchange 2013 in TMG in a coexistance scenario)?
This is nice, but doesn't really approach it from a coexistance scenario:
http://blogs.technet.com/b/exchange/archive/2012/11/21/publishing-exchange-server-2013-using-tmg.aspx
Thanks!

Hi Trana,
In TMG you can use single IP address to publish multiple Web address and below are the options which you can explore.
Hope your OWA ECP etc are Https
You need a SSL certificate which has all the URL SAN entry of both old and new Exchange server.
Create a listener and select the IP address (Say public IP address 195.219.x.x)
Link the SSL certificate
Public DNS entry
A record , Single IP
195.219.x.x
Point to
Owa1.exchange1.com   - Old Server
195.219.x.x
Point to
ECP1.exchange1.com     - Old Server
195.219.x.x
Point to
ECP2.exchange2.com      - New Server
195.219.x.x
Point to
Owa2.exchange2.com     - New Server
Create a Web publishing rule as below
Old server Exchange 1
Owa1.exchange1.com
ECP1.exchange1.com
One Web publishing Rule with all the URL added on it and link the Rule with the listener we created
Point the Web publishing to Exchange1.com server which is old
New server Exchange 2
Web publishing Rule with all the URL added on it and link the Rule with the listener we created
Point the Web publishing to Exchange2.com server which is New
ECP2.exchange2.com
Owa2.exchange2.com

External emails not received after shutdown of Exchange 2010 in coexistence with Exchange 2013

I have exchange 2013 and exchange 2010 in coexistence mode. All mailboxes have been moved to Exchange 2013 and firewall/spamfilters already pointed to Exchange 2013 CAS server. I can receive/send from and to external addresses, however when I shutted down
the Exchange 2010 all incoming external mails were not received. What could be the cause?

Start by re-checking how the device that takes the traffic from the external MX IP to internal is configured.
Sniff the traffic to ensure that it is hitting 2013 directly.
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.

Exchange 2010 - 2003 coexistence "unable to relay"

Hi
I have a customer with a Exchange 2010 / 2003 coexistence.
The Exchange 2010 has 3 CAS/HT servers.
When sending mails from 2003 to the outside world, one of the CAS/HT is giving me "unable to relay".
Right now I have removed it from the routing group connector, but do you have any ideas where to look?
BR
Steen

Hello,
If there is only AD site, the receive connector is not needed.
If there are multiple AD sites, when you send message to other AD sites, the receive conenctor is needed. If you send message from exchange 2003 to exchange 2010 or exchange 2010 to exchange 2003, the routing group connector is needed.
Cara Chen
TechNet Community Support

Exchange 2010-2013 co-existence - need for OWA/ActiveSync legacy namespace?

Hi all
Straight to the point: how to I update units that were set up manually with Exchange ActiveSync (pointing to owa.domain.com) with a temporary legacy namespace owa-legacy.domain.com, and then back to owa.domain.com?
Background: I did a test run of migrating a single-server installation from Exchange 2010 to Exchange 2013. As expected, after moving a user's mailbox to the new Exchange 2013 CAS with owa.domain.com still pointing to Exchange 2010, the user
was unable to log in at the Exchange 2010 OWA, and the ActiveSync unit was unable to fetch mail.
So I created a legacy namespace (owa-legacy.domain.com) and set this as the URL on the Exchange 2010 server, and waited for it to populate, then switched owa.domain.com to Exchange 2013. But the URL on ActiveSync units was still pointing to the wrong URL.
What did I overlook or not understand, or am I making migration more complex than needed?
Thanks for reading and best regards
/Maurice
PS: here were some of my pre-post readings:
Exchange 2003-2013 co-existence, even better
Exchange 2003-2013 co-existence,
Exchange 2010-2013 co-existence slides,
Upgrading ActiveSync to Exchange 2010,

Hi
Is that because External URL on Internet facing CAS servers were set to Blank，and Users are not able to get Updated URL
Please try to Add the External URL and made sure that all the required configurations are set Appropriately.
Also I suggest posting on Exchange ActiveSync Forum as well
http://social.technet.microsoft.com/Forums/en-US/home?forum=exchangesvrmobility
Cheers
If you have any feedback on our support, please click
here
Zi Feng
TechNet Community Support

Mail Flow between 2 AD Sites stops and EMC unavailable on the local server

Hello All,
I'm hoping you can help me find a solution to this recurring problem.
SYMPTOMS :
Mail Flow between 2 EXCH2010 servers in 2 different AD Sites (separate time zones) stops suddenly with no messages in the Event Viewer or exchange logs.
When this happens the EMC is unavailable on the local server : Error message Connection attempt to http://<servername> with the help of "Kerberos" failed : The connection to the remote server failed with the following error : Access Refused
Same error when opening Exchange Powershell
On the OTHER server (ie the one I can connect to in Site 2) I can :
1 - Connect to the first server using EMC with no problems
2 - Using mail queue viewer pointed at the server in Site 2 I can see the following error for email directed to the server in Site 1 : 451 4.4.0 Primary target address responded with: "235 00000804YIIF/<load of alphanumeric characters 80 or so long>
RECOVERY :
A reboot of the server allows access to the EMC and Powershell and mail flow once again starts.... until the next time
OTHER INFORMATION :
When in the above state, ran Exchange Management Troubleshooter which finds errors but cannot identify them : "Unknown Error" then stops !
Ran ExBPA : turns up nothing
Currently needing to reboot every day or so.
I though maybe the local server had a problem with resolving itself correctly, did some troubleshooting around that and turned up nothing. Even added itself to its hosts file in order to resolve its IP : Changed nothing.
Searched on the above error 451 4.4.0 etc and turned up nothing useful.
I think the Kerberos error is telling, but I haven't turned anything up during a search yet.
Any ideas ?
Please AMA if you need more info or clarification.
Matthew

Hello,
When the issue happens, can you telent the target server successfully?
Please refer to the following KB article to see if it helps:
https://support2.microsoft.com/kb/979175?wa=wsignin1.0
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Can i use exchange 2010 in the mail(4.5)?

Can i use exchange 2010 in the mail（4.5）？
i can't use exchange 2010 in the mail （4.5），but i can use normally in the mail （3.6）。why？

Of course you can use your iPhone in the rain but since devices are not waterproof, nobody in their right mind would recommend it. The risk is yours and an out-of-warranty repair might cost more than a few bucks.
I highly recommend you read this article: http://support.apple.com/kb/ht3302
And some kind of a protective casing if you insist on using the device in the rain.
Live long and prosper!

Appointments from Exchange 2010 show as Mail in Mailbox

I have a very frustrating issue with a single user on one of our post offices. For reasons unknown appointments sent to the user from Exchange 2010 appear as mail items instead of appointments within the mailbox. Other users on the same post office do not get the same issue. I have tried resetting the user's views and a full client reset via maintenance. I have set the user's client settings to be the same as another user who does not get the issue without any luck either. Maintenance checks on the account does not flag any errors. I'm pretty certain I'm missing something very simple, but alas I can not think what.
Software wise we're running client 8.0.1 on post office agent version 8.0.2. We seem to get the same results regardless of the Client version of outlook, (we have tried the web version and 2003 and 2010 of the client). Anything else I could try would be greatly appreciated.
Kind Regards
Rob

In article <[email protected]>, Rob naylor
wrote:
> Software wise we're running client 8.0.1 on post office agent version
> 8.0.2.
>
How about updating those as they are a bit old.
Try looking at that user's account from another machine and from
WebAccess (if installed).
It is good to separate the PC from the user account as sometimes an odd
problem can be from some funky issue on the PC.
I'm not surprised that different versions of the Exchange 2010 client
doesn't make a difference as there is the formatting is set when
Exchange formats the outgoing to the internet.
A thought there, is your user setup as a contact on the Exchange
system, there have been settings in the past that caused invalid
formatting of internet messages. Something to the effect that 'this
user is on OutLook/Exchange vs regular internet standards'.
Has there been a single appointment sent from a user on that Exchange
system to two of your users?
Andy Konecny
Konecny Consulting Inc. in Toronto
"Give more than others think is wise
Challenge yourself beyond what others think is right"
Michael 'Pinball' Clemens

Exchange 2010 & 2013 coexistence mail flow between servers

Similar Messages

Maybe you are looking for