2003 to 2010 transition

In mid transition from Exchange 2003 to 2010 and setting up the redirect from the new 2010 server to the 2003 system for owa, I've set the "exchange2003URL" to point to our frontend 2003 server url "https://*********/exchange
When logging in I am presented with the 2010 outlook web app and am redirected to the 2003 server but getting "page cannot be displayed"  error code 64, it is going to the correct server as the certificate is the correct OWA ssl but it seems to be landing on the "/exchweb" page instead of the "/Exchange" I've tried enabling forms based authentication but this stops anyone logging into owa
Jon CarneyInfrastructure EngineerAsked:
Who is Participating?
 
Gaurav SinghSolution ArchitectCommented:
You will need to have a rule in ISA for legacy  domain. existing domain should point to Exchange 2010 server CAS. legacy domain like legacydomain.abc.com should point to Exchange 2003. You will need to create separate rule in ISA for OWA to point to the exchange 2003 servers.
0
 
Jon CarneyInfrastructure EngineerAuthor Commented:
Hi Systechadmin

Thanks for the reply, I did see that post but the cert it refers to is an internal cert, we are using a wildcard issued by third party geotrust with all intermediate certs installed on all Exchange servers.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
Gaurav SinghSolution ArchitectCommented:
Is there any proxy server like ISA or TMG?
0
 
Jon CarneyInfrastructure EngineerAuthor Commented:
There is an ISA 2006 server but I've tried bypassing the server for internal use by changing the DNS entry to point directly to the FE Exchange server and not ISA as we're using split DNS but getting the same results.
Trying it directly on the new exchange server via a web browser lets you log in fine.
0
 
Jon CarneyInfrastructure EngineerAuthor Commented:
Right, I've set up the rules on the ISA server and legacy is pointing to 2003 servers, seem to be getting a bit further but now seeing an "error code 10061: connection refused" after the redirect?
0
 
Gaurav SinghSolution ArchitectCommented:
is the legacy domain included in the certificate? Please check the ISA logs for any rules issues.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.