Solved

Cutover Migration - Exchange 2007

Posted on 2013-05-16
6
2,613 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
  • 3
  • 3
6 Comments
 
LVL 39

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 39

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
The problems with reply email signatures

Do you wish that you could place an email signature under a reply? Well, unfortunately, you can't. That great Exchange/Office 365 signature you've created will just appear at the bottom of an email chain. What a pain! Is there really no way to solve this? Well, there might be...

 

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 39

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

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.

Question has a verified solution.

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

Suggested Solutions

Microsoft Office Picture Manager was included in Office 2003, 2007, and 2010, but not in Office 2013. Users had hopes that it would be in Office 2016/Office 365, but it is not. Fortunately, the same zero-cost technique that works to install it with …
Read this checklist to learn more about the 15 things you should never include in an email signature.
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
how to add IIS SMTP to handle application/Scanner relays into office 365.

920 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

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now