Help with configuring Exchange 2010 for Office 365 migration (Autodiscover)


We are trying to set up a cutover migration from an on-premise Exchange 2010 server to Office 365.  When we create the migration endpoint in 365 if won't connect and comes up with a suggestion to run Exchange Connectivity Test.  When we run that test it errors on the SSl certificate as it seems to be finding the SSL certificate of the domain provider rather than the one on the Exchange Server.  I've found an article saying we need to run a command in EMS as follows:

New-MigrationEndpoint -Name Cutover -MailboxPermission FullAccess -ExchangeServer WIN-blablabla -Authentication basic -ExchangeOutlookAnywhere -RpcProxyServer -SkipVerification

However I've tried to set the variables to something relevant but the commend keeps erroring.  with "The term 'New-MigrationEndpoint' is not recognized as the name of a cmdlet, function, script file, or operable program.

Can someone please help us resolve this issue? We are entering the command as follows:

New-MigrationEndpoint -Name Cutover -MailboxPermission FullAccess -ExchangeServer  myemailservername -Authentication basic -ExchangeOutlookAnywhere -RpcProxyServer -SkipVerification
Gavin ReidAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

Vasil Michev (MVP)Connect With a Mentor Commented:
Well you need to provide credentials, but the cmdlet will ask for them. Other than that, simply insert your exchange server name (for example WIN-NNEFJKNHR5) and OA endpoint (say You will also need to provide a test mailbox even when using the SkipVerification parameter (so include also the -EmailAddress and  -MailboxPermission parameters).
Vasil Michev (MVP)Commented:
The cmdlet needs to be run against EO Remote PowerShell, not the EMS. Also, you need permissions to run it (by default you need to have the "Migration" role assigned).

You should look into the autodiscover issue though, as you will need autodiscover working properly for more than just the migration.
Gavin ReidAuthor Commented:
Thanks Vasil, can you please help me form the command correctly as I'm not sure exactly what variables I need to put in
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Ajit SinghCommented:
Please select Exchange Server -> Microsoft Office Outlook Connectivity Tests -> Outlook Autodiscover to run the test.  If you have any firewall settings, please try temporarily bypassing it at an off-work hour to see if the issue would be gone.

Besides, please refer to Perform a cutover migration of email to Office 365 and make sure you have done everything under the Prepare for a cutover migration section.

Get help from this article to Create migration endpoints:

Hope this helps!
Gavin ReidAuthor Commented:
Just ran the command and got this:

New-MigrationEndpoint : The term 'New-MigrationEndpoint' is not recognized as the name of a cmdlet, function, script
file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:1 char:1
+ New-MigrationEndpoint -Name Cutover -MailboxPermission FullAccess -Ex ...
+ ~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (New-MigrationEndpoint:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
Vasil Michev (MVP)Commented:
You need to have the Migration role assigned in order to run this cmdlet.
Gavin ReidAuthor Commented:
Made sure the user is a member of the migration role in Exchange. Still getting the same error, it's complaining about the very first part of the command as if the syntax is wrong but have copied and pasted the command and just edited the variables
Vasil Michev (MVP)Commented:
Again, the cmdlet needs to be run against Exchange Online, not the on-prem Exchange. And you need the permissions in EO. Make sure to restart the PowerShell session after granting permissions if you havent done so already.

if it's still not working, post a screenshot so we can take a proper look.
Gavin ReidAuthor Commented:
Hi Vasil,
Ok I've managed to log on to Exchange Online properly now using PowerShell. I've logged on to the 365 account and pasted the command:

New-MigrationEndpoint -Name Cutover -MailboxPermission FullAccess -ExchangeServer server001 -Authentication basic -ExchangeOutlookAnywhere -RpcProxyServer -SkipVerification

 I was then prompted for credentials again and I entered the 365 admin account credentials but I then got the following error:

WARNING: An unexpected error has occurred and a Watson dump is being generated: Object reference not set to an instance of an object.
Object reference not set to an instance of an object.
    + CategoryInfo          : NotSpecified: (:) [New-MigrationEndpoint], NullReferenceException
    + FullyQualifiedErrorId : System.NullReferenceException,Microsoft.Exchange.Management.Migration.MigrationService.Endpoint.NewMigrationEndpoint
    + PSComputerName        :
Vasil Michev (MVP)Commented:
You're missing the EmailAddress parameter.
Gavin ReidAuthor Commented:
Thanks Vasil, I added the email address to the command and it worked! Really grateful, I now have a working migration endpoint! Thanks!
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.