Transend Remote Agent

To install Transend Remote Agent:

1. Dowload the installer.
2. Select Save File.
3. Click the downloads folder in your directory and select Transend Remote Agent.exe.
4. Read the installation notice and click Install.
5. Once installation has completed, click Finish.

Important:

• Transend Remote Agent(s) should only be installed on remote machines that have been configured (for scalability purposes) to act as additional migration machines in concert with the Console machine.
• Ensure each Remote Agent install is the same version as the Console.
• If performing your migration on a single workstation, Transend Remote Agent install is not required. The Migration Console installer includes its own Local Agent.

Firewall

Open TCP port 18971 for inbound communications in your Remote Agent machine’s firewall settings.

Antivirus / Windows Defender / Malware Scanners

These will interfere with and considerably slow down migration processing. It is recommended you disable all scanning software during migration processing.

Alternatively, set the following folders and processes exemptions from being scanned: Folders to exempt from scanning:

• C:\ProgramData\Transend
• C:\Windows\Temp C:\Program Files\Transend Migration Agent — applies to Remote Agent machine only
• C:\Program Files\Transend Migration Console — applies to Console machine only
• C:\Program Files (x86)\Transend Corp\Console Services
• C:\Users\AppData\Roaming\Transend Migration Agent — applies to Remote Agent machine only
• C:\Users\AppData\Roaming\Transend Migration Console — applies to the Console machine only

Processes to exempt from scanning:

• tmagent.exe
• tmcd.exe
• tmcmd.exe
• tmo64a.exe
• Transend Migration Agent.exe — applies to Remote Agent machine only
• Transend Migration Console.exe — applies to Console machine only

(OPTIONAL)

Using network drives with a Remote Agent

If you are using a network file share for source or target data, detached files location or deduplication files location, you must use a UNC path, not a mapped drive letter within the Console configuration. Additionally, you must change the logon account used by the Agent service, as follows:

• Open Windows Services
• Find and double click Transend Agent Email Migration
• On the Logon tab, change from “Local System account” to “This account” and enter the appropriate local or domain user account credentials
• Restart the service for the change to take effect

Once Remote Agents are installed on Remote Machines, you must register your Remote Agent Machines in the Console UI. This allows the Console to connect to the Remote Agent Machines to distribute migration jobs and retrieve progress updates.

1. In Transend Migration Console, click on Scale > Remote Machines from the top menu
2. Click the Add button to add a new row to the table
3. Enter the IP address or fully qualified domain name of the Remote Agent Machine
4. (Optional) If the Console must connect to the Remote Agent Machine via a proxy server, enter the Proxy Host and Proxy Port information. Otherwise leave those blank
5. Add more rows for additional Remote Agent Machines, if necessary
6. Mark the checkbox next to the Remote Agent Machine to enable it for migration
7. Click the Test Enabled button. The Daemon service on the Console will attempt to connect to the Remote Agent Machine with the address you supplied. View the Status column to determine success or failure
   • Note: If the connection attempt fails, make sure you entered the correct address. Also, check that the service is running on the Remote Agent Machine and that TCP port 18971 is open on its firewall
8. Click Save to save your Remote Agent Machine information
9. You may add or remove Remote Agent Machines as needed

Transend Remote Agents are able to run on virtual or physical machines and servers. Disable Anti-virus – we recommend disabling anti-virus on all machines performing migrations. For more detail please see the Configure Remote Machines tab. System Requirements

• Windows 8 or 10, or Windows Server 2008, 2012 or 2016 with current Service Packs.
• 4 CPU cores.
• 8 GB RAM or greater.
• Use hard drives that are 7200 RPM or greater.
• Atleast 100 GB of available disk space (possibly more depending on requirements, but no less than 50% or more available disk space).
• High performance independent 10/100/1000 Network PCI/PCIe/SCSI Network Adapter.
• Must be running .Net Framework v4.7.1 or higher.

Network Considerations

• Configure machines and server to operate under only one protocol.
• Convert on a hard wired (not wireless or VPN) 10/100/1000 LAN segment (recommended but not required).
• Dedicate a Switched LAN segment to the machines and servers involved in the migration.
• Update Network card drivers to the current version.

Server & Workstation Considerations

• Close email clients (Outlook, oOtes, etc.) during processing
• Disable SPAM filter during migration.
• Disable directory sync (OneDrive, Google Drive, etc.) to ensure that sync services don’t interfere with Transend Migration Console files.
• Disable screen savers and especially Open-GL screen savers.
• Disable or close unnecessary programs which could impede performance during the migration.
• Ensure that the latest service packs for the operating system are current.
• Update the email application software to the version recommended by the manufacturer.
• Minimize network latency: migrate local files where possible, locate migration nodes in the same network segment as mail servers, access over WAN only when absolutely necessary.
• Defrag the hard drive before migration to increase file/seek access time if the hard drive is fragmented.
• Set Windows to optimize memory for “best performance” under Windows Advanced Settings.
• Change the temp directory to a separate partition other the partition where the swap file resides. Use the /D < directory > switch option to change the temp directory location. See help file for more information.
• If running software to remove Temp files and/or Windows Registry entries from a computer (i.e. CCleaner or similar), we recommend restarting all machines running Transend products (including machines with Remote Agents) after usage of system cleaning tools.