Connectivity between the Daemon and Remote Agents

Migration job files are created by the Console and stored in C:\ProgramData\Transend\tmcd\std_jobs. Numbered jobs appear there with a .JOB file extension. After the Daemon successfully transfers a job file to a Remote Agent, the file gets renamed to .OLD (i.e. – 42.job becomes 42.old). Note: Depending on the number of users migrating and the scale… […]

Read More…

Debugging

When troubleshooting an issue, Transend Support may recommend you enable Debugging mode so they can obtain more information about your migration issue or error. To enable Debugging mode, follow these steps: On the Configuration Settings > Optional screen, select the Advanced Options tab at the top. Check the “I know what I’m doing! Edit Advanced… […]

Read More…

Monitoring migration performance

Periodically check the system resources on the Console and Remote Agent machines until you’ve established a baseline of optimized performance. Maxing out your system resources can negatively affect migration performance. Open Windows Task Manager, click on the Details tab and then sort the Name column. Look for the following: TransendMigrationAgent.exe TMAgent.exe TMCMD.exe There will be… […]

Read More…

Monitoring migration progress

You can monitor the progress of your migration from the Transend Migration Console user interface. From the navigation pane, go to Migrations / Run. Find the desired migration job and click the View Progress button next to it. Basic information is viewable including progress, amount of data migrated and the number of items migrated. This… […]

Read More…

Provide log files to Tech Support

If there are problems for which you need assistance, you must collect log files and send them to Transend Support for review. Go to the user migration details for the user in question. In the Jobs column, right click on the job number and choose Generate Debug Report. The default selection will capture all relevant… […]

Read More…

Rerun a migration

If a migration includes users who ended with errors or warnings, you can rerun the migration to include only the users who were not completed successfully. This can save significant time if you need to address problems that only affect a few users, and do not require an adjustment to the configuration settings or user… […]

Read More…

Reviewing migration results

On the Console machine’s navigation pane, click Migrations / Run. Click the View Results button next to the migration job in question. On the progress bar, click on Completed (green) or Failed (red) to show only those results. Click the column headers to sort, for example, by user name or number of warnings. Review the… […]

Read More…

Items that can’t migrate

Sometimes select items cannot migrate or cause the migration to fail or crash. When an item cannot migrate due to corruption, a bad naming convention or otherwise, we recommend you follow the below steps.Rerun the migrationOften a simple Rerun of the migration allows items to migrate that didn’t previous migrate. If the error was caused… […]

Read More…

Transfer ownership of a Google mailbox to a Managed Account

Google supports two types of user accounts, managed user accounts and consumer user accounts. Managed user accounts are under the full control of a Cloud Identity or Google Workspace administrator. In contrast, consumer accounts are fully owned and managed by the people who created them.It can be problematic when someone uses a corporate email account… […]

Read More…

Rollback / Undo a migration

If you have migrated items to a target mailbox with Transend Migration Console, and wish to rollback or undo that migration so that all migrated items are removed from the target mailbox, follow the steps below. Notes:Only items that were migrated with Transend Migration Console can be removed from the target mailbox. No data sent/received/created… […]

Read More…