T –
Using “Remote Command 1” to import a .reg file will *not* work if the .reg file is located on a network drive. However, if the .reg file were placed on the target computer and then executed with a local path, it *would* work. The reason for this is because when BatchPatch is remotely executing a process/command on the target system, the remote process does not have access to any network drives and can only access the local system. The exit code 0, in this instance, is misleading. The regedit.exe process is successfully terminating, which is why it returns 0, but it’s not actually importing the .reg file.
Using the “Deployment” action is the correct way to accomplish what you are trying to accomplish because it first copies the .reg file to the target computer before executing it with a local path as described above. I am not able to reproduce your issue of it hanging at “Queued…” nor am I sure why it might be happening.
What version of BatchPatch are you running?
What happens if you move the EIOBoardOutlook64.reg file to the machine that the BatchPatch console is running on instead of having it on a network drive?
Also, what registry hive is the .reg file targeting? HKEY_LOCAL_MACHINE?
Thanks,
Doug