Migrating (moving) computers without having trust in place with Migration Manager RUM utility (4327859)

When using QMM RUM 8.* (valid for all versions of Migration Manager 8.5 onwards) and migrating a computer without having trust in place the migration fails. At the same time computer discovery and resource processing works as expected. RUMAgent.log reports:

------------------------

1/11/2017 8:07:14 PM 1524 UTC -8:00, Pacific Standard Time

1/11/2017 8:07:14 PM 1524 COMPUTERNAME, Windows Server 2008 R2 Standard Edition x64, build 7601, Service Pack 1

1/11/2017 8:07:14 PM 1524 ================================================================================

1/11/2017 8:07:14 PM 1836 RUM agent service started (file: QsResourceUpdatingAgent.exe, version: 8.13.1.8)

1/11/2017 8:07:14 PM 1652 Agent name: COMPUTERNAME.

1/11/2017 8:07:14 PM 1652 Reading agent configuration from: C:\WINDOWS\Quest Resource Updating Agent\config.ini.

1/11/2017 8:07:14 PM 1652 Using controller on host: QMMCONSOLE.

1/11/2017 8:07:14 PM 1564 Start calling controller.

1/11/2017 8:07:14 PM 1564 Checking pending task from controller.

1/11/2017 8:07:14 PM 1564 Initializing connection to controller at \\QMMCONSOLE .

1/11/2017 8:07:14 PM 1564 Closing connection to controller.

1/11/2017 8:07:14 PM 1564 Error 0x5. Access is denied.

1/11/2017 8:07:14 PM 1564 Controller call failed.

--------------------------------

Why does this happen?

MigrationManager_8.13_SysReqAndAccessRights.pdf (https://support.quest.com/technical-documents/preparing-migration/8.13/system-requirements-and-access-rights/19#TOPIC-529324)   contains the following information on Page 87

Resource Updating Manager Service Accounts

Local account

This account must be created only if computer running Migration Manager RUM Controller Service (in fact, computer running Migration Manager console) and computers running Migration Manager RUM Agent Service (workstations and servers to be processed) are located in different domains of different forests without trusts established between them.

Note that in this case you should specify account for Migration Manager RUM Agent service account explicitly.

The Local System account (default) cannot be used.

On computer running Migration Manager RUM Controller Service.

Create local account with the same name and password as Migration Manager RUM Agent service account has.

Must be a member of the local Administrators group on the computer running the Resource Updating Manager.

On console machine please create a local account and name it exactly as the service account with the same password.

This applies only to scenarios where migration of computers is performed by using RUM 8.5 (up)and where no trust is available between source and target domains.