Adoption not working with 'The system cannot find the file specified' error is the beacon and target adoption machine are on different domain
Adoption may fail with error 'The system cannot find the file specified' in the log.
The cause of this issue may be due to the reason beacon adopt agents is through installing a temp service (using system account) on the target device first. If the beacon and the target devices are in different domains, the system account running the service may not have permission to access the beacon file share even these two domains are trusted.
The standard/suggested process is to install a beacon on the same domain as the target machines to be adopted.
Finished processing task of type 'TaskType_Adoption' on target 'xxx.xxx.xxx.xxx' with result '-1'
<Parameter Index="0">\\<beaconServerName>\mgsRET$\mgsreservice.exe</Parameter> <LastError Result="2">The system cannot find the file specified.