Solved

Exchange migration problem

Posted on 2014-12-20
10
112 Views
Last Modified: 2014-12-31
We have migrate Exchange 2010 SP3 to 2013 CU6

Ex email server name was mail and the newer one's name is posta  
when we shut down ex mail server some outlook's return limited connection error , all clients connectiong exchange from outlook via ip address not with domain names and also we are using an email gateway this is why our mx records different then it is so we are redirecting emails to ip address directly from the mail gateway but sometimes it logs some errors like this  
Some computers getting smtp errors (smtp connector was created on ex 2010 but what does matters 2013 see connector ? )

when we open back ex 2010 server every thing returns to normal so so. hw that should be possible this are the results of diag :

PS C:\Users\administrator.> dcdiag

Directory Server Diagnosis

Performing initial setup:
   Trying to find home server...
   ***Error: posta is not a Directory Server.  Must specify /s:<Directory Server> or  /n:<Naming Context> or nothing to
   use the local machine.
   ERROR: Could not find home server.
PS C:\Users\administrator.> repadmin /showrepl

Repadmin: running command /showrepl against full DC ad.xxxx.com
Default-First-Site-Name\AD
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: dab63121-51f8-48ee-aa92-29ff9bcebf17
DSA invocationID: dab63121-51f8-48ee-aa92-29ff9bcebf17

Open in new window

0
Comment
Question by:Cahit Eyigunlu
  • 5
  • 5
10 Comments
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40510794
Hey Cahit,

DCDIAG is just for Domain Controllers, so that is why the test is failing. It is not an Exchange Server test. If you are uncertain about the health of your domain controllers then rerun the test from a DC, or specify the /S switch as indicated in the help.

We do need more information for this problem though.

Have you moved all mailboxes to 2013?
What migration documentation are you following?
Why are you using an IP address to configure Outlook clients?
Are you using a 3rd party certificate on Exchange?
Are you using split-brain DNS?
Have you configured all your internal and external URLs in Exchange?
What version of Outlook are your clients using?
0
 

Author Comment

by:Cahit Eyigunlu
ID: 40510832
Have you moved all mailboxes to 2013?
Yes

What migration documentation are you following?
We just installed brand new 2013 cu6 without any error log then start migrate tool on ecp


Why are you using an IP address to configure Outlook clients?

Yes not a domain name we are using ip address on server name


Are you using a 3rd party certificate on Exchange?

yes we bought from rapidssl for web app.


Are you using split-brain DNS?

No just simple Active directory & dns server



Have you configured all your internal and external URLs in Exchange?


Yes we do we have no problem on owa and we get no error while migration



What version of Outlook are your clients using?


2013
0
 

Author Comment

by:Cahit Eyigunlu
ID: 40510838
some times it returns

'550 5.1.1 RESOLVER.ADR.RecipNotFound; not found'
0
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40510974
Hey Cahit,

I think something might be wrong with DNS or the URLs. Take a look at my article on 2013 namespace design and implementation. See if this helps.
https://supertekboy.com/2014/07/08/designing-simple-namespace-exchange-2013/
0
 

Author Comment

by:Cahit Eyigunlu
ID: 40510987
but maybe the problem should be mailgateway because our mx records points to mail border  
then it forward to ip address of the new mail server .
is there any way to set auto discovery on dns server to point outlook calls to the exchange instead of mx records
0
Better Security Awareness With Threat Intelligence

See how one of the leading financial services organizations uses Recorded Future as part of a holistic threat intelligence program to promote security awareness and proactively and efficiently identify threats.

 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40511035
Your mail gateway and MX records are only for mail flow.

Autodiscover needs to point to the Exchange server directly. Not the mail gateway. So use a CNAME or A record to point to the public IP of your Exchange server. Forward ports 80 and 443 through your firewall to Exchange.
0
 

Author Comment

by:Cahit Eyigunlu
ID: 40511136
how should i create autodiscovery records ?
0
 
LVL 31

Accepted Solution

by:
Gareth Gudger earned 500 total points
ID: 40511230
You can do this one of two ways. But you need to create a DNS record with your external DNS provider.

If you have autodiscover.yourdomain.com on your SSL certificate, you can create an A or CNAME record called autodiscover.

If you don't have autodiscover on your SSL certificate then you can create an SRV record (as long as your external DNS provider support them).
0
 

Author Closing Comment

by:Cahit Eyigunlu
ID: 40525282
thank you
0
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40525283
Glad to help!
0

Featured Post

Why spend so long doing email signature updates?

Do you spend loads of your time carrying out email signature updates? Not very interesting are they? Don’t let signature updates get you down. Let Exclaimer Cloud - Signatures for Office 365 make managing email signatures a breeze.

Join & Write a Comment

The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
Local Continuous Replication is a cost effective and quick way of backing up Exchange server data. The following article describes the steps required to configure Local Continuous Replication. Also, the article tells you how to restore from a backup…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…

759 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now