Migrate Exchange 2010 to 2013 External Mail Flow

Dear All,
I am in the middle of Exchange Server 2010 to 2013 Migration. The scenario is I have single Exchange 2010 server with HUB/CAS/Mailbox and installed new Exchange 2013 with single CAS and single Mailbox server. The internal email flow between Exchange
2010 to 2013 and 2013 to 2010 is working. Having some issues and need assistance to resolve at earliest.
The issue with the external mail flow and I want to Exchange 2010 should be configured to send external email while migrating users to Exchange 2013. Once migrate all users to Exchange 2013 then will configure Exchange 2013 send connector.
How can I configure single name space of web URL for OWA both on Exchange 2010 to Exchange 2013, if user mailbox is in Exchange 2010 can access same OWA URL as user migrate to Exchange 2013.
How to configure SSL certificate, I have single URL certificate this would be enough for OWA, ActiveSync and Anywhere.
Is that possible if directly move the Exchange 2010 database to Exchange 2013 database, this will move all users mailboxes in one go or do I need to migrate users mailbox individual or in bulk.
Kindly guide if any thing missing that need to address during start the migration activity.
Thanks in Advance

Hi ,
Sorry for delay.
Question : Thanks for your valuable response. On
point no.2, I want to use same external URL for Exchange 2010 and Exchange 2013, is this possible if user is on exchange 2010 server or migrated on Exchange 2013 can use same external single name space URL to access OWA ?
Yes you can have the same External URL for the exchange 2010 owa and exchange 2013 owa.So users from exchange
2010 and exchange 2013 can access owa on the same URL from external world.For exchange 2010 users owa connections will be proxied from exchange 2013 to exchange 2010.
For mailbox connectivity issue in exchange 2013 :
1.From internal outlook clients ,Please check the internal outlook anywhere name is resolved to exchange
2013 server and also make sure the authentication set on the outlook anywhere is set to NTLM. Same time we need to have the internal outlook anywhere name on the SAN certificate.
2.Make sure the names used exchange on 2013 URL'S is available on the SAN certificate and also the certificate
needs to installed on the exchange server and that certificate has to be enabled for the required services like iis,pop.imap,smtp.
3.Make sure the outlook client request coming for internal outlook anywhere name and also to autodiscover
service is not reaching the proxy server if you have on your network.
In case if you have proxy server in your environment for internet access ,So for that we need to add the internal outlook anywhere name and autodiscover name
on the internet explorer proxy exceptions for all the internal outlook clients.We can globally achieve it through group policy.
4.please share me the output for the below mentioned command.
get-ClientAccessServer -Identity “server name” | fl AutodiscoverServiceInternalURI
5.If you are having outlook 2007 then make sure it fully patched with latest sp and updates.
6.On which operating system version those outlook 2007 clients are installed?
Please reply me if anything is unclear.
Thanks & Regards S.Nithyanandham

Similar Messages

Questions about migrating Exchange 2010 to 2013

We currently have two Exchange 2010 servers with roles separated. One local mailbox server without CAS in our building and a CAS with no mailboxes in a remote datacenter.
We plan to migrate to 2013 with two new servers hosting all roles on each and then shut down the 2010 servers. There will be one local and one in a datacenter for Exchange 2013 so that either server could be individually restarted without internal LAN users
losing email access. (We do not want to open network access from the Internet to the onsite CAS). Is it practical to set it up this way?
How do we get the existing certificates (mail, autodiscover, and the local host name etc.) moved from the 2010 to the 2013 to the new servers when I assume they both must be running side by side for at least a short time while mailboxes are moved form 2010
to 2013? Will we need to buy new SSL certificates since the local host machine names for the Exchange server 2013 servers will be new and there will be more than one CAS?

Most of the CAs allow issuing duplicate certificate (as if you are requesting for a new cert) for the servers running same application. If your CA doesn't provide duplicates you can export the certificate and import to Exchange2013. http://msexchangeguru.com/2013/06/29/import-cert-e2013/
In certificate you dont need your internal FQDN. Especially in future you wont be able to add your internal FQDN in your certificate as most of the CAs wont allow you to add internal FQDN.
When you migrate to exchange 2013 you just need to configure the external URLs of Ex2010 in Ex2013 for both (i.e. same URLs for internal and external URLs) and point your common name and autodiscover to Exc2013 as Ex2013 will proxy the requests to your legacy
Ex2010 server. i.e. Your client interface will be Ex2013.
Please check this it will help you configure Split DNS and configure your URLs
http://exchange.sembee.info/2013/install/clientaccesshostnames.asp
http://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/ GUI
Configure split DNS to resolve external name from internal network.
Keep both Ex2010 CAS and Ex2013 CAS servers till all get logged in atleast once to connect to Ex2013 mailbox automatically.
As your DAG stretched across the data centers make sure
your DAG is in DAC mode.
http://technet.microsoft.com/en-us/library/dd979790(v=exchg.150).aspx
Please read this as well for details about DAG configured in multiple site
http://technet.microsoft.com/en-us/library/dd638129(v=exchg.150).aspx
Ensure you use Exchange2013 SP1 as it is already released and available for download
http://www.microsoft.com/en-us/download/details.aspx?id=41994
Do you have a load balancer in place?
Regarding internet facing it depends. You can configure CAS2013 server in DMZ if you wish to.
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

How to Migrate Exchange 2010 to 2013

am planning to migrate my existing Exchange 2010 Environment to Exchange 2013, My Existing setup as follows below.
2MBX Which is part of DAG, 1CAS/1HUB/1Archival MBX . Please advise me how to initiate and complete successfully.
OS : windows server 2008 R2 Ent.
Forest Functional Level : Windows server 2003
Domain Functional Level : Window server 2003
Also we have Gateway for external emails SPAM Filtering.
Thanks, Venkatesh. "Hardwork Never Fails"

You're in the Lync forums, I'd post this question in the Exchange forums:
http://social.technet.microsoft.com/Forums/exchange/en-US/home?forum=exchangesvrgeneral
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

Public Folder Migration Exchange 2010 to 2013 Stuck on Queued

I submit the request New-PublicFolderMigrationRequest and the status is stuck on "Queued". What are the steps to troubleshoot this? I have followed the article in on Technet to perform my PF migration.

[PS] C:\Windows\system32>New-PublicFolderMigrationRequest -SourceDatabase (Get-PublicFolderDatabase -Server "exchange3.a
npinetwork.com") -CSVData (Get-Content "C:\PFMigration\foldertomailbox.csv" -Encoding Byte)
Name SourceDatabase
Status
PublicFolderMigration Public Folder Database 1055175278 Queued
[PS] C:\Windows\system32>Get-PublicFolderMigrationRequest | Get-PublicFolderMigrationRequestStatistics -IncludeReport |
Format-List
RunspaceId : c2270d62-665e-44ad-8829-43f5befde1f9
Name : PublicFolderMigration
Status : Queued
StatusDetail : Queued
SyncStage : None
Flags : IntraOrg, Pull, SuspendWhenReadyToComplete
RequestStyle : IntraOrg
Direction : Pull
Protect : False
Priority : Normal
Suspend : False
SourceVersion : Version 14.3 (Build 123.0)
SourceDatabase : Public Folder Database 1055175278
SourceServer : exchange3.anpinetwork.com
BatchName :
OutlookAnywhereHostName :
RemoteCredentialUsername :
AuthenticationMethod : Basic
RemoteMailboxLegacyDN :
RemoteMailboxServerLegacyDN :
BadItemLimit : 0
BadItemsEncountered : 0
LargeItemLimit : 0
LargeItemsEncountered : 0
FolderToMailboxMap : {\}
QueuedTimestamp : 1/16/2014 1:44:08 PM
StartTimestamp :
LastUpdateTimestamp : 1/16/2014 1:44:10 PM
InitialSeedingCompletedTimestamp :
FinalSyncTimestamp :
CompletionTimestamp :
SuspendedTimestamp :
OverallDuration : 00:00:23
TotalFinalizationDuration :
TotalDataReplicationWaitDuration :
TotalSuspendedDuration :
TotalFailedDuration :
TotalQueuedDuration : 00:00:23
TotalInProgressDuration :
TotalStalledDueToCIDuration :
TotalStalledDueToHADuration :
TotalStalledDueToReadThrottle :
TotalStalledDueToWriteThrottle :
TotalStalledDueToReadCpu :
TotalStalledDueToWriteCpu :
TotalStalledDueToReadUnknown :
TotalStalledDueToWriteUnknown :
TotalTransientFailureDuration :
TotalIdleDuration :
MRSServerName :
EstimatedTransferSize : 0 B (0 bytes)
EstimatedTransferItemCount : 0
BytesTransferred :
BytesTransferredPerMinute :
ItemsTransferred :
PercentComplete : 0
PositionInQueue : 6/6 (Position/Queue Length)
PreventCompletion : True
FailureCode :
FailureType :
FailureSide :
Message :
PoisonCount : 0
FailureTimestamp :
IsValid : True
ValidationMessage :
OrganizationId :
RequestGuid : 238914aa-baf7-42b2-91d0-4b27e22e3a81
RequestQueue : ANPIMDB02
ExchangeGuid : 0c62c485-3fd1-4aaf-b29d-67cfa078ac41
Identity : 6209b848-c493-4147-9937-d91e3f16f846\238914aa-baf7-42b2-91d0-4b27e22e3a81
DiagnosticInfo :
Report : 1/16/2014 1:44:07 PM [LSVGNV04EXC01] 'anpinetwork.com/Springfield/Users and
Computers/Network Services/Users/Mitch Givner' created request.
ObjectState : New
[PS] C:\Windows\system32>

Mail flow is not working Exchange 2010 to 2013 in coexistence mode

Hi ,
We are migrating Exchange 2010 sp3 to Exchange 2013.
mail flow is not working from 2010 to 2013, mails are qued up in smtp relay queueu.
already added 2010 ip address to 2013 receive connector and give anonymous permission.
but still mails are smtp relay queue.

Hi Sujith,
As requested by
Nithyanandham please post the error from Queue Viewer.
Few things to check.
Please remove IP address from "Default Receive connector" first.
Ensure both servers can ping by FQDN and it returns correct IP. i.e. ping exch2013.contoso.com
Make sure both exchange server can communicate each other. if possible try to telnet port 25 by FQDN of the Exchange2013 server and try to send an email from exchange2010 using the URL below. if there is any error please post error.
http://exchange.mvps.org/smtp_frames.htm
Make sure "Exchange server Authentication" is ticked in your default receive connector properties. If not ticked tick it and restart Transport service and check mail flow again.
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Exchange server name not changing in mail profile after migration from 2010 to 2013

Following a migration from 2010 to 2013 we are finding that for a number of users the old exchange server address stays in the mail profile (control panel -> mail -> e-mail accounts) which causes Outlook not to load.
We are able to go into control panel -> mail -> e-mail accounts and change this manually to the new exchange 2013 server address but we have quite a number of users and don't really want to do it manually.
Shouldn't it be updating automatically and if so why is it?

Hi,
Yes, it should be changed by autodiscover. Does this issue occur to all the migrated users?
I have seen this kind of issues before when migrating from Exchange 2003/2007 to Exchange 2010. The most efficient way is to rebuild the Outlook profile.
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Exchange 2010 and 2013 coexistence Internal and external URL

Hi all,
been reading alot of threads about Outlook anywhere and virtual directories in co-existence exchange 2010 and 2013.
Still i dont get any smarter.
Here is scenario:
Exchange 2010
Cas1
Cas2
Mailbox1
Mailbox2
Casarray is Exchange.casarray,com ( internal dns pointed to CAS1 in exchange 2010).Seems like by default both exchange 2013 cas servers are added to the casarray.
Exchange 2013
CAS+Mailbox
Cas+Mailbox
DNS
mail.exchange.com pointing to VIP (kemp loadbalancer)
Autodiscover ( pointed to same vip ,kemp load balancer)
Outlook anywhere on all servers (2010 and 2013)
Internal ( pointing to VIP on Kemp)
External ( pointing to external IP,then it passes firewall that again passes to kemp)
Problem we are having is when migrating users from Exchange 2010 - 2013.
Users using Outlook 2010
restart of outlook and mail works fine.
OWA works fine
Active sync fails ( need to inherit permission of users AD object),wait couple of hours then mobile can sync again.)
Users using Outlook 2013
Outlook in disconnected status,only fix is to create new profile.
OWA works fine
Active sync fails ( need to inherit permission of users AD object),wait couple of hours then mobile can sync again.)
Question is,what should be set for internal and external url (active sync,owa,ews)on 2010 and 2013 servers?
Where is the config wrong?
Thanks!
Please 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. Thank you! Off2work

Hi Martina,
did the test as mentioned,even tried both CAS 2013 servers.Flush and registerdns didnt help.
Still Outlook is Connected to the cas.exchange.as (which again Points to 1 of Exchange 2010 servers),
Tried repair Outlook profile,no og.Only fix is to setup New account.
Any more tips?
thanks!
Please 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. Thank you! Off2work

Exchange 2010 to 2013 Migration: Authentication/Proxy Settings Issue

I'm in the final stages of preparing for our Exchange 2010 to 2013 migration. I'm noticing minor authentication issues on mobile devices (android & ios) and proxy setting issues with Outlook that require user intervention. In an effort to make the migration
as smooth as possible for our internal users, I'd like to get these settings ironed out before starting the migration.
Symptoms:
Outlook - I'm aware that internal Outlook usage has changed its connection protocol from RCP/TCP to RCP/HTTP, but it appears that Outlook isn't updating its settings in the "Microsoft Exchange Proxy Settings" after a users mailbox has been migrated
from 2010 to 2013. Currently, 2010 users with Outlook 2013 have the following settings configured in Outlook's Exchange Proxy Settings:
URL to connect to my proxy server for Exchange: webmail.domain.com
Connect using SSL only: Checked
Only connect to proxy servers that have this principal name in their certificates: Unchecked
On fast networks, connect using HTTP first, then connect using TCP/IP: Unchecked
On slow networks, connect using HTTP first, then connect using TCP/IP: Checked
After migrating a user's mailbox from 2010 to 2013, the above settings remain the same in Outlook and their client disconnects from Exchange and isn't able to reconnect. After manually enabling the checkbox for "On fast networks, connect using HTTP
first, then connect using TCP/IP", Outlook clients are able to connect to Exchange via their newly migrated mailbox.
Is there a way to automatically updating these 2 proxy settings in Outlook during the migration instead of having to manually change each user's configuration in Outlook?
Android & iOS - Currently, users on Android & iOS with Exchange 2010 mailboxes have the following configuration:
domain: blank
username: their AD username
server: webmail.domain.com
After migrating a mobile users mailbox from 2010 to 2013, neither OS (Android or iOS) is able to connect due to an authentication failure. On iOS, if I manually change the domain from blank to my company's domain, authentication succeeds and their 2013 mailbox
begins to update. On Android, the option to change the domain name from null is grayed out, requiring the user to delete the Exchange profile and re-add it with the domain name intact. Is there a way to configure Exchange 2013 to not require the domain name
for mobile users in the same way that it's been working for us with Exchange 2010?
Please let me know if you require cmdlet print outs of my virtual directories to help troubleshoot the issue.

Hi,
Generally, when the user mailbox is moved from Exchange 2010 to Exchange 2013, the Autodiscover service would detect the changes and update the new configuration automatically.
Please make sure the autodiscover service in your new Exchange 2013 is configured correctly. We can create a new mailbox in Exchange 2013 and check whether the new Exchange 2013 user can setup account successfully in Outlook or not. If the new user works
fine, it indicates the autodiscover service in Exchange 2013 should be proper for internal user.
Please restart the following Exchange service to have a try:
Microsoft Exchange RPC Client Access
Microsoft Exchange Mailbox Replication
Restart IIS service by running IISReset in a Command Prompt window.
Then check whether the Outlook client can connect to Exchange 2013 or not.
As for Android & iOS issue, I suggest we can ask a question in ActiveSync forum for more suggestion:
https://social.technet.microsoft.com/Forums/en-US/home?forum=exchangesvrmobility
Regards,
Winnie Liang
TechNet Community Support

Exchange 2010 to 2013 users migration

Hi,
I am migrating users from Exchange 2010 to 2013 and facing a lot of migration issues. few of them are as follow.
1. It hung up at "syncing" and end up with a failure.
2. After a long migration i got the following errors
Error: MigrationPermanentExeception: Failed to reset the target mailbox after the move. Error Details:MaipExceptionADUnavailable: Unable to prepopulate the cache for user :: on domain controller xyz.domain.com (hr=0x80004005,ec=2414) Diagnosti Context: Lid:
65256 Lid:1494 ---- Remote Context Beg ---- Lid: 52664 StoreEc: 0x96E Lid: 35973 StoreEc: 0x96E Target Mailbox unlock operation was not replicated. If a lossy failover occurs after the target mailbox was unlocked, the target mailbox could remain inaccessible.
Error details: Target mailbox connection was lost.
3. users migration is taking a lot of time although mailbox size is not big and both servers are in same datacenter.
Need urgent help pls....

Hi,
Here are the general steps for troubleshooting mailbox moves:
1. If the move request didn't complete, view the Move Request Statistics.
2. If the move request completed with errors, view the move report.
3. View the Event log on the Client Access server running the instance of the Microsoft Exchange Mailbox Replication service that's processing the failed move request.
4. use the Exchange Management Console or the Exchange Management Shell to increase the diagnostic logging levels on the Client Access server for the Mailbox Move and Service categories of the MSExchange Mailbox Replication service.
For more detailed information about general steps for troubleshooting mailbox moves, you can refer to the article below:
http://technet.microsoft.com/en-us/library/dd638094(v=exchg.141).aspx
Additionally, in order to narrow down the cause, I’d like to confirm the following information:
1. Are the problematic target mailboxes in the same database?
2. Is there a time boundary? After that, you cannot move mailboxes:
http://social.technet.microsoft.com/Forums/en-US/90403f75-e530-478a-ab68-27823b730f68/exchange-2013-batch-to-migrate-users-from-2010-database-is-hung-at-syncing-after-a-disaster?forum=exchangesvrdeploy
Thanks,
Angela
Angela Shi
TechNet Community Support

Exchange 2010 to 2013 Migration- orphaned 2010 servers in Edge subscription

Migration of Exchange 2010 to 2013 was carried out. Steps to decommission the 2010 servers was done, including removing the Exchange software fro the servers. Looks like some pieces were missed though as the 2010 servers still appear in the smarthostdelivery
and shadow redundancy on the 2010 edge transport server.
How can these be removed?

Hi,
I recommend you can use the following script to cleanup the queue:
Cleanup Shadow Redundancy Queues
Performs a search per server per shadow redundancy queue. If shadow redundancy queues contain
at least 1 message the receive date is inspected. If it is more then 1 day ago it will cleanup
the message.
Normally you do not have to cleanup the shadow redundancy queues because messages will automatically
expire, how long this takes depends on your config but normally 2 days.
However in some scenarios it might be necessary to clean the queues.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Migration Exchange 2010 to Exchange 2013 with CAS Array and DAG

Dear All,
I am starting the migration of Exchange 2010 2 servers (CAS/Mailbox) with DAG no CAS Array to Exchange 2013 with 2 servers CAS array and 2 Mailbox servers with DAG. I read on some blogs that no requirement of CAS array on Exchange 2013. My concern how to
configure NLB on CAS servers for the client to connect.
Please guide and have any deployment guide for this, kindly share.
Thanks

Hi ,
As you said there is no use and meaning of having the cas array in exchange 2013 and also thanks a lot to Microsoft for introducing an single namespace facility in exchange 2013.
My suggestion and Microsoft recommendation should be to go with hardware load balancers for exchange 2013 rather than using the windows NLB and round robin method.
Why we need to go for HLB ?
Disadvantages
of some load balancing methods :
Windows
NLB :-
If you use Windows NLB then it can provide redundancy on server level failure and not on application level.
DNS
round robin :-
In case if we use the windows round robin method for load balancing then it wouldn't provide server level
and application level redundancy during the failures.At the Same time we need to manually adjust the DNS records during the server failure but on the client end dns caches will create the issues.
Configuring NLB for exchange 2013 :
http://msexchangeguru.com/2013/08/14/windowsnlb/
NLB configurations for exchange 2010 and 2013 will be same.
Configuring round robin for exchange 2013 :
http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/
Advisable method is to have the CAS and MBX roles on the same box if NLB not comes it to play.Because windows failover clustering and NLB cannot be configured on the same box.In exchange 2013 cas role is a stateless server role so there is no need to have
that role on a separate box.
Thanks & Regards S.Nithyanandham

Exchange 2010 to 2013 Public Folder Migration -- Token Serialization

Here is the log entry,Failed to save admin audit log for this cmdlet invocation. Organization: First Organization Log content:Cmdlet Name: New-PublicFolderMigrationRequestObject Modified: f0daff33-6a93-4367-b609-662cfa0b92de\71fc0595-b5d7-4f15-8b7c-bffcefbd810fParameter: SourceDatabase = Public Folder Database Parameter: CSVData = VGFyZ2V0TWFpbGJveCxGb2xkZXJQYXRoDQpDb2JvY28gUEYsXA0KQ29ib2NvIFBGLFxJUE1fU1VCVFJFRVxBcg==...Caller: ExternalAccess: FalseSucceeded: TrueRun Date: 2015-07-07T12:41:45OriginatingServer: (15.00.0995.012)Error:Microsoft.Exchange.Data.ApplicationLogic.AuditLogAccessDeniedException: The requesting account doesn't have permission to access the audit log. --- System.Web.Services.Protocols.SoapException: The requesting account does not have permission to serialize tokens. at...

Hey Guys!
I'm in the process of testing a Public Folder migration from Exchange 2010 to 2013, I've been following the recommened migration scenario from Microsoft but have ran into this issue when running New-PublicFolderMigrationRequest. I let the request sit at a queued status for over 6 hours and then decided to look at the event logs. I'm receiving an access denied, requesting account does not have permission to serialize tokens.
Luckily this is just a test and not in a production environment :-)
Any suggestion or help to point me in the right direction would be appreciated
Thanks Guys
This topic first appeared in the Spiceworks Community

Exchange 2010 to 2013 Activesync migration

Hey guys got a question, if i'm doing a migration from 2010 to 2013 and i have activesync policies on 2010, will a migrated user still adhere to these policies or do should i create the polcies on 2013 as well before migrated users?
also i've noticed some users arent getting the policies i created, they all have the same phone, brand new from the company, but some mobiles are getting the policy and some others are getting email but the policies just isnt being applied to the phone, is
this a flaw of activesync?

I'm not really sure about your second question. Hopefully someone else can help on that one.
The only things I can think of would be to make sure that ActiveSync is enabled for those users, and that the policy is applied to their mailbox.
You could run the Test-ActiveSyncConnectivity command and use the
Remote Connectivity Analyzer tool to get more information
Test-ActiveSyncConnectivity
Connectivity Analyzer

Exchange 2010 to 2013 Co-Existence Reverse DNS Issue

We are running a Exchange 2010 and 2013 coexistence. Mail Flow is fine on the 2013 side, but for mailboxes still on 2010, some are getting mail delivery failures only for certain external addresses. One of the deliveries says the Sending IP
does not have a valid rDNS. The IP Address it sent back is the main Public IP and not the Public IP assigned to our mail servers. Not understanding why the 2013 mailbox users can send to these external addresses no problem when 2010 mailbox users
are being routed through 2013. Thanks for any help.

Hi,
According to your post, I understand that account in Exchange 2010 deliver message failed for certain external addresses, however the user in Exchange 2013 works fine.
If I misunderstand your concern, please do not hesitate to let me know.
Whether all user in Exchange 2010 or some special account experience this question?
If this issue only occur on some specific external address, please contact its administrator to double confirm the configuration of anti-spam filter.
Besides, I recommend run Message tracking log and Protocol log to check the deliver process. More details about “Analyzing the protocol logs and Message tracking logs in Exchange 2013”:
http://social.technet.microsoft.com/wiki/contents/articles/23182.analyzing-the-protocol-logs-and-message-tracking-logs-in-exchange-2013.aspx
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

Will MX record work for the incoming mail flow and external mail flow.

Hello All,
I have created 2 machines with windows 2008 R2 workgroup and installed Forefront TMG 2010
I am using the VIP for the external adapter for the NLB and going to connect it through the MX record will it work for the incoming mail flow to the Exchange 2010 and external mail flow.
Is that right what i am doing please suggest. Thanks in Advance!
Sidharth Guntoji,Messaging Consultant, ITBigBang (P) Ltd Www.ITBigBang.Com | Hire Us for Messaging Consulting

Hi,
Based on my experience, the MX record contains the fully qualified domain name of the messaging server that’s responsible for accepting messages for the domain.
Do you want to configure the TMG server as a secure SMTP relay server? Did you mean that the external DNS server point to TMG’s external IP for the MX rcord and the internal Exchange server is using TMG’s internal IP address as the default gateway? Did you
install any exchange role on the TMG server?
I am sorry to say that I am not quite sure of your deployment, I would appreciate it if you can share your network topology and configuration.
Best regards,
Susie

Migrate Exchange 2010 to 2013 External Mail Flow

Similar Messages

Maybe you are looking for