Sign up for Office 365
Learn more about Office 365
Hi. Please assist
I’m attempting migrate my organization using Cutover Exchange Migration. I get an error when I start the migration.
Microsoft Server 2003 R2 32bit
Exchange 2003 SP1
Office 365 E1 Account
Create a new migration
Select Exchange 2003
Enter Admin details
Enter domain and proxy details
Select amount of mailboxes
We weren't able to connect to the remote server. Please verify that the connection 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.
Permission to all mailboxes allocated to admin account
Check RPC over HTTP on testexchangeconnectivity.com.
Testing RPC/HTTP connectivity.
The RPC/HTTP test failed.
Attempting to resolve the host name mail.penquin.co.za in DNS.
The host name resolved successfully.
IP addresses returned: 18.104.22.168
Testing TCP port 443 on host mail.penquin.co.za to ensure it's listening and open.
The port was opened successfully.
Testing the SSL certificate to make sure it's valid.
The certificate passed all validation requirements.
ExRCA is attempting to obtain the SSL certificate from remote server mail.penquin.co.za on port 443.
ExRCA successfully obtained the remote SSL certificate.
Remote Certificate Subject: CN=mail.penquin.co.za, OU=Penquin, O=PENQUIN AIRTIME, L=Johannesburg, S=Gauteng, C=ZA, Issuer: CN=Thawte SSL CA, O="Thawte, Inc.", C=US.
Validating the certificate name.
The certificate name was validated successfully.
Host name mail.penquin.co.za was found in the Certificate Subject Common name.
Certificate trust is being validated.
The certificate is trusted and all certificates are present in the chain.
ExRCA is attempting to build certificate chains for certificate CN=mail.penquin.co.za, OU=Penquin, O=PENQUIN AIRTIME, L=Johannesburg, S=Gauteng, C=ZA.
One or more certificate chains were constructed successfully.
A total of 3 chains were built. The highest quality chain ends in root certificate CN=thawte Primary Root CA, OU="(c) 2006 thawte, Inc. - For authorized use only", OU=Certification Services Division, O="thawte, Inc.", C=US.
Analyzing the certificate chains for compatibility problems with versions of Windows.
No Windows compatibility problems were identified.
The certificate chain has been validated up to a trusted root. Root = Eemail@example.com, CN=Thawte Premium Server CA, OU=Certification Services Division, O=Thawte Consulting cc, L=Cape Town, S=Western Cape, C=ZA.
Testing the certificate date to confirm the certificate is valid.
Date validation passed. The certificate hasn't expired.
The certificate is valid. NotBefore = 10/4/2011 12:00:00 AM, NotAfter = 10/3/2012 11:59:59 PM
Checking the IIS configuration for client certificate authentication.
Client certificate authentication wasn't detected.
Accept/Require Client Certificates isn't configured.
Testing HTTP Authentication Methods for URL https://mail.penquin.co.za/rpc/rpcproxy.dll.
The HTTP authentication methods are correct.
ExRCA found all expected authentication methods and no disallowed methods. Methods found: Basic
Testing SSL mutual authentication with the RPC proxy server.
Mutual authentication was verified successfully.
Certificate common name mail.penquin.co.za matches msstd:mail.penquin.co.za.
Attempting to ping RPC proxy mail.penquin.co.za.
RPC Proxy was pinged successfully.
Completed with HTTP status 200 - OK
Attempting to ping RPC endpoint 6001 (Exchange Information Store) on server mail.penquin.co.za.
The endpoint was pinged successfully.
RPC Status Ok (0) returned in 841 ms.
Testing the Name Service Provider Interface (NSPI) on the Exchange Mailbox server.
An error occurred while testing the NSPI RPC endpoint.
Attempting to ping RPC endpoint 6004 (NSPI Proxy Interface) on server mail.penquin.co.za.
RPC Status Ok (0) returned in 342 ms.
Testing NSPI "Check Name" for user firstname.lastname@example.org against server mail.penquin.co.za.
An error occurred while attempting to resolve the name.
An RPC error was thrown by the RPC Runtime process. Error 1717 UnknownIf
Thanks for the feedback.
I noticed your Service Request has been closed. If the issue has been fixed in your side or is no longer existing, please update in the forum.
I resolved this issue myself. My Exchange server wasn't set as a global catalog. After this change the migration started and migrated successfully.
Tks ShaunSwan1 it woks for me too! :)
0 out of 1 people found this post helpful.