Connectivity between the Console and Remote Agents

It is recommended to install Console and Remote Agents on the same network segment, if possible. This will reduce latency and optimize migration performance, while reducing the number of potential network roadblocks between them. If you are migrating to or from an on-premises mail server, it is also recommended to locate migration machines as close… […]

Read More…

Recover from a crash

Recovering from a crash happens automatically, for example, after an unexpected machine reboot. Once the machine is back up, the Agent service starts automatically and gathers progress data from any crashed jobs and prepares those for the Daemon to retrieve and pass along to the Console for display. Any user migration job that was in… […]

Read More…

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. Note: The following instructions only apply to the 3.x build of Transend Migration Console. See instructions at bottom of page for 2.x debugging steps. To enable Debugging mode, follow these steps:… […]

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…

Getting Started with Microsoft Defender

In this training session, you’ll learn how to use Microsoft Defender (formerly named Security Center) a cloud-based platform that helps you prevent, detect, and respond to cyberattacks. While Microsoft Defender spans both Microsoft 365 and Entra (formerly Azure), this session focuses on the Microsoft 365 side of the product. This is a huge topic, so… […]

Read More…