Zarafa Updater Service. The zarafa updater service runs as a local system account. Therefore, it has all the needed privileges to install the Zarafa Windows Client on the desktop. The zarafa updater service will wait on a pipe for Zarafa launch updater application to send it the current version of the client and the details of the Zarafa Server to connect to. The zarafa updater service launches this update for installation in a silent mode.
Although the entire update process is silent, logs will be generated for troubleshooting. These files are sent to the server depending on the server settings. The client will only find updates successfully if the default Outlook profile is configured to work with a Zarafa Server, and if updates are available at that server. Please refer to the User manual on how to configure Outlook profiles. Zarafa Updater status. The zarafa-server reports the status from the Zarafa client updater in the server.
The zarafa-admin reports the latest status of the client update. When a client update failed, the log files are located in the directory configured in the server. MSI Options. If you rather push the zarafa client installation from your Windows Domain server, you probably want the installation not to install the Zarafa Updater Service. The following options can be used to achieve that:. To install this feature too, add Updater to this option.
Leave this option to normally install in the "Program Files" directory. Make the installation quiet. No graphical interface will be shown. To show progress of the installation, use the modifier b for basic gui or r for reduced gui.
If you show the full gui f modifier , it will be interactive. With this. See the Knowledge Base article for the installation and configuration of Exmerge. The Zarafa Migration Tool is then used in the next stage to import these. Zarafa to PST Migration. The Zarafa Migration Tool can export pst files from Zarafa server user stores. The tool will create one pst per user store. Scalix to Zarafa Migration Tool. However, this can only be done with the zarafamigrationCmdLine.
This manual is intended for users of the Zarafa Migration Tool. This document will explain how to conduct the different migrations available. Chapter 2. Migrating Public Folders. Before installing the Zarafa Migration Tool make sure the Zarafa Server is installed and configured on the Linux server. The Exchange server or pst files used as data-source are available. NET framework 3. Before starting the Migration Tool, make shure all the. NET packages are updated to the most recent released version.
When closing the migration before completing the installation it is possible to save the configuration. This option is available when closing the migration tool in a dialog. When restarting the migration tool the saved values are picked up so the migration an continue. The tool can also be run from the command line by issuing the command zarafamigrationCmdLine. If run with --help it will show the available options. If a config. See the Chapter 5, Appendix A; Configuration options command line tool for a peek at config file format.
Starting the Migration Tool. To install the Migration tool run zarafamigrationtool. Select Type Of Migration. In the welcome screen click link corresponding to the type of migration that is going to be conducted. The first page will be about setting Logging and Filters amoung others. The following two pages will differ depending on the chosen migration type see next three chapters. After which the rest of the input pages are common to all migration types.
At the first page it is possible to set a number of parameters controlling the migration. It is possible to specify another log file name and location then the default one ZarafaMigration. Click browse and select file. It is possible to select another logging level. By default info logging level is used 3. Change values in the drop down menu. If migration of deleted items is wanted tick the check box Migrate Deleted Items Folder.
If filtering of old items is wanted, enter the date for which to filter the stores with. If use date filter is checked, items older then the specified date will be excluded in the migration.
Source and destination configuration. Exchange To Zarafa Migration. In the Exchange Server Page enter either a pre created Outlook admin profile or enter the Exchange server name and admin user and password.
By selecting either server address or profile radio-buttons. Click next. A connection test is performed, of which the progress is shown in status field at the bottom left. When the test is successful, the next page will be shown.
On the Zarafa Server Page the address of Zarafa Server instance should be provided, by default port will be added. If another port is used this should be specified with a colon after the host name. Consequtively the admin users credentials should be supplied. Again a connection test is performed, of which the progress is shown in status field at the bottom left. In case unicode files are provided the migration tool should be told so by checking the appropriate check box.
This supports large files, up to 20GB. This option can only be used if using Outlook and higher. If not ticked a maximum size of 2GB will be used. See Figure 2. If Unicode file format is to be used tick the check box.
This support large files, 20GB. If not ticked a maximum size 2GB will be used. Click Next. Account User Mapping. If no. If the. It is important that these 2 columns are defined with a column head on the first line of the.
The column heads indicate in what order the data is presented in the rest of the file. Column heads are case sensitive. Any extra columns will be ignored. Do not include any spaces between column heads. Template files for each migration file can be found in migration tool program directory.
To find out the correct user store string for the user to be migrated, log into the MS Exchange server using an admin account. Four alternatives exist to find the info:.
This is the easiest method, it allows to completely export all users into a CSV for use with the Zarafa migrator. Open a command prompt and run the following command:. Now simply open it up in an editor and remove the DN column.
This way it can be used with the migrator tool. Switch explanation: -f path to save the csv, -d folder from which to export users, -r object type, -l properties to export. If desired switch sAMAccountname for mail to use the email as the username for the users. Once connected expand the Default naming context container until finding the container in which the users reside. Right click on the user and choose Properties , scroll through the list until legacyExchangeDN is shown.
Double click the entry and copy the value. This value can then be used in the CSV file. Open the address book and find the user to be migrated. In the main address book view you find the store address in the field E-mail Address. Users in the same exchange server are usually prefixed with the same default, so usually it is enough to find it out only once and then only change the last cn part. Migration Progress. Click start migration, the progress will be indicated by the three progress bars.
0コメント