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?
You need to be signed in and under a current maintenance contract to view premium knowledge articles.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center