Exchange 2003 migration to Office 365


Having an issue here with prepping and getting ready to move over some mailboxes from an Exchange 2003 server to Office 365.  Doing a Staged Migration in case you need to know.   Been running the  Exchange connectivity analyzer and running the Outlook Connectivity test.

Now with Exchange 2003 I know RPC over HTTP needs to be running (and it is).  Outlook webmail works just fine.  
But I cannot continue with the migration because of an issue.

For the most part the test comes back green.  All except for the first part (RPC over HTTP connectivity)

Now Ive gone into IIS on the server and made sure anonymous authentication is unchecked and basic and integrated is check (under the RPC site).

I know I have ports 6001- 6004 open and pointed to the correct server.   I've been on this for hours now, researching and looking to get this working and am unable to do so.

Any help would be greatly appreciated.   thanks!

Here is my test result from the testconnectivity analyzer:

 Testing Outlook connectivity.
  The Outlook connectivity test failed.
 Additional Details
Elapsed Time: 4663 ms.  

 Test Steps
 Testing RPC over HTTP connectivity to server
  RPC over HTTP connectivity failed.
 Additional Details
HTTP Response Headers:
Content-Length: 1656
Content-Type: text/html
Date: Tue, 13 Oct 2015 15:07:48 GMT
Server: Microsoft-IIS/6.0
WWW-Authenticate: Basic realm=""
X-Powered-By: ASP.NET

Elapsed Time: 4663 ms.  

 Test Steps
 Attempting to resolve the host name in DNS.
  The host name resolved successfully.
 Additional Details
IP addresses returned:

Elapsed Time: 201 ms.  


 Testing TCP port 443 on host to ensure it's listening and open.
  The port was opened successfully.
 Additional Details
Elapsed Time: 259 ms.  


 Testing the SSL certificate to make sure it's valid.
  The certificate passed all validation requirements.
 Additional Details
Elapsed Time: 468 ms.  

 Test Steps
 The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server on port 443.
  The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
 Additional Details
Remote Certificate Subject:, OU=PositiveSSL, OU=Domain Control Validated, Issuer: CN=COMODO RSA Domain Validation Secure Server CA, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GB.

Elapsed Time: 401 ms.  


 Validating the certificate name.
  The certificate name was validated successfully.
 Additional Details
Host name was found in the Certificate Subject Common name.

Elapsed Time: 0 ms.  


 Certificate trust is being validated.
  The certificate is trusted and all certificates are present in the chain.
 Test Steps
 The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate, OU=PositiveSSL, OU=Domain Control Validated.
  One or more certificate chains were constructed successfully.
 Additional Details
A total of 2 chains were built. The highest quality chain ends in root certificate CN=COMODO RSA Certification Authority, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GB.

Elapsed Time: 33 ms.  


 Analyzing the certificate chains for compatibility problems with versions of Windows.
  Potential compatibility problems were identified with some versions of Windows.
 Additional Details
The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.

Elapsed Time: 6 ms.  


 Testing the certificate date to confirm the certificate is valid.
  Date validation passed. The certificate hasn't expired.
 Additional Details
The certificate is valid. NotBefore = 10/13/2015 12:00:00 AM, NotAfter = 10/12/2016 11:59:59 PM

Elapsed Time: 0 ms.  


 Checking the IIS configuration for client certificate authentication.
  Client certificate authentication wasn't detected.
 Additional Details
Accept/Require Client Certificates isn't configured.

Elapsed Time: 495 ms.  


 Testing HTTP Authentication Methods for URL
  The HTTP authentication methods are correct.
 Additional Details
The Microsoft Connectivity Analyzer found all expected authentication methods and no disallowed methods. Methods found: Basic
HTTP Response Headers:
Content-Length: 1656
Content-Type: text/html
Date: Tue, 13 Oct 2015 15:07:48 GMT
Server: Microsoft-IIS/6.0
WWW-Authenticate: Basic realm=""
X-Powered-By: ASP.NET

Elapsed Time: 289 ms.  


 Attempting to ping RPC proxy
  RPC Proxy was pinged successfully.
 Additional Details
Elapsed Time: 92 ms.  


 Attempting to ping the MAPI Mail Store endpoint with identity: 1skynet.skynet.local:6001.
  The attempt to ping the endpoint failed.
   Tell me more about this issue and how to resolve it
 Additional Details
The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.

Elapsed Time: 2856 ms.
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.

I'd tell you to scrap what you are doing, and use

Simple, and it just works.  I have used it to migrate from 2003, 2007 and 2010 exchange servers from organizations as small at 10 people to as large as 400.  

To set it up, you just need an admin account on your 2003 server that has access to all the mailboxes.  Setup the destination information, run it in staged migrations.  

When you want to go live with the Office 365, there is actually no downtime, except DNS propagation. Which, can be avoided pretty easily by change autodiscover sessions.

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
Vasil Michev (MVP)Commented:
Seems like incorrect RPC configuration as detailed for example here:

The solution is to change the RPC proxy settings as per:
mkavinskyAuthor Commented:
my ports and registry settings look correct though.  using the default - 6001, 6002 and 6004.   I went ahead and made the registry edit as you provided in the second link and still nothing

same error
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
Office 365

From novice to tech pro — start learning today.