GWAVA, Inc. Migration Toolkit. For GroupWise to Exchange and Office 365 From edirectory to Active Directory. Version 2.1

Transcription

1 GWAVA, Inc. Migration Toolkit For GroupWise to Exchange and Office 365 From edirectory to Active Directory Version 2.1 GWAVA is a registered trademark of GWAVA, Inc, 100 Alexis Nihon, Suite 500, Saint Laurent, Quebec H4M 2P1 Retain is a trademark of GWAVA, Inc, 100 Alexis Nihon, Suite 500, Saint Laurent, Quebec H4M 2P1 GroupWise and edirectory are registered trademarks of Novell, Inc. Exchange and Active Directory are registered trademarks of Microsoft, Inc.

2 Contents Technical Support... 4 Sales... 4 Overview... 4 Supported Mail Systems... 4 System Requirements... 5 Installation... 7 User Migration Configuration License Novell Settings edirectory GroupWise Microsoft Settings Active Directory Exchange Office Other Settings About User Migration Directory Service Export edirectory Users Create Users in Active Directory Directory Users Matching GroupWise Export GroupWise Users to CSV File Merge edirectory and GroupWise Users List Create Forwarding Rules Export Distribution Lists Exchange Mail Enable Active Directory Users Create Distribution lists

3 Migrate Proxy Rights Office Create Users Office 365 License Create Distribution List Migration Preparation Enable Basic Authentication Setup Impersonation Account Create Throttling Policy and Size Limits Migration Configuration GroupWise Exchange Office Duplicates Default Sender Auto Address Translation Time Zone User List Migration Criteria Others Log File Uninstall Appendix A Common Errors CSV File Notes Appendix B: Exchange settings Exchange Throttling policy Exchange Exchange Exchange Size limits IIS Size Limits

4 Exchange settings Grant Impersonation Permissions to the Retain user Authentication Methods Technical Support If you have a technical support question, please consult the GWAVA Technical Support section of our website at Sales To contact a GWAVA sales team member, please info@gwava.com or call Tel: 866-GO-GWAVA ( ) in North America or Alexis Nihon Blvd. suite 500 Montreal, Quebec Canada. H4M 2P1 Overview The Migration Toolkit automates the process of mail system migrations, removing the difficulties and tedium in creating users and moving mail and system data from GroupWise to Exchange. The Migration Toolkit not only migrates users from GroupWise to Exchange, but does so in steps, allowing for a smooth setup of the Active Directory system. The steps available are Active Directory user, to mail user, to active mailbox, and also a merge for edirectory users with Active Directory. This graduated approach provides options for either a measured setup or rapid deployment. The Migration Toolkit functions from exported CSV files which the toolkit creates. Creation of the CSV file is the sole reason the Toolkit connects to the GroupWise system. Logging into edirectory, the toolkit grabs all user objects and exports them to the CSV file. After the CSV file has been created, the toolkit only needs to have an active connection to Active Directory to migrate users into Exchange. Supported Mail Systems GroupWise , 8.x, 2012 Exchange 2010, 2013 Office 365 Note: Support for Office 365 requires an impersonation account, or an administrator account with builtin impersonation rights. Most licenses of Office 365 include impersonation with the administrator account, though some may not. Ensure that impersonation rights are held by the admin, or an impersonation account can be created. The migration will not function without impersonation. 4

5 System Requirements General o Windows 7 SP1, Windows Server 2008 R2 o.net 4.5 o Windows Management Framework 3.0 o Java JRE 1.6 (64-bit required for 64-bit migration, 32-bit for the 32-bit version of the tool) o GroupWise client (Client version must match server version) Creating Users in Active Directory o Remote Server Administration Tool (RSAT) o Specific Windows features enabled after installing RSAT Active Directory Module for Windows PowerShell Active Directory Administrative Center AD DS Snap-Ins and Command-line Tools Creating Users and Licensing in Office 365 o Microsoft Online Services Sign-In Assistant for IT Professionals o Windows Azure AD Module for Windows PowerShell Windows Workstation The Windows Features required on the workstation are enabled through the Control Panel. Without the Windows features enabled, the Toolkit will fail to function. Control Panel Programs and Features Turn Windows Features On or Off The Migration of users from edirectory to Active Directory is limited to users found in edirectory. External GroupWise users with no entry in edirectory cannot be migrated. 5

6 For Windows Server 2008, install the following: Start Administrative tools Server Manager Select Features from the left pane and then Add Features to open the Features Wizard. Remote Server Administration Tools AD DS and AD LDS Tools AD DS Tools AD DS Snap-Ins and Command Line Tools Active Directory Administration Center AD LDS Snap-Ins and Command Line Tools Active Directory module for Windows PowerShell Complete the install of the required features. 6

7 Installation The installation of the Migration Toolkit is very simple; run the Migration Toolkit Setup and follow the prompts. The setup wizard provides clear instructions on what is going to be installed. Select Next to continue. Read and accept the terms of the License Agreement then select Next to continue. The System Requirements is simply for purposes of the installation. This will not impact the function of the Toolkit, nor will it be imprinted or displayed on any of the users or data migrated to Active Directory. 7

8 The destination folder is default and all other information gathered is displayed. If any of the data is incorrect, select Back and correct the information. To begin the installation, select Next. Select the desired components to install. The installation can be performed for a full, custom, or minimal installation. Select the desired components to install and select Next. Choose whether to create a start menu folder, and what it should be named. When finished, select Next to continue. 8

9 Select whether to include Desktop and Start menu icons, then select Next to continue. The summary of the installation configuration is displayed. Review and make sure that all information provided is as desired, then initiate the install by selecting the Install button. Once initiated, the program will be installed. 9

10 On completion, the installation utility reports on the installation. Select Finish to exit the installation program. To start the Toolkit, select either the start menu or the shortcut icons on the desktop. Make sure to select the desired tool for the toolkit. In order to migrate , the users must already be created in the destination system. If the system users do not exist or have not been migrated yet, run the User Migration first. 10

11 User Migration The user interface contains five menus for use: Configuration, Directory Service, GroupWise, Exchange, and Office 365. Each item will change or highlight when the mouse hovers over them. The Configuration menu is located at the top right of the interface. All action tabs and menus are listed, (Directory Service, GroupWise, Exchange, Office 365), highlighted in dark green when selected and grayed out when not selected. The Directory Service menu is the default menu shown on startup. The Exchange menu option is located in the middle of the interface, and is grayed-out when not in use. When accessing the different options under either the Directory Service and Exchange menus, the icons of the different options must be selected to utilize any specific option. Each time an action item or submenu item is selected a new window will be spawned which appropriately contains the options or work to be completed. All settings will be locked until a proper working license is applied. To obtain a license, create a trusted application key and save it to a file. The license requires the edirectory Tree name and a trusted application key for the system to be migrated. Configuration Before any options or work can be accomplished by the Migration Toolkit, the toolkit must have the configuration completely filled-out. Every item under configuration contains important connection information for the host mail systems. All fields are mandatory. License Before any work can be completed, a valid license file must be provided to the Migration Toolkit. If a license file is lacking or needs to be acquired, please contact the sales representative. To apply a license file, open the configuration menu by clicking on Configuration and select License. In the License window, select the import icon and browse to the location of the 11

12 license file. Select the license file and click Open. The license information will be added to the License window. Select OK to save the license to the system and close the License window. Novell Settings edirectory The Toolkit connects to the edirectory system to create a CSV file containing the users found on the edirectory system. To connect to the edirectory system the Toolkit must have connection information provided. Provide the connection DNS or IP address to the edirectory server and the username and password of a user with administrator rights. The login information may also be saved for use at a later time. To save the login information select the Save to file option. Load from file allows the loading of previously saved login information. To use the current configuration and close the edirectory Configuration window, select the Save button. The TEST button is provided to check that the settings are correct. Pressing the TEST button performs a simple login with provided information. GroupWise To connect to the GroupWise system and migrate mail, the toolkit utilizes a Trusted Application key. This key can be generated inside ConsoleOne or through utilizing the trusted application key generator. All fields except the password are mandatory. The user provided here does not need to have any special rights, the only requirement is that the user is valid on the system. The GroupWise system must be configured for migration to function. Save the configuration to a file before selecting Save to allow easier and faster configuration with future uses. 12

13 Microsoft Settings Active Directory The Toolkit connects to the Active Directory to import users and to activate non-activated mailboxes. This interface has three menus: Active Directory, Exchange, and Office 365. The different menus are selected by clicking on the specific name along the top of the window. For user migration, the Toolkit requires login and address information for the Active Directory or Exchange server. All fields are mandatory. For Active Directory, the login requires the LDAP connection information for an administrator level user. The Default Context is the destination container in Active Directory for the migrated users. This must be an existing location; the tool will not create it. In order to migrate , the Active Directory and either the Exchange or the Office 365 configurations are required, which ever applies to the data destination. Exchange Exchange configuration is similar to that of Active Directory, though the Server name is different and the Username must be a full address and password. The Domain Name used for imported addresses can either be used as specified, or from the CSV file. The Mailbox Database is the name of the Exchange database keeping the mailboxes, and must be the complete name, (i.e. Mailbox Database ). Use the TEST button to ensure that the settings are valid. Make sure that the Windows Machine used has the DNS server which Exchange uses in its list. 13

14 The login information may also be saved for use at a later time. To save the login information select the Save to file option. It is recommended to use clear save names to differentiate between the Active Directory and Exchange configuration files. Load from file allows the loading of previously saved login information. To use the current configuration and close the Configuration window, select the Save button. The Toolkit will not attempt to use the login information or connect to the specified system until a user export is selected. Office 365 Configuration for Office 365 is minimal. After configuring Active Directory, a valid login and password, the domain name to be used, (either from CSV file or the active Office 365 Domain name), and the default location, (Country). If the domain name is not to be taken from the CSV file, then it must be specified below. If multiple domains are needed, the domain setting should be From CSV file, and the CSV file modified accordingly, (destination address column). Multiple Usage locations also require manual modification of the CSV file. Other Settings The Other Settings option contains the default Password Options. When users are migrated, a password is created for them in their profile. This password may either be randomly generated or may be a standard password set as default for all. If the passwords are to be random, a new password is generated for each user migrated. If the password is to be a standard password set as default for all users migrated, then the password may either be specified by the administrator, or it may be randomly generated by the Toolkit. Passwords must be a minimum of 8 characters long, mixed case, with one number and one special character. This is required regardless of server settings. In addition, users may be required to change their passwords on the next login. By default, users will be required to change their password 14

15 on first login. Passwords for successfully created users are saved in the same CSV file used for user creation. The new passwords may be ed to the users. If this option is selected, SMTP settings must be provided. All fields must be configured. About The About page displays the version number and information for the Migration Toolkit. User Migration Directory Service Export edirectory Users Exporting users from edirectory only exports users located in edirectory. This creates a nice clean list of users. To create a list which also contains resources and external users, utilize the GroupWise user export function. To automatically create the CSV file, migrate the users from the edirectory system into Active Directory or Exchange, the users must first be exported from the edirectory system and saved in a CSV file. From the main interface, select the Export edirectory Users to CSV File function by selecting the icon. If configuration is correct, the Toolkit will allow the new system to connect to edirectory without any errors. If there are connection errors, check the configuration for errors or clear up any network issues which would cause the Toolkit to experience problems seeking to connect with the edirectory system. To begin the export, the Toolkit must first create a list of users from edirectory. Select the Load Users button at the bottom right of the window. User information should populate the screen. These are the users which will be used to create the CSV file. 15

16 Once the users have been loaded, select the Export All button to export the users to a CSV file. The export dialog opens a save window. Select the desired location and name for the CSV file and select Save to complete the operation. The export saves two files, users.csv and users.csv.data. The data file contains the data object for each user. Both are required. To close the export window select the close window button on the top right of the window. Once the users have been exported to the CSV file, the work with edirectory is complete. Note: the Toolkit will not migrate any GroupWise user or external entity which does not have an edirectory object. Additional notes on the CSV file can be found in the Appendix. 16

17 Create Users in Active Directory Once the CSV file has been created from the edirectory or GroupWise system, the users may now be migrated into the Active Directory system. When the migration of the exported users is desired, from the main menu, select the Create users in Active Directory from CSV File option. Once the option has been selected, a new window will open for the migration process. When the new window opens, nothing can be completed before the CSV file is selected. To display the CSV file and browse the data without migrating, click on the Browse CSV File button from the top of the window and browse to the desired CSV file. An additional file, CSV.DATA is also created by the toolkit during user export. This file is required for toolkit operation and is automatically loaded if the name is unchanged and it is located in the same directory as the selected CSV file. The file may also be manually selected and loaded by the Browse CSV.DATA File button if the file has been moved or filename changed. 17

18 Once the users have been loaded from the CSV.DATA file, the Start button becomes active and user creation may be started. To begin creation of all users, select the desired users, either specifically, (by selecting one or multiple rows), or through the Select All button, then select the Start button. During migration, the result of each user s attempted creation is displayed. The Toolkit will not create any user which already exists in the system, checked by first and last name. Once the users have been created, the Toolkit updates the initial CSV file. This file now contains each migrated user s GUID number and generated password. Because this file contains additional fields, (GUID, destination context, destination DN, etc.), it is required to enable the mailboxes of created users in Active Directory. Without this information and file, the users cannot be mail enabled. Directory Users Matching The Users Matching option is tailored for use by Administrators with partially migrated systems or systems with duplicate users existing on both systems. The user match option in the Toolkit does not actually manipulate user data between the two systems; however, it does create three CSV files which contain very different information on the users in both systems, and those only in one system. To utilize this feature, both edirectory and Active Directory login settings must be configured and connected correctly. The match function tells the Toolkit to connect to both systems and compare the users in each. The Toolkit then created three CSV files: one which displays users only in Active Directory, another which displays users only in edirectory, and the last file displays users which exist in both systems. For this to work correctly, the users must have the same first name and last name in both systems. The comparison is case sensitive. To use the merge function, select the Directory Users Matching icon from the main window. 18

19 Once the Users Matching tool has finished discovering and comparing the users in both systems, it will create three different CSV files: Users found only in GroupWise, Users only found in Active Directory, and users in both. The files and names are shown. Save all these files for future reference and use. The Merge_NotMergedEDUsers.csv is the file which should be used to create users in Active Directory which have not yet been created in the Active Directory system, but which exist in edirectory. While this may be accomplished by running a full migration on a CSV file containing the entire user list from edirectory, it is best to use a merge CSV file as it only contains the users which need to be migrated, and will result in much better performance. To complete the match, return to the Create Users in Active Directory menu and use the xx_notmergededusers.csv file. The CSV.DATA file created in a standard user export should be used. The process is the same. GroupWise Export GroupWise Users to CSV File The user export function for GroupWise functions identically to the edirectory user export. To use the function, select the Export users option and follow the same process as the edirectory user export. 19

20 Merge edirectory and GroupWise Users List If the GroupWise system contains users which are not listed in edirectory, or visa-versa, the lists can be merged to create a complete list which contains all the users in the system. The Merge edirectory and GroupWise User s List function compares the two lists, and creates one list with all associated data necessary. This function requires that both the edirectory user list, and the GroupWise user list exports have been completed, and the CSV and CSV.DATA files are available. Select the option from the GroupWise menu. After the Merge window opens, browse to and select the appropriate edirectory and GroupWise Users CSV and Data files. The Data file is not required, however it will aid in creating a complete list with data file. Once the lists have been selected, click the Merge button to complete the action. When done, save the combined.csv files and close the window through the X at the top. 20

21 Create Forwarding Rules In the process of migrating users from GroupWise to Exchange, users may have their destination addresses changed. If they are changed, messages sent to the old address will not reach the intended user. To ensure that new mail sent to users in the GroupWise system ends up in their new Exchange or Office 365 mailboxes, forwarding rules may be created. This option requires that users have already been exported and created in the Exchange or Office 365 system, and the appropriate CSV and CSV.DATA files have been saved from the user creation process. Specifically, the CSV file used must have the destination address field filled in as it was created in the Exchange or Office 365 system. Select the Create Forwarding Rules option from the main GroupWise window. Once open, select the Browse File option and select the appropriate CSV file to load the users. Once the users have been loaded, select the desired users to have forwarding rules applied to their accounts by either selecting them manually or by right-clicking and selecting all. The load status button may be used to check any existing forwarding rules for the users. If rules currently exist, it is recommended to utilize the Remove Rules button to clean the slate and ensure that the only rules active in the system are the ones created here. Use the Create Rules button to create new rules. 21

22 Once the rules have been created, the window may be closed. Export Distribution Lists To export distribution lists from GroupWise, the Export Distribution List option should be utilized. Select the option from the main GroupWise page to begin. From the Distribution list window, select Start to load the Distribution list. Select the desired items and select Export. Save the CSV file. 22

23 Exchange Mail Enable Active Directory Users Once the users have been created in Active Directory, they are not yet mail enabled. To mail enable the users which have been created, the CSV file saved after creation is required. Each user s GUID is required for activation, and found in the newly saved CSV file. During the mail enable function, users mailboxes are added to the mailbox db. The mailbox db setting is added to the CSV file during the Create Users in Active Directory operation, if the values in the CSV file and the settings here differ, the CSV file value will be used. If users in the same CSV file are to be placed into different mailbox databases the CSV file should be modified manually. To enable the users, select the Exchange tab from the main Toolkit window to expose the Mail Enable Active Directory Users option. Select the option icon to open the Mail Enable window. Once the window has opened, click the Browse File button and select the CSV file containing the GUIDs. 23

24 The users to be enabled must be selected. Choose to select all or to manually determine which users to enable, and then select the Start button to begin the enabling process. The interface will display the success as well as any errors for each selected user. During mail-enabling users if an address has already been assigned to another user, the address for the new user will be changed and the Status will be shown as Warning. After mail enabling users, the CSV file will be updated and if any address has been changed they will be updated in the file. Create Distribution lists The process for creating distribution lists is identical between Office 365 and Exchange. From the appropriate main window, (either Office 365 or Exchange main window), select the Create Distribution Lists button to open the window. Select the Load Distributions Lists button and browse to the exported distribution list CSV file. If the users data file is not loaded automatically, select the Load Users Data button and select the appropriate CSV.DATA file. Once loaded, the list will display how many members are included and the status. Select the desired lists to be migrated, and then select the Start button to create the distribution lists. Once complete, the window may be closed. 24

25 Migrate Proxy Rights The process for migrating proxy rights is identical between Office 365 and Exchange. From the appropriate main window, select the Migrate Proxy Rights button to open the window. Select the Browse File button and browse to the select CSV file containing the users whose Proxy Rights are to be migrated. Once loaded, the list will display the Name, and Status of all users. Select the desired user(s) who s Proxy Rights are to be migrated by clicking on them, selecting multiple, or using the Select all or Select None buttons along the top. Once the desired users are selected, click the Start button to begin migration. The status will be displayed as the users proxy rights are migrated. Once complete, the window may be closed by clicking on the X at the top of the window. 25

26 Office 365 For Office 365, the process is a bit different than migrating users to Exchange. The process of exporting users from GroupWise or edirectory is unchanged depending on the domain and location usage settings. If multiple domain or usage locations are desired, the CSV file must first be modified before it is ready to be migrated into Office 365. The following configuration is ONLY necessary if the domain and usage location settings in the Office 365 configuration are set to use CSV, or multiple domains or usage locations are desired. Locate and open the exported user list CSV file and find the destination address column. This value is where the migration tool gains both the address and the domain for the new system. If the Office 365 configuration was set to gain the domain from CSV file, or if multiple domains are desired, the destination field must be modified. If it is already as desired, no modification is necessary. The second column to check is usagelocation. This is the country of use for each account. This is specified as the two-digit country code. (ex. US, DE, NL, etc.) (Neither field is required for resources and doesn t need to be modified for those accounts.) As with the domain, the usagelocation field may be modified to reflect multiple different locations as desired. Once the destination address value in the CSV file is as desired, save the file, taking care to make sure that the format is not changed. The file must remain a CSV file. To import the users in the modified CSV file, both the CSV and the CSV.DATA file must be present. Browse to and select the desired CSV file. The toolkit will automatically load the data file from the same location, if it is identical in the file name. If the name has been changed, the file will not be automatically recognized and must be loaded separately. 26

27 Create Users Once the CSV and CSV.DATA files have been loaded, select the users which are to be created in Office 365 and click the Start button to initiate user creation. Make sure to resave the CSV file for the exported users. The new data will be required to license the users and migrate later. The user creation wizard will not automatically exit on completion, and will be available to either create more users or to exit. To exit, close the window. NOTE: After activation, the system will wait as specified in Office365WaitingTime before assigning nicknames. The time setting is found in the Exchange Setting Configuration file. Default is 60 seconds. On slower machines, Office 365 can take up to 5 minutes to have users propagate through the system. This can cause problems when creating resources. Resources should be migrated separately from users, according to the Office365WaitingTime setting. Default is 60 seconds. Administrators can change this setting if desired. If resources are created at the same time as users without modifying the wait time, Office 365 will not recognize any existing user belonging to that resource. The resource will be created without users connected to them as the system doesn t yet recognize that the users exist. Such resources should be deleted and re-created through the migration tool. 27

28 Office 365 License Once the users have been created in Office 365, they must be licensed. To input a license for the users in Office 365, the new data file made by the user creation wizard must be modified with the license information for the system. First, open the License Users window from the Office 365 menu. To get the license information for the host system, select the License Information button. Take note of the license listed in the column code and write it down, as that is the value which must be added to the exported user data file. Open the exported user file and locate the userlicense column. This column must be filled in with the license shown in the License Information window. Modify and save the file, taking care to keep the format as CSV. Once the user file has been modified, browse to and select the file to load it into the License Users tool. Users must be selected before the license will be applied to their accounts. Select the users desired and then click Start to license enable the users in Office 365. Once complete, the users have been licensed in the Office 365 system. To exit, close the window. 28

29 Create Distribution List The process of creating distribution lists in Office 365 is identical to creating distribution lists in Exchange. See that section for details. Migration Preparation Before mail can be input in to the Exchange system, there is some preparation work which needs to be completed. Enable Basic Authentication Setup Impersonation Account Create new Throttling Policy, Including setting the message size limit in Exchange and IIS Enable Basic Authentication Basic authentication is required to allow the Migration tool to log into and input messages into the system. Basic authentication is enabled through the IIS Manager in two places. Open the IIS Manager, the two settings are located under: Server Sites Default Web Site EWS Authentication Enable Basic Authentication Server Sites Default Web Site Autodiscover Authentication Enable Basic Authentication Ensure that both areas have been set. Setup Impersonation Account The impersonation account is required for Exchange and Office 365 for the tool to put mail into the new mailboxes. Note: Small to Midsize business plans do not support impersonation accounts. If you have a small to midsize business plan with Microsoft, you need to use the Admin account. Enter the following command, (with desired system specific variables), into the Exchange Management Shell: New-ManagementRoleAssignment Name:MigrationToolkitImpersonation Role:ApplicationImpersonation User:<admin_user_name> Create Throttling Policy and Size Limits Migrating mail and message data into the new Exchange or Office 365 system may require a larger size limit and throttling settings than default. Modifying these settings will allow for a faster and more successful migration. Increasing the size limit for the migration alone may be problematic as mail input into the system may not be allowed back outside. Keep this in consideration while inputting message data into the new system. In addition, changing size and throttling limits depends on the specific version. Instructions and scripts are provided in Appendix B. 29

30 Migration The Migration tool is the same for all systems involved. However, the mail migration tool needs to be configured, just as the User Migration was. The configuration is mostly the same as the configuration from the User Migration but contains a few different items. The different configuration is required in that the Migration is handling message data, and not users. To configure the Migration, open the Migration interface and then select File Configuration. The Migration Context window contains the entire configuration for the tool. Source and Target Servers are required and their settings must be configured. Select the desired source and target servers from the drop-down menus and then select the Settings button to the right of the menus to configure them. 30

31 Configuration Configuration of the system is simple, and while the system does not automatically remember configuration data from session to session, the data can be saved and loaded from a file. Ensure to save the configuration to a file after a successful test, before selecting the Save button. GroupWise The tool utilizes SOAP with a Trusted Application key to access message data from GroupWise, and both are required to connect to the system. Make sure that SOAP is enabled on the target Post Office, and then list the address and port of the GroupWise Post Office desired. The Trusted Application key needs to be the same key provided to GWAVA Inc. for the creation of the license file, or it will not function. Exchange The Exchange information for the target system must be filled out with the correct address and credentials to get access to add mail into the system. Administrator or Impersonation account user name needs to be UPN format, (User Principal name). Exchange requires an impersonation account with, an address, to allow the migration to function. The Search Domains needs to include the impersonation user, however, multiple search bases may be added; separate them with a semicolon. Office 365 Provide the Office 365 Impersonation account login credentials in UPN. The EWS URL setting is optional, used for manually setting a server instead of relying on autodiscover. (Contact support for help finding the EWS URL, or see The Administrator account is required to input the message data into the different accounts. The test and login requires a direct connection to the Office 365 server. Some security and proxy settings may interfere, ensure a clear connection for functionality. 31

32 Duplicates Duplicate check is the way the migrator keeps message data from being duplicated in the target system. While this setting is not essential to configure for first-time migrations, this is very useful for migrations which were partial or were interrupted and must be resumed or repeated. The duplicate check has three settings: No action, Skip, and Replace. These are self-explanatory. It is highly recommended that the setting be set to either Skip or Replace. The Skip setting will offer the best performance in cases where a user has been partially migrated previously, though the Replace may also be used to ensure that everything is fully present and in the same state as they exist in the GroupWise account. Default Sender All messages will display a sender with a default of the host system; however, this can be modified. The Default Sender must be specified in an format. The mail will have a message stating that the mail is sent on behalf of the original sender information. Auto Address Translation Address Translation changes the destination address to the users current address in Exchange, if the recipients are both listed in the same CSV file. Time Zone time zones are kept in UTC format, but are displayed according to local time zone in the client. The migrator sets the time zone according to the time zone of the local machine, and may cause problems if the time zone is different for the mail being migrated. Select the time zone appropriate to the mail being migrated from the dropdown menu. User List The user list file must be the file created after the Mail Enable operation has been completed or from a merged file. For Office 365, the CSV file must be the one saved after the licensing process was complete. (The Office 365 file must have all three additions or modifications: destinationadress, usagelocation, and office365license.) 32

33 Migration Criteria The Migration Criteria is the scope of the migration. All the data items listed here are, by default, set to be migrated. If it is desired that certain data items are not migrated, unselect them here and they will not be migrated. In addition, often the Exchange or Office 365 system has an attachment size limit and if attachments are oversized, the system will fail to migrate the attachment regardless of the Migration Criteria setting. Make sure that the Exchange and Office limits on attachment size are set to the desired size, or alternately configure the limit here accordingly. Others The other interface holds the options for the personal address book. The migrator does not migrate these by default. Once the configuration has been completed, return to the main window and select Load users. Once the users have been loaded, the desired users must be selected before the start button will become available. To select the desired users, click them with the mouse, or right-click and select all. 33

34 Once selected, click the Start button to begin the migration. The utility will begin migrating the full amount of concurrent migrations at the same time as soon as the process has begun. Users waiting to be migrated are set into the queue. If the migration is stopped during a migration, the utility may be resumed where it last completed. Users which were partially migrated will have their mailboxes migrated again to ensure that all message data was migrated correctly. Ensure that the duplicate setting is configured appropriately. Once complete, the window may be closed. Log File The log files for the Toolkit is stored under the following paths: C:\Users\{user}\AppData\Roaming\GWAVA\MigrationToolkit\User Migrator\logs\user_migrator.log C:\Users\{user}\AppData\Roaming\GWAVA\MigrationToolkit\ Migrator\logs\Migration.log Uninstall To uninstall the Toolkit, run the Uninstall option from the start menu entry. The uninstall process is very simple and simply requires confirmation then the program is uninstalled. 34

35 Appendix A Common Errors Could not create attachment, or Attachment error Usually this is due to one of three problems: 1. The attachment has been deleted, but the referencing it still exists in the system. 2. The attachment has a problem or corruption exists. 3. The attachment is oversized for the Exchange / Office 365 system. Check Office, IIS, or Exchange thresholds and limits. Throttling error Errors encountering a stoppage of all migration until a set amount of time has passed, usually 10 minutes, are throttling errors. This indicates that the system has hit a throttling limit. Check the throttling policy settings in Exchange. Once the error is encountered, the migration tool will attempt to retry the blocked message every second until ten seconds has passed, then checks at ten seconds, twenty, etc.. Up to 300+ second intervals, until the system again is available. CSV File Notes There are several CSV files created by the Toolkit, and it is important to know the difference between them. The CSV file stores the information which not only dictates where the users came from and what their information is, but also contains the information which dictates where and how the users are to be handled. The original CSV file may be modified, or even created manually, to dictate the users and information. For instance, the Default Context column in the CSV file dictates the final context where each user will be created in Active Directory and Exchange. If the CSV is going to be modified or created, there are some things to keep in mind: Column names are case sensitive The separator character is, Abbreviations: CN: Common Name AD: Active Directory XCH: Exchange GW: GroupWise ED: edirectory M / R / O: Mandatory or Recommended or Optional 35

36 Section Attribute Name M / R Notes Creating Users in Active CN M CN in ED Directory firstname, lastname, M At least one of them is required displayname destinationdirectory R this is the AD directory path for the user if not specified the default value in Exchange connection settings will be used destination R If the user is an user it s recommended to provide this attribute for him/her. This address will be set as UserPrincipalName in AD Creating Mailboxes in Exchange CN M CN in ED destination M User s address in XCH This will be set as External Address destinationguid R User s object GUID in AD destinationdn R User s DN in AD mailboxdb R User s mailbox database in XCH If not specified the default value in Exchange connection settings will be used nicknames O This is the nicknames/aliases/proxy addresses of a user. the nickname values are separated with pipe character ( ). e.g. username@domain only username should be entered in CSV file Creatin Users in Office 365 License Users in Office 365 CN M CN in ED displayname M usagelocation M two-char country code e.g. CA, US destination M User s address in Office365 CN M CN in ED office365license M User s plan/license in Office

37 More notes on Office365License: example: beginfinite:desklesspack The first part is the tenant name in Microsoft s cloud service and the second part is the plan s codename. In this example, DESKLESSPACK is the codename for Kiosk User Plan If CN is missing the user will be skipped and will not be displayed in data grid. If other attributes are missing, they are not skipped in the data grid. However, a message will be displayed in the Message column of the data grid. No action will be taken for these users during provisioning process. Appendix B: Exchange settings Exchange Throttling policy Modifying the throttling policy may significantly improve migration performance. Different versions of Exchange use different commands to access and set the throttling policy. To change the throttling policy, use the following provided script appropriate for your version of Exchange. Exchange 2010 New-ThrottlingPolicy MigrationToolkitPolicy Set-ThrottlingPolicy MigrationToolkitPolicy -RCAMaxConcurrency $null -RCAPercentTimeInAD $null - RCAPercentTimeInCAS $null -RCAPercentTimeInMailboxRPC $null -EWSMaxConcurrency $null - EWSPercentTimeInAD $null -EWSPercentTimeInCAS $null -EWSPercentTimeInMailboxRPC $null - EWSMaxSubscriptions $null -EWSFastSearchTimeoutInSeconds $null -EWSFindCountLimit $null - CPAMaxConcurrency $null -CPAPercentTimeInCAS $null -CPAPercentTimeInMailboxRPC $null - CPUStartPercent $null Set-Mailbox <admin_user_name> -ThrottlingPolicy MigrationToolkitPolicy Exchange 2013 New-ThrottlingPolicy MigrationToolkitPolicy Set-ThrottlingPolicy MigrationToolkitPolicy -RCAMaxConcurrency Unlimited -EWSMaxConcurrency Unlimited -EWSMaxSubscriptions Unlimited -CPAMaxConcurrency Unlimited -EwsCutoffBalance Unlimited -EwsMaxBurst Unlimited -EwsRechargeRate Unlimited Set-Mailbox <admin_user_name> -ThrottlingPolicy MigrationToolkitPolicy 37

38 Exchange Size limits The different size limits in Exchange and IIS may cause serious problems with message migration. Any message which is outside the size limit will be refused and fail to be input into the mail system. To check and modify size limits, use the following commands in the Exchange Management Shell: To get current Exchange message size limits: Get-TransportConfig Format-List -Property MaxReceiveSize, MaxSendSize Get-SendConnector Format-List -Property Identity, MaxMessageSize Get-ReceiveConnector Format-List -Property Identity, MaxMessageSize To set Message size to 100MB, or more: Set-TransportConfig -MaxReceiveSize 100MB -MaxSendSize 100MB Get-SendConnector Set-SendConnector -MaxMessageSize 100MB Get-ReceiveConnector Set-ReceiveConnector -MaxMessageSize 100MB 38

39 IIS Size Limits To set the IIS limit to 100MB or more, follow the instructions below and substitute or modify the desired size if necessary. Increasing the maximum received message size is done in two major steps: Step 1: Step 2: Open Windows Explorer Navigate to C:\Program Files\Microsoft\Exchange Server\ClientAccess\exchweb\ews Open the file Web.Config in a text editor such as Notepad Find all XML tags starting with maxreceivedmessagesize= Change existing values to maxreceivedmessagesize=" " Save the file Open a Command Prompt (cmd.exe) Type: cd %windir%\system32\inetsrv Type: appcmd.exe set config "Default Web Site/ews" -section:requestfiltering - requestlimits.maxallowedcontentlength: Run: iisreset Exchange settings The Migration Toolkit requires access to all mailboxes and the ability to create new ones. To accomplish this while maintaining security, it is recommended that a special user is created for the migration toolkit. This user must be granted sufficient rights in order for the Toolkit to function correctly. This user is used wherever login settings are required. The user utilized for the Toolkit should be a mailbox-enabled user with read access to see all other users, groups, resources, and Exchange Servers in the Exchange Forest. The Toolkit user also must have Exchange impersonation rights to every mailbox on every server in the organization to be migrated. The Toolkit user MUST NOT be a member of any Exchange Administrator group, as Exchange denies impersonation rights for all administrator accounts. Additional Impersonation permissions need to be added to the user created for Toolkit. The quickest way to add these rights is through the Exchange Management Shell. After creating the new user in Active Directory, open the Exchange Management Shell. 39

40 Grant Impersonation Permissions to the Retain user. The commands required are different depending on the version of the Exchange Server. Exchange 2010 requires only one command per Exchange system to be issued, whereas Exchange 2007 requires the commands to be run on every Exchange server in the Exchange system to grant required permissions. If the Exchange system contains 2007 and 2010 servers, the different commands must be completed on one server of each type. Exchange 2010 command: For Exchange 2010, the only command necessary for impersonation permissions is: New-ManagementRoleAssignment name ImpersonationAssignmentName Role ApplicationImpersonation User ServiceAccount Where the Name is a name chosen by the administrator and the ServiceAccount is the name of the Migration Tooolkit user. For Example: New-ManagementRoleAssignment Name impersonation-retain -Role ApplicationImpersonation -UserRetain If additional Exchange servers are added to the system after running this command to grant rights to the retain user, the command must be run again to grant rights to the new server. Exchange 2007 commands: ( Toolkit is the name of the Migration Toolkit user, or Impersonation account below) Get-ClientAccessServer Add-AdPermission -UserToolkit -ExtendedRights ms-exch-epi-impersonation Get-MailboxDatabase Add-AdPermission -UserToolkit -ExtendedRights ms-exch-epi-may-impersonate Get-MailboxServer Add-ADPermission -usertoolkit -ExtendedRights Send-As, Receive-As, ms-exch-store-admin 40

41 Authentication Methods The Migration Tool requires Basic Authentication to be enabled on EACH CAS Exchange server in the system. Open Server Manager on Exchange server. 1. In left pane, expand Roles, expand Web Server (IIS), select Internet Information Services (IIS) Manager. 2. A new Connections pane opens, expand your Exchange server object, expand Sites, expand Default Web Site (Multiple Protocols), select EWS. 3. Under heading IIS, open Authentication icon 4. Select Basic Authentication, click Enable in right pane. You can now close Server Manager. 41