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: 188.8.131.52
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 = Efirstname.lastname@example.org, 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 email@example.com 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
There problem here lies with RPC/HTTP not configured correctly without the end users using Outlook Connect Anywhere.
Have you looked into using MigrationWiz? It used a differnent mechanism to retrieve and migrate files.
How are things going? As Louis said, the issue is related to the Outlook Anywhere configuration. Please note that there needs a public certificate for the Outlook Anywhere.
Here is a step by step wizard for enabling Outlook Anywhere for your reference:
How are things going? Do you need any other help with this issue?
The error I get is an NSPI error. From what I can see it's related to Autodiscover that is not available in Exchange 2003. RPC over HTTP is working perfectly and has been working for 3 years. The SSL certificate is new and is working fine.
Using MigartionWiz is an option, but I don't want to pay any additional fees.
I still need urgent assistance with this issue.
Actually NSPI is a requirement for the communication to Exchange Server with RPC protocol, not only for autodiscover. I would suggest you submit a Service Request in MOP to get more help about this issue, or you may choose temporarily setup another Exchange Server (with CAS role) for the migration.
How are things going? Have you opened a Service Request for this issue?
Add your internal IP address for mail.penquin.co.za to the hosts file on your server. Let me know if that works.
Unfortunately adding the internal IP to the Hosts file did not resolve the issue.
Could ISA be causing this issue?
RPC and ActiveSync works just fine. The users are able to connect offsite using mail.penquin.co.za with basic authentication.
The NSPI error might be caused by some connectivity issues between your Exchange Server and your local DC. When the Exchange Server cannot query users information from DC, an NSPI error will be reported. So I suggest you test the status of your DC with the Domain Controller Diagnostics Tool first.
Moreover, I sincerely recommend you submit a Service Request from MOP for the issue, and this will lead you to an advanced level support.
I will use the DCDIAG tool. The Exchange server is the BDC, will Exchange still query from the DC?
How do I submit a Service request from MOP?
If your Exchange server is also DC, I believe it will query itself. To submit a Service Request, please logon your Microsoft Online Portal(MOP) with the global administrator account, Choose Admin page, and you should be able to see the Service Request under Support on the left panel. Click and submit your request.
How are things going? Please let me know if there is any update about the issue.
I have logged a service request. I haven't had any feedback.
I have sent a private message to you with the subject <Information Request: Re: I’m attempting migrate my organization using Cutover Exchange Migration. I get an error when I start the migration>. Please send me the ticket number by replying the private message, and you can check and reply the private message with the steps below:
• Go to the Your details section on the right side of the community site.
• Click Private messages.
• Click the subject title of the response to read the message.
• You can reply by using the form in this display."
• Click Submit Reply.