A Transend Corporation White Paper Preparing Microsoft Office 365 for Migration Copyright December 2012 by Transend Corporation
Table of Contents Section 1: Introduction... 1 Section 2: Benefits of Using EWS... 1 Section 3: Basic Requirements... 1 Section 4: Collecting Office 365 Server Settings... 2 Section 5: Assign Global Administrator Permissions (for batch processing)... 3 Section 6: Install and Configure Windows Powershell... 3 Section 7: Connect Windows Powershell on your Local Computer to the Cloud-based Service... 4 Section 8: Assign the Admin Permission to Open a User Mailbox... 5 Section 9: Assign the Admin Permission to Open All User Mailboxes... 5 Section 10: Disconnect Windows Powershell from the Cloud-based Service... 6 Section 11: Enable EWS Impersonation or Delegation in Transend Migrator... 7 Section 12: Technical Support... 8
Section 1: Introduction This Preparation Guide provides an overview of preparing Microsoft Office 365 for migration using Exchange Web Services (EWS). This document is not intended to include every possible configuration, but instead gives an overview of the common configurations so that you can adjust as needed. Section 2: Benefits of Using EWS The following represents benefits of using EWS to migrate data into Office 365: Does not require MAPI - Means that Outlook does not need to be installed. Migrate all Data Types - Supports the migration of Email, Address Books, Calendars and Task/To-Do items. Batch Mode - Can be used to migrate a single user mailbox or multiple users in Batch Mode. Admin Account - Supports the use of an Admin account to migrate multiple users while only using the Admin s password (does not require each end-user password). Section 3: Basic Requirements The following list contains the basic requirements for migrating data to or from Office 365: Windows operating system (XP/2003/Win7/2008). An active Office 365 account (all accounts must be created and active). Office 365 Server Settings. Password for single user migration. Administrative access for batch migrations. PowerShell for assigning administrative access when batch processing. Page 1 of 8
Section 4: Collecting Office 365 Server Settings 1. Log into your Office 365 email account and click on Options. 2. Click on See All Options 3. Select Account and then My Account. 4. Click on Settings for POP, IMAP, and SMTP access and record the IMAP settings. Page 2 of 8
Section 5: Assign Global Administrator Permissions (for batch processing) When migrating multiple users, it is easier to migrate with an administrative account so that you do not need to provide a password for each user. If you have the password for each user then you can bypass the following steps. The following steps explain how to assign permissions to an account so that you can migrate any account without the need for a password. 1. Log into Office 365 using the Administrative logon. 2. Select Users from the Management shortcut. 3. Select a user who will be given permission to migrate email open the user information by selecting it. 4. Choose the Settings tab. 5. Assign the Global Administrator role to this person under the question that asks, Do you want this user to have administrator permissions? 6. Save these changes. Section 6: Install and Configure Windows Powershell Install and configure Windows PowerShell. Connect Windows Powershell to the service. Review this Microsoft Support article for more details. Page 3 of 8
Section 7: Connect Windows Powershell on your Local Computer to the Cloud-based Service 1. Click Start > All Programs > Accessories > Windows PowerShell > Windows PowerShell. 2. Run the following command: 3. 4. In the Windows PowerShell Credential Request window that opens, type the credentials of an account in your cloud-based organization. When you are finished, click OK. 5. Run the following command: Note: The AllowRedirection parameter enables cloud-based organizations in datacenters all over the world to connect Windows PowerShell to the cloud-based service by using the same URL. Page 4 of 8
6. Run the following command to enable the execution of scripts on your system: 7. Run the following command: A progress indicator appears that shows the importing of commands used in the cloud-based service into the client-side session of your local computer. When this process is complete, you can run these commands: 8. Start Transend Migrator. 9. From the menu, select Migration Options. 10. Select Custom Options. 11. Select Exchange Web Services. 12. Choose the /AUTHEWSI custom option. 13. Enter the Admin user and password, and then enable this switch. Section 8: Assign the Admin Permission to Open a User Mailbox Section 9: Assign the Admin Permission to Open All User Mailboxes Page 5 of 8
Section 10: Disconnect Windows Powershell from the Cloud-based Service Important If you close the Windows PowerShell window without disconnecting from the server-side session, your connection will remain open for 15 minutes. Your account can only have three connections to the server-side session at one time. When you're finished using the server-side session, always disconnect Windows PowerShell by running the following command: Remove-PSSession <session variable> For example, to disconnect from the server-side session that is defined by the $Session variable, run the following command: Remove-PSSession $Session After you have connected to the server-side session, you are ready to perform tasks in the Office 365 cloud based service. For detailed instructions, see Use Windows PowerShell in Exchange Online. Page 6 of 8
Section 11: Enable EWS Impersonation or Delegation in Transend Migrator 1. Start Transend Migrator. 2. Select Migration Options from the Menu, then select Custom Options. 3. Enable the /AUTHEWSI switch option and enter the administrative account, email address, and password using the syntax example shown above. 4. Press the OK button. 5. Save your configuration. 6. Begin migration when you are ready. Page 7 of 8
Section 12: Technical Support Technical support is available to help you understand how to use Transend Migrator with your migration project. Please review the Help File and online resources before contacting technical support. Technical support is available Monday through Friday, 9:00AM - 5:00PM (Pacific Time). You are encouraged to submit questions through email. This will allow us time to properly research your situation and make appropriate recommendations. Email: tech.support@transend.com. Phone: (650) 324-5370 Transend Corporation 225 Emerson Street Palo Alto, CA 94301 (650) 324-5370 www.transend.com Page 8 of 8