Solved

Exchange 2007 to 2013 coexistence OWA and Outlook anywhere not workikng correctly

Posted on 2014-03-01
7
2,945 Views
Last Modified: 2014-03-08
Hello All and thank in advance,

I am migrating Exchange 2007 to 2013 and last night I configured the coexistence mode.

Exchnage 2013 is sitting on a 2012 R2 server and Exchange 2007 on a 2003 R2.

OWA was working fine in the begin but now externally it will redirect immediately to the legacy URL and nothing will load. Haven't change anything at all and I have checked my virtual directories to make sure that everything is correct same with the SSL.

Internally is working, but if I use an account that is on the 2007 exchange I will be able to  login but if I logout and try the owa url again it will redirect me to the legacy immediately (even if I do ctrl + F5 to clear the cache).

Second configuring phone email is working fine for the test user on the exchange 2013 but when I try to configure on my iphone a user that is on the 2007 exchange it fails.

Both Exchange servers are on the latest update.

Appreciate your time and help.
0
Comment
Question by:jamescarson69
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 2
7 Comments
 

Author Comment

by:jamescarson69
ID: 39897841
Hello All,

I resolved the first part of the OWA issue by making some changes in the Firewall. Now I am able to access OWA externally but again it redirects me immediately to the the legacy.domain.com/owa. So there is no way to login to OWA with a user created in Exchange 2013
0
 

Author Comment

by:jamescarson69
ID: 39897850
Also when I try the Microsoft Remote Analyzer for RPC while using the account of a user that exists in the Exchange 2013 everything is working fine. When I try the same test with a user account from the exchange 2007 It fails and I get the below

Attempting to ping RPC proxy owa.domain.co.uk.
       RPC Proxy can't be pinged.
       
      Additional Details
       
An HTTP 401 Unauthorized response was received from the remote Unknown server. This is usually the result of an incorrect username or password. If you are attempting to log onto an Office 365 service, ensure you are using your full User Principal Name (UPN).
Headers received:
request-id: a8da4815-131b-46d9-a400-19bbfa5ef11d
X-FEServer: DCLVMEX13
Content-Length: 0
Date: Sat, 01 Mar 2014 22:42:24 GMT
Server: Microsoft-IIS/8.5
WWW-Authenticate: Basic realm="owa.domain.co.uk"
X-Powered-By: ASP.NET
Elapsed Time: 183 ms.
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39897906
First

"Exchange 2013 is sitting on a 2012 R2 server"

Is that Exchange 2013 SP1? If not, then you are in an unsupported scenario. Exchange 2013 prior to SP1 was not supported on Windows 2012 R2. Windows 2012 and 2012 R2 are not the same thing.

Simon.
0
Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

 

Author Comment

by:jamescarson69
ID: 39897907
Hello Simon,

Yes it is Exchange 2013 SP1
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39898795
Exchange 2013 will proxy ActiveSync and Outlook Anywhere, but redirect OWA.
You need to ensure that ActiveSync has no external URL configured.

For Outlook Anywhere, it should just work, as long as the servers can see each other and the settings are close to default.

Simon.
0
 

Accepted Solution

by:
jamescarson69 earned 0 total points
ID: 39898976
Hello Simon and thank you for the reply.

I spoke with Microsoft today and they helped me resolve the issue.

The OWA issue got resolved by itself not sure what to say about it:S

About active sync there were two issues:

First issue was that in the virtual directories I was using the external URL for the internal and as you suggested I had the external URL empty instead I should have used the FQDN of the server for the internal and the Microsoft engineer configured also the external URL.

And second is that on the IIS of the 2007 exchange at the active sync properties I had to enable the integrated windows authentication because as they told me when in coexistence basic authentication only will not work.
iis-for-active-sync.JPG
0
 

Author Closing Comment

by:jamescarson69
ID: 39914446
Worked together with Microsoft Support and they resolved the issue with the above.
0

Featured Post

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Find out what you should include to make the best professional email signature for your organization.
This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
how to add IIS SMTP to handle application/Scanner relays into office 365.
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…

739 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