Solved

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

Posted on 2016-11-25
11
62 Views
Last Modified: 2016-12-24
Hi,

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 mail.mydomain.com -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 remote.mydomain.com -SkipVerification
0
Comment
Question by:Adam Lydiate
  • 5
  • 5
11 Comments
 
LVL 40

Expert Comment

by:Vasil Michev (MVP)
ID: 41901437
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.
0
 

Author Comment

by:Adam Lydiate
ID: 41901441
Thanks Vasil, can you please help me form the command correctly as I'm not sure exactly what variables I need to put in
0
 
LVL 40

Accepted Solution

by:
Vasil Michev (MVP) earned 500 total points
ID: 41901514
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 mail.domain.com). You will also need to provide a test mailbox even when using the SkipVerification parameter (so include also the -EmailAddress and  -MailboxPermission parameters).
0
Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

 
LVL 11

Expert Comment

by:Kevin k
ID: 41901518
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:
https://technet.microsoft.com/en-IN/library/jj874458(v=exchg.150).aspx

Hope this helps!
0
 

Author Comment

by:Adam Lydiate
ID: 41901551
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
0
 
LVL 40

Expert Comment

by:Vasil Michev (MVP)
ID: 41901597
You need to have the Migration role assigned in order to run this cmdlet.
0
 

Author Comment

by:Adam Lydiate
ID: 41901611
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
0
 
LVL 40

Expert Comment

by:Vasil Michev (MVP)
ID: 41901631
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.
0
 

Author Comment

by:Adam Lydiate
ID: 41901685
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 remote.domain.co.uk -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        : outlook.office365.com
0
 
LVL 40

Expert Comment

by:Vasil Michev (MVP)
ID: 41901864
You're missing the EmailAddress parameter.
0
 

Author Closing Comment

by:Adam Lydiate
ID: 41904061
Thanks Vasil, I added the email address to the command and it worked! Really grateful, I now have a working migration endpoint! Thanks!
0

Featured Post

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
one user won't sync with O365 3 52
Email forward and auto reply 4 36
Graph API & MS Apps 1 22
Using isinteg or eseutil with Exchange 2010 6 11
Adoption of Microsoft’s Enterprise Mobility and Security solution and Office 365 will re-order the File Sync and Share market Microsoft has stated that its Enterprise Mobility + Security (EMS) is the fastest growing product in the history of the …
A list of top three free exchange EDB viewers that helps the user to extract a mailbox from an unmounted .edb file and get a clear preview of all emails & other items with just a single click on mailboxes.
This lesson covers basic error handling code in Microsoft Excel using VBA. This is the first lesson in a 3-part series that uses code to loop through an Excel spreadsheet in VBA and then fix errors, taking advantage of error handling code. This l…
This video discusses moving either the default database or any database to a new volume.

856 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question