Sometimes after upgrading, the attached migration workers stop picking up jobs and no longer migrate.
This guide will help to get them migrating again.
First check the monitor page on the Migration Control Center (MCC):
Make sure the workers show up on the list and appear to be online.
Reboot the workers and the MCC.
End the Migration Worker Application on each worker machine, then bring up the Windows task manager to make sure there are no CMT* processes running.
An example of this is cmtproxy.exe. If there are any, end them. Clear the %TEMP% folder in Windows, this is usually under the user profile folder. Clear the C:\Windows\temp folder as well.
This folder is used for temporary migration files as well as various XMLs used for settings and address translation.
CMT will build these files again when the worker application is started or when it starts the next migration job. Start the worker again, then check the C:\Windows\temp folder to see if the NameTranslation.xml file has been or is still being created.
Check the C:\Program Files\CMT Universal (for 3.8 and higher = C:\Program Files (x86)\Binary Tree\CMT for Exchange\Worker) folder on the worker machines and verify the file versions of the .exe and .dll files.
They should be the same as the upgraded installation of CMT Universal on the Control Center machine.
If the workers are still online, the next step is to re-register the CMTe worker.
To do this, first end the the worker application and all CMTe processes on each worker machine
For 3.8 and newer versions
Uninstall the worker application
Then open SQL server, and confirm the MigrationQueueTable is empty
If there are any other entries in either of these tables, delete them now.
For 3.7 and earlier versions
Run the Launch FHConfigWiz.exe icon from the CMT for Exchange | Migration Worker Installation folder under your Windows Start Menu:
Click the Un-register button:
Just to make sure, open the C:\Program Files\CMT Universal\CMT_XMLServer\App_Data\CMT_Universal.mdb file and check both the FarmHands table and the MigrationQueueTable table. You must end the CMT worker application before doing this. The FarmHands table should list only the Control Center after removing the workers.
Now you can re-register the workers, You won't need to reinstall the worker application, just run the FHConfigWiz.exe again:
Enter the Control Center IP address or DNS name and test the connection, then click next and continue to follow the prompts to register the worker:
Once you click Finish, launch the migration worker application on the worker again, then check the file versions and C:\Windows\temp folder for the NameTranslation.xml file (If you are using classic translation).
Check the monitor page to make sure all workers are showing up again.
Finally, start a migration and see if the workers start picking up migration jobs again.