Difference between revisions of "MTK GroupWise to PST Migrator Configuration"
From GWAVA Technologies Training
(Created page with "==GroupWise To PST Configuration== Before any migrations can be done the tool must be configured. Access settings and license through the gear menu ===Import License=== The ...") |
Latest revision as of 20:41, 23 June 2017
Contents |
[edit] GroupWise To PST Configuration
Before any migrations can be done the tool must be configured. Access settings and license through the gear menu
[edit] Import License
The first thing that must be done is to import the license. This is a separate license from the main MTK license.
Open gear Menu | License, click on Import and browse to the license PEM file.
[edit] Configure Settings
Open gear Menu | Setting page, and fill in the data.
[edit] GroupWise
- Post Office IP address: The IP address of the post office being migrated from
- Post Office Port: 1677 by default
- SOAP Port: 7191 by default
- Admin username: The username of an admin user
- Trusted App Name: The name of the trusted application key, case sensitive
- Trusted Application Key: The key, case sensitive
[edit] Archive Location
If you have GroupWise personal archives to be migrated place them all in a folder and enter the path to that folder here.
- Enable "Append UserID to Archive Location", if desired.
- Enable "Append Sub-Directories to UserID" and enter a prefix, if desired
[edit] PST
- Set the location where the PST files will be exported to.
- Set the File size limit. Outlook 2010, 2013, 2016 allow PST files of up to 50GB, Outlook 2007 allows up to 20GB, while Outlook 2002/XP allows up to 2GB. The larger the file the slower Outlook becomes. [1]
Save the settings to file. You will be able to Load these setting from file for the next session after you close the program.
Press Save to begin this session.
Return to Retain_Migration_Toolkit