We initiated the 10 Workstations Migrations by using the RUM Console.
Out of 10, 9 Workstation got Migrated to Target Domain successfully, but one workstation not Migrated. getting Error message Error 0x6d1. The procedure number is out of range. in the MOVE Process Failed
Checked the Particular Workstation is reachable and also Remote Registry is running state. Please help me how to Migrated this workstation.
Also observed the Workstation Object Name is in Source Domain, not an Target Domain.
What is the operating system version of the workstation that failed this way?
Did you have the workstation side agent perform the move or the RUM service on the RUM console machine?
The Operating system is Windows 10 Enterprise and the built Version is 10.0 (19044)
Yes, from the Workstation side the RUM agent QsRUMAgent services is running status only.
Have you tried removing and re-installing the agent?
That's a very low level error that seems to indicate some kind of unhandled exception in the code of the agent.
Thanks for helping, I cleanup the RUM agent and reinitiate the from scratch , now the workstation is Migrated. Thanks once again for helping
Hi JohnnyQuest,
For today I got the same error for one of the workstation, and multiple of times clean-up and reinitiate the Migration still getting the same error message
Has anyone found a fix for this? I have been seeing this off and on during a PC domain migration. Clean up did not help.
Hi Johnny,
we noticed some of the Workstation which is built version 19042 are getting same error message during the Workstation Migration.
If you haven't done so already, I would suggest you open a Support ticket on this.
Not sure exactly this is correct way, but I retried the Migration without selecting this option in advance (Perform the task remotely (without agents). finally its worked
Oh...
It's generally much more efficient (and potentially reliable) to de-select that option (I've never understood why it's on by default). That way the agent on the workstation is responsible for performing the action. Otherwise, it is the Resource Updating Manager (RUM) controller service on the console that does the work over the network wire.
Oh...
It's generally much more efficient (and potentially reliable) to de-select that option (I've never understood why it's on by default). That way the agent on the workstation is responsible for performing the action. Otherwise, it is the Resource Updating Manager (RUM) controller service on the console that does the work over the network wire.
