• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 405
  • Last Modified:

Migration - Exchange 2003 to 2010 Issues

The story so far (famous last words):

Installed Exchange 2010 on Server 2008 R2 Standard in coexist mode with our legacy Exchange 2003 server.

We followed this for the install:

http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_2881-Migrate-Small-Business-Server-2003-to-Exchange-2010-and-Windows-2008-R2.html

When I run the ExRCA for Auto Discover (see attachment) it is pulling a Certificate from the Firewall which of course doesn’t match the autodiscover.abcd.co

When I access OWA with https://mail.abcd.co/owa and I use an account whose mailbox is on
2010 it works fine.

When I access OWA with https://mail.abcd.co/owa and I use an account whose mailbox is on 2003 I login on the 2010 OWA page and then I get another login box (same as if I was logging into http://mail.abcd.co/exchange) which I enter un and pw which then goes to this page with this error.

https://legacy.abcd.co/exchweb/bin/auth/owaauth.dll
The website cannot display the page HTTP 500 error

If I login with http://mail.abcd.co/exchange/ with an account whose mailbox is on 2003 it works fine.

Not sure where to start the trouble shooting process and could use some guidenece.

Really need some help from the experts to heal these issues…

Thanks in advance…


 ExRCA-is-attempting-to-test-Auto.docx
0
Vince Glisson
Asked:
Vince Glisson
  • 5
  • 5
  • 2
  • +1
2 Solutions
 
sunnyc7Commented:
Check this for OWA during coexistence
http://exchangeserverpro.com/exchange-2010-owa-legacy-url-redirection-http-500-error

Didnt understand why you would use a SBS migration doc for Exchange 2003 > 2010 migration.
that document doesnt apply.
0
 
Madan SharmaConsultantCommented:
please once check if there are following directories under server settings- - client access-- outlook web access
Exchange
Exchweb

if you don't have these directories then there are some issue while preparing active directory for exchange legacy permission

you also need to create a dns entry for your domain legacy.yourdomain.com
hope it will help you.
0
Improved Protection from Phishing Attacks

WatchGuard DNSWatch reduces malware infections by detecting and blocking malicious DNS requests, improving your ability to protect employees from phishing attacks. Learn more about our newest service included in Total Security Suite today!

 
Vince GlissonOwnerAuthor Commented:
@sunnyc7: comments from SBS migration doc...

Daeraligh:
Is this the same process as migrating exhange 2003 to 2010. Using a win server 2003 to a new win 2008 server? If not can you get an articale for it.

This article is most helpful. Thanks

Dae
 
demazter:
Yes it is the same process, just skip the specific SBS parts.
 
0
 
sunnyc7Commented:

I just googled > Exhcange 2003 2010 migration < and got this as a first result.

I have used these steps and they have worked out well so far.
http://msexchangegeek.com/2010/01/30/rapid-transition-guide-from-exchange-2003-to-exchange-2010/
0
 
Vince GlissonOwnerAuthor Commented:
@sunnyc7:

Looks to be a very well written guide, thank you very much, any help is greatly appreciated.
0
 
sunnyc7Commented:
You can run those commands in powershell and get cracking.
It's faster, than click this, click that on EMC
0
 
Vince GlissonOwnerAuthor Commented:

Outlook 2003 clients are not connecting after I move their mailbox over to Exchange 2010. Outlook 2010 clients do not have any problems finding the new Exchange Server and are working fine, except for the Certificate Warning.

 
0
 
Madan SharmaConsultantCommented:
0
 
sunnyc7Commented:
Run this from CAS Server
Set-RpcClientAccess –Server Exchange_server_name –EncryptionRequired $False

Restart service and try again for Outlook 2003 ?
0
 
Vince GlissonOwnerAuthor Commented:
@sunnyc7:

That was it...one more problem out of the way... thanks
0
 
sunnyc7Commented:
Please close the case if the issue is resolved.
0
 
Vince GlissonOwnerAuthor Commented:
@sunnyc7:

Not all issues have been solved, autodiscover is still not working, but i think to be fair i should close this case and start another question specific to Outlook Anywhere and the autodiscover feature.

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.

Join & Write a Comment

Featured Post

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.

  • 5
  • 5
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now