I am using Microsoft Remote Desktop 10 via macOS and I was having a problem in this thread (hdiutil Microsoft Remote Desktop 10 issue) which got me no where as the report issue feature no longer works (the website that is redirected is not activated anymore, offline).
I was googling and github searching my issue and I came across:
which states that:
Tests shown that it is possible that tsclient file redirection may
not work at the early logon phases. In that case, error box “Network
path not found” will be shown. To resolve this issue, use following
autostart program setting in .rdp config file: alternate
shell:s:cmd /c ping 127.0.0.1 -n 3 && “tsclientC folder
spacefile.exe” NB: it is not a good idea to append logoff command,
because our exe will be terminated too soon. Instead, mstsc process
termination will leave session running on target server, leaving us
some time to perform
Now, what I find interesting and my question is, is it possible to run a CMD command that runs indefinitely until RDP session is closed, and to always try to connect to the tsclient, even if on the macOS it is disconnected and reconnected.
In Microsoft Remote Desktop 8, if you disconnect and reconnect the disk image in macOS, you can still connect to it on the RDP session; however, in Microsoft Remote Desktop 10, if you disconnect and reconnect, in the RDP windows session, you can no longer connect as it says “Network address invalid”.
So I was wondering if anyone knows anything about this. I feel as if running a CMD command indefinitely through the rdp config file on initial connection may solve this issue.
Please give me any research, knowledge, or further questions as I am desperate to solve this.
Thanks.
