Stalker CommuniGate Pro to Kerio Connect migration tool

    CommuniGate to Kerio Connect migration tool (thereinafter cg2kms) is a command line utility converting Stalker CommuniGate Pro mailboxes for Kerio Connect.
    With respect to the parameters specified, cg2kms performs the following actions:  
    An extended IMAP protocol is applied during the migration (it is necessary that the IMAP service is running in Kerio Connect). Thanks to this solution, it is possible to migrate even to a remote host.
    The migration tool should be used at the same host where CommuniGate is installed and it is necessary that it can access the CommuniGate store
   In addition, the CommuniGate server must be disabled, otherwise, data files are locked.
    Master authentication must be enabled for the server in Kerio Connect. Detailed information on Master authentication is provided in the Kerio Connect manual.

Command line parameters

The only parameter required is path to the  CommuniGate store.

Form of the path specification is as follows: cg2kms -path "/var/CommuniGate" [options]

-path PATH
Required parameter. Path to the data store, typically to the "/var/CommuniGate" or "c:\CommuniGate Files" directory.

-domain DOMAIN
Name of the domain to be viewed or migrated.

-user USER
User to be migrated.

-server SERVER
Name or IP address of  Kerio Connect. This parameter is required for the migration. 

-port PORT
Port of the IMAP service at Kerio Connect. This parameter is optional. If not specified the default value 143 is used.

-password PASSWORD
Master authentication password for access to Kerio Connect. This parameter is required for migration.

-setPass PASSWORD
If a single user who uses a password encrypted in CommuniGate, the password specified is used. The parameter is ignored if the user already exists in Kerio Connect.

-forceSetPass PASSWORD
If a single user is migrated, the password specified is used.  The parameter is ignored if the user already exists in Kerio Connect.

-migrate
If this parameter is added, the user will be migrated. If not, information overview is provided by CommuniGate data store.

-force
If migration of a user yet existing in Kerio Connect is initiated, the migration cannot be completed unless the -force is enabled.

-primaryDomain DOMAIN
Name of the primary domain to be used for migration. If this argument is not specifed, the name of computer, from which migration was ran,  is used.

-quiet
This command disables dumps.

-help / -?
This command displays program help. The help is displayed even if no parameters are specified.

Examples

User migration from all domains:
    cg2kms.exe -path "c:/CommuniGate Files" -migrate -force -server localhost -password 12345

User migration from a single domain test.com:
    cg2kms.exe -path "c:/CommuniGate Files" -migrate -force -server localhost -password 12345 -domain test.com

Migration of a postmaster user from the test.com domain:
    cg2kms.exe -path "c:/CommuniGate Files" -migrate -force -server localhost -password 12345 -domain test.com -user postmaster

Passwords

    1. If the -forceSetPass PASSWORD parameter is specified, the password is set to PASSWORD.
    2. If the -setPass PASSWORD is specified and the password saved in the plain format at CommuniGate is detected, the original  CommuniGate password is used. If the password cannot be read  (i.e. it is encrypted), the PASSWORD will be used.
    3. If an unencrypted  CommuniGate password is detected, its value is set.
    4. If a password stored at CommuniGate cannot be read, a new one will be generated.
    All password, both generated and migrated, are stored in the  cg2kms_[datetime].pass file (e.g. cg2kms_2005-05-10_09-35-18.pass).

Migration step-by-step

  1. Disable CommuniGate
  2. Each migration should be physically running at the same server where CommuniGate was running. If it's not, it is necessary to use argument -primaryDomain.
  3. Make sure that you have read rights for the CommuniGate data store 
  4. Start cg2kms by command line including appropriate parameters
    Any information on the migration is logged in cg2kms_[datetime].log (e.g. cg2kms_2005-05-10_09-35-18.log). Only basic information and migration process status for individual folders is listed on the screen.

Copyright

    Copyright (c) Kerio Technologies