Exchange Migration Issues

Hi All,
Have taken over a site that's had a exchange migration completed from exchange 2010 to exchange 2013 using a CAS Server and a mailbox server

No-one is able to connect to the new server, the original exchange server is still in place appears to be using 2 different names to connect to the server and

When i do auto configuration test it fails with the following error

autodiscover request completed with status code 503

Any help with this would be greatly appreciated

Thanks in Advance
Chris AceAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Amit KumarCommented:

1. is OWA working fine from new servers (Exchange 2013)?
2. check Autodiscover SRV record is it pointed to New Server (Exchange 2013)?
3. Check external and internal URL on all Exchange virtual directories published on both Exchange 2010 and Exchange 2013
4. Are you using CAS Proxy/redirection method to connect if any user is on Exchange 2010?
5. Check Outlook Anywhere settings too
Chris AceAuthor Commented:
It appears there is a CAS Proxy Redirection happening as if i try to create a new profile to connect directly to the new server it fails but will connect to old server but can't open the mailbox

Owa works fine and inbound email working fine

outlook anywhere is pointing to correct location

will check others and come back to you

Amit KumarCommented:
CAS proxying is not a default configuration, we will have to change IIS virtual directories authentication to Integrated Authentication on Old Exchange servers and new servers with FBA. Also we need to configure Internal/External URLs accordingly.

If you are using FBA (Form based Authentication) on both servers then it will be redirection.

Check below mentioned things:

1. Login in OWA with Exchange 2010 user using Exchange 2013 OWA URL, if it re-directs to Exchange 2010 OWA URL and open OWA so it is CAS-Redirection. If not and it gives you message of mentioning Exchange 2010 OWA URL so redirection is not configured.

Note: As per my knowledge now-a-days Exchange servers are already configure to silent redirect Legacy OWA URLs

2. There must be only one Autodiscover SRV record in internal DNS and only one HOST A record in public DNS. Both must be pointed to Exchange 2010 CAS Server.

One more thing to check that is outlook anywhere working from internet or not?

3. check all Exchange virtual directories's Internal and External URL, Please confirm if you are using same for both.

Check by below PS:

get-owavirtualdirectory | fl Name, ServerName, OWAVersion, LegacyRedirectType, CrossSiteRedirectType, InternalURL, ExternalURL >C:\OWAStat.txt

get-OutlookAnywhere | fl ServerName, ExternalhostName, ExchangeVersion >C:\OAStat.txt

Open in new window

Verify both text files and check if URLs are correct in place.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.