When specifying a Custom Map in Resource Updating Manager console "Actions\Specify Custom Map" and then next creating a Standalone task as described here: Solution SOL15336 - How to install a second instance of Resource Updating Manager (RUM) - https://support.quest.com/SUPPORT/index?page=solution&id=SOL15336 the old Custom Map is still used.
When creating standalone tasks, configuration files (vmover.in_ and vmover.ini) for the job are taken from the QMM console default folder for service information: C:\Program Files\Common Files\Aelita Shared\Migration Tools.
Click Start and let RUM (Resource Updating Manager) run the resource updating task on a single PC. This will force the creation of new vmover.in_ and vmover.ini files according to the Custom Map.
Generate new vmover.in_ and vmover.ini files via QMM console Tools - Export To - INI File ... and place them in the default location C:\Program Files\Common Files\Aelita Shared\Migration Tools on the console. Then create standalone resource updating task.
Generate new vmover.in_ and vmover.ini files via QMM console Tools - Export To - INI File ... and update these files on the remote resource updating console.
PLEASE NOTE: RUM will use a compressed version .in_ first if both .in_ and .ini files exist in the same folder. Therefore ensure if a new Vmover.ini file is generated and placed under "C:\Program Files\Common Files\Aelita Shared\Migration Tools" that the old Vmover.in_ is renamed or backed up to another location. It is always recommended to generate Vmover.in_ and Vmover.ini files in pair or just Vmover.in_ alone to ensure old .in_ file was not taken during the task creation.
Enhancement Request CR0193202 has been submitted to Development for consideration in a future release of Migration Manager for AD. This would make the Custom Map option effective for newly generated standalone resource updating tasks.