Documentation and articles that we have followed till now (e.g.https://support.quest.com/technical-documents/migration-manager-for-ad/8.10/installation-guide/3#TOPIC-80597) suggest that in case where DNS resolution is not an option, WINS should be preferred with a "final" fallback solution the use of host files.
In the case of RUM we encountered the following problem: While the source workstation was found using DNS (because source domain has Microsoft DNS) and the deployment of the agent worked as expected, the "discovery" task ended with a warning. The reason was that there is no WINS server in the source domain and target works only with WINS , subsequently the agent on the source workstation, once installed could not "find" the computer in the target domain that had RUM installed. The result we got in the log file was:
Warning: Configuration path \\TVDMNG02\QuestResourceUpdatingConfigs$\ is not accessible. Error 0x00000035. The network path was not found. .
Warning: The Dell Migration Manager RUM Controller Service is not accessible. Error 0x000006BA. The RPC server is unavailable. .
...where TVDMNG02 is the server where the RUM is installed. Further troubleshooting indicated that the problem was "backwards" resolution, that is, the agent on the workstation was not able to locate the RUM. We temporarily resolved the problem by adding an entry with the NETBIOS and the IP address of the RUM in the workstation host file, however the client is reluctant to deploy such a host file entry for 5000+ workstations.
We wonder if there is a way (registry entry perhaps on RUM) to pass the IP address of RUM to the agent during the discovery task. Any other alternatives will be appreciated.
Thank you in advance
