How to perform a server migration to MDaemon using the ActiveSync Migration Client

The ActiveSync Migration Client will migrate all data a user has access to via ActiveSync on a source mail server into MDaemon, so offers a good solution when migrating data from Exchange 2010 onwards or Office365 to MDaemon.

The migration tool uses the ActiveSync protocol to pull data from any source server that supports ActiveSync version 14.1.

Special Considerations

  • For Exchange migrations, Exchange Server 2010 SP1 and higher are supported for use with the ActiveSync Migration Client.
  • It is recommended to disable the Public and Shared folder during the majority of the migration.  The migration tool will consider all folders each user has permissions to view as personal folders.  Having public and/or shared folders enabled while performing the migration will result in public and shared folders synced for each individual account.
    • o   Best practices in regards to migrating public folders is to follow these steps:
      1. Disable syncing Public and Shared folders via ActiveSync on the original server.
      2. Follow the article and add all users to the input.txt file with the exception of one account.
      3. Once finished, enable public folders sync on the original server.
      4. Rebuild the input.txt file for the single remaining user.
      5. Perform the sync command.
      6. The public folders should now be synced to the user’s personal folder location.
      7. Cut/Paste these folders to the \MDaemon\Public Folders directory.
  • For migrations from Office 365, the server name outlook.office365.com will be used. You must also use /SSL to force the ASMC to use a SSL connection.
  • Servers may require SSL connections and so the /SSL switch needs to be used.

There are three parts to the migration.  

  1. Migrating all of the mail and PIM data for specified users from the host server to the server the migration is taking place.  
  2. Importing the accounts to the MDaemon server.  
  3. Rebuilding the Reminders.dat file from the user’s data.

Installation

The ASMC.exe and RemRebld.dll files are located in the \MDaemon\App directory. The ActiveSync Migration Client is a command-line tool and does not require an installation.

Command Line Parameters

To connect to the source server, the ActiveSync Migration Client uses a /InputFile parameter which points to a text file that contacts the source server’s name, user login (email address), and password to the account.  

The file type used for the /InputFile parameter should be in a comma-separated value (CSV) or tab-delimited file.

The /LogFile parameter will generate a log file will be written out to a specified directory.

The /OutDir parameter to specify a preferred path if necessary.  The tool will write the user’s migrated data to the \MDaemon\Data directory, by default. 

There are several more parameters that are not required but can be used:

  • /InputFile:String : [Required] Input File (Hostname source | Email address | Password).  Can be a Tab Delimited File or a Comma Delimited File.  Named columns aren’t supported.  Example to follow.
  • /LogFile:String : [Required] Log File (mirrors console logging to text file)
  • /OutDir:String :  Output Directory [Required for initial migration when NOT run on an MDaemon Server]
  • /XmlDir:String : XML Archive Directory (Required if /WBXML parameter is used)
  • /ImportFile:String : Pathname of CSV file for MDaemon to import accounts from.
  • /ThreadCount:UnsignedInteger : Number of concurrent migration threads [Default = 4]
  • /WindowSize:UnsignedInteger : Number of items to retrieve per transaction with the server [Default = 10]
  • /DNSTimeout:UnsignedInteger : DNS Resolver Timeout [Default = 15 seconds]
  • /ConnectTimeout:UnsignedInteger : Connection Timeout [Default = 30 seconds]
  • /SendTimeout:UnsignedInteger : Send Timeout [Default = 60 seconds]
  • /ReceiveTimeout:UnsignedInteger : Receive Timeout [Default = 60 seconds]
  • /SSL:Boolean : Use SSL [Default = False]
  • /WBXML:Boolean : Archive WbXml Data [Default = False] Requires /XmlDir
  • /Audio:Boolean : Add audio feedback for notifications [Default = False]
  • /ReSync:Boolean : Remove destination data and perform Initial Syncs [Default = False]
  • /RebuildReminders:Boolean : Processes previously migrated users and rebuilds Reminder.dat [Default = False]
    • o   This parameter must be run on an MDaemon server
    • o   User’s must exist on the server prior to running this parameter
    • o   Must NOT be used in conjunction with /ReSync

Pathnames (Strings) that have spaces present in them must be enclosed in double quotes.

Example:

/InputFile:C:\Migration\MigrationUsers.txt 

Vs.

/InputFile: “C:\Migration\Migration Users.txt”

Part 1 – Data Migration using the migration tool

By default, the migration will write all the migrated data to the \MDaemon\Data\DomainName directory.  If you want to write the migrated data to a specified location, you’ll need to use /OutDir parameter.

Considerations:

  1. MDaemon version 16.0.0 or higher has been installed on the destination server (we recommend the latest version of MDaemon) 
  2. The version of the source server must be version 12.0.0 or higher (14.0.0 recommended) with ActiveSync enabled.
  3. The domain to be migrated has been created in the destination server.

Steps:

  1. Create a new text file. If using a comma-separated value format, populate the text file with comma separations like this:

If using a tab-delimited format, the syntax would contain a tab between values

  1. Save the CSV/TSV file to a directory that will be referenced later.
  2. Open a Command Prompt
  3. Use the CD command to navigate to the \MDaemon\App directory.
  4. Use the ASMC command in front of the migration code syntax.
    The example below references the CSV/TSV file, creates a log file, output data to the \MDaemon\Users\(domain)\ directory, and creates a CSV file to import users into MDaemon.

    C:\MDaemon\App>ASMC /InputFile:C:\migration\input.txt /LogFile:C:\migration\log\logfile.txt /Outdir:C:\MDaemon\Users\company.mail /ImportFile:C:\MDaemon\APP\UserImport.csv

Part 2 – Importing accounts into MDaemon

In this example, the /ImportFile:C:\MDaemon\App\UserImport.csv string in our command line will create a CSV file in the \MDaemon\App folder.  This file is used to import the users into MDaemon.

  1. Launch MDaemon
  2. Select Accounts
  3. Select Importing
  4. Click Import accounts from a comma delimited text file…
  5. Navigate to the \MDaemon\App directory 
  6. Select the UserImport.csv file

Part 3 – Rebuild the reminders.dat file 

This step is required if you want the migrated calendar and event items to have MDaemon’s server-based reminder emails sent to clients.  This is useful if a user is using an IMAP client in some situations where they do not have access to their calendar or task information.  This has no bearing on altering the behavior of any ActiveSync Client or CalDav client as for its display of reminders. 

  1. Open an elevated command prompt
  2. Use the CD command to navigate to the \MDaemon\App directory.
  3. Use the ASMC command in front of the following command.
    C:\MDaemon\App>ASMC /InputFile:”C:\migration\input.txt” /LogFile:C:\migration\log\logfile.txt /RebuildReminders

Migration Exceptions 

The ActiveSync migration tool will only sync fields that are available in the ActiveSync 14.1 protocol.  The following data is not migrated from WorldClient webmail or other servers. 

  1. Calendar
    • o   Priority Field – results will show normal regardless after migration
  2. Contacts
    • o   Blackberry PIN
    • o   Webpage (Home)
  3. Tasks
    • o   All fields under the details tab
    • o   Percentage complete – ActiveSync uses either complete or not complete
    • o   Status field will either be Not started or Finished
    • o   Priority Field
    • o   Private Flag
Copy link
CopyCopied
Powered by Social Snap