Migrating from Exchange 2003 to Exchange Online

We are trying to migrate from Microsoft Exchange 2003 to Microsoft Exchange online. When going through cut-over migration plan, we get this error -

"We weren't able to connect to the remote server. Please verify that the migration endpoint settings are correct and your certificate is valid, and then try again. Consider using the Exchange Remote Connectivity Analyzer (https://testexchangeconnectivity.com) to diagnose the connectivity issues."

When we are connect, we specify the exchange server and rpc proxy server. exchange server is set to our internal server name. RPC server is set to the mail.server.com. When we run the internal analyzer, we get all clear.

Any ideas on what the issue is? We verified the rpc authentication is set to basic, but are still having issues.

Help! Thanks all!
LVL 1
Roderick WolsiferAsked:
Who is Participating?
 
Alan HardistyCo-OwnerCommented:
No - you need a real trusted 3rd party certificate to migrate. It should cost no more than $50 - some are free.

Alan
0
 
Alan HardistyCo-OwnerCommented:
Have you installed a trusted 3rd party SSL certificate on your Exchange server?  If not - you need to.

Does Outlook work properly over HTTPS externally?

Alan
0
 
Roderick WolsiferAuthor Commented:
Yes, there is a 3rd party SSL cert in place.  Outlook functions correctly externally.
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
Alan HardistyCo-OwnerCommented:
Have you run the RPC over HTTPS test on testexchangeconnectivity.com specifying manual server settings?  Does it pass?
0
 
Roderick WolsiferAuthor Commented:
We're getting a 'certificate chain did not end in a trusted root' error using the connectivity test.
0
 
Neadom TuckerCommented:
So that sounds like maybe the certificate that you are presenting is not the correct certificate.  Basically what it's telling you is that your PKI chain trust is broken.

I would take a look at the certificate itself and the certificate chain and verify it has a valid trust from the bottom all the way to the top.
0
 
Alan HardistyCo-OwnerCommented:
Where did you get the very from and did you install the Intermediate Certificate from that provider?

Alan
0
 
Roderick WolsiferAuthor Commented:
I just found out it is not a 3rd party cert.  Is it possible to migrate without?
0
 
Neadom TuckerCommented:
Yes like Alan said it has to be trusted.  Office365 will not trust your server.  You can use other services like  MigrationWiz.
https://www.bittitan.com/products/

But a certificate is cheaper.
0
 
Roderick WolsiferAuthor Commented:
Alright, SSL fixed, now getting:
      

        RPC Proxy can't be pinged.
       
      Additional Details
       
An unexpected network-level exception was encountered. Exception details:
Message: The remote server returned an error: (401) Unauthorized.
0
 
Alan HardistyCo-OwnerCommented:
What Auth settings do you have on the RPC virtual directory?  Should be basic and integrated.

If not - set those, run IISRESET and retest.
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.