Solved

Cutover Migration - Exchange 2007

Posted on 2013-05-16
6
2,688 Views
Last Modified: 2013-05-17
I am trying to perform a Cutover migration from on-premise Exchange to Office 365.

I am currently trying to create a migration endpoint and am having an issue.

First, for whatever reason, I tried running the commands on the local machine "$TSMA = Test-MigrationServerAvailability -ExchangeOutlookAnywhere -Autodiscover -EmailAddress administrator@contoso.com -Credentials $credentials" and received an error message that the cmdlet was not found (tried in powershell v2 and exchange management shell)

I then connected poweshell to the office 365 account and ran the same command and after the command completed it did not say any info about it being successful.

I then tried the command "New-MigrationEndpoint -ExchangeOutlookAnywhere -Name CutoverEndpoint -ConnectionSettings $TSMA.ConnectionSettings" and received an error that the parameter set cannot be resolved using the specified named parameters.

I am extremely confused as to where and how I create the migration endpoint. Im guessing i would have to do it locally but the command cannot be found.

I appreciate any help,

Thanks
0
Comment
Question by:akus1
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
6 Comments
 
LVL 41

Expert Comment

by:Vasil Michev (MVP)
ID: 39174064
What you need to do is simply enable Outlook Anywhere. You don't need to test this using PowerShell, you can navigate to ExRCA and run the Outlook Anywhere test:

https://www.testexchangeconnectivity.com/

Then, simply login to the portal and create the migration batch. Here's the article just in case:

http://help.outlook.com/en-us/140/ff628719.aspx
0
 

Author Comment

by:akus1
ID: 39174462
Unfortunately, with the new redesigned Office 365 interface it is not possible to simply follow those instructions.

A Migration endpoint needs to be created with the new layout or design.
0
 
LVL 41

Expert Comment

by:Vasil Michev (MVP)
ID: 39174511
If you are using the 'new office', pressing the New migration button will actually walk you over the steps of creating new migration endpoint as well (if this is the first migration you are running). Alternatively, you can first create the endpoint in EAC -> Recipients -> press the ... button -> Migration Endpoints -> New

http://technet.microsoft.com/en-US/library/jj874458(v=exchg.150).aspx#OutlookAnywhere

(look for the Create a migration endpoint for cutover and staged Exchange migration section)

Basically, you need to provide the username/password for on-prem admin account as with the previous version, or if that fails, manual settings (exhcange server and proxy FQDNs)

Once you have created the endpoint you can test it using the PowerShell commands above or ExRCA and continue with the migration.
0
Comparison of Amazon Drive, Google Drive, OneDrive

What is Best for Backup: Amazon Drive, Google Drive or MS OneDrive? In this free whitepaper we look at their performance, pricing, and platform availability to help you decide which cloud drive is right for your situation. Download and read the results of our testing for free!

 

Author Comment

by:akus1
ID: 39174692
As far as I know EAC is only available on Exchange 2013, they are running Exchange 2007. This is why I am lost as far as the powershell commands not working.

I have followed the steps above to a T on the on-premise and Office 365 Powershells.
0
 
LVL 41

Accepted Solution

by:
Vasil Michev (MVP) earned 500 total points
ID: 39174791
Yes, EAC =  Exchange Admin Center in the cloud, the OFFICE 365 EAC. That's where you create the endpoint and/or you run the PowerShell commands, not the on-prem one.

The migration process is basically posing as a client, it uses the settings provided to connect to the on-prem server, fetches the GAL and uses the admin account to fetch all the mailboxes/groups/contacts visible in the GAL.

Again, there is no need to run the PowerShell commands, you can do this using the GUI. It will run the test automatically, you don't need to worry about this. Just make sure you have enabled Outlook Anywhere locally, grant the necessary permissions to the account then follow the instructions in the article above to create the endpoint/run the migration.

If you insist on doing this using PowerShell, make sure you are connected to the correct server (EO). If you are still having problems, it might be due to network issue or incorrect configuration. You can narrow this down by using the Outlook Anywhere test from https://www.testexchangeconnectivity.com/
0
 

Author Comment

by:akus1
ID: 39174851
Awesome, thank you vasilcho!

Worked like a charm. Microsoft should update that config to say that EAC is incorporate into Office 365 now too.
0

Featured Post

Edgartown IT Case Study

Learn about Edgartown's quest to ensure the safety and security of the entire town's employee and citizen data. Read the case study!

Question has a verified solution.

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

How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
This article will help to fix the below errors for MS Exchange Server 2013 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
This Experts Exchange video Micro Tutorial shows how to tell Microsoft Office that a word is NOT spelled correctly. Microsoft Office has a built-in, main dictionary that is shared by Office apps, including Excel, Outlook, PowerPoint, and Word. When …
A company’s greatest vulnerability is their email. CEO fraud, ransomware and spear phishing attacks are the no1 threat to a company’s security. Cybercrime is responsible for the largest loss of money to companies today with losses projected to r…

690 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