We have a cmd file located in a network share and a shortcut of it in the desktop. When it's created it works as expected, but once in a while the program doesn't work and when we check, the path where the shortcut is pointing has changed with the domain name instead of the letter of the mapped drive. We didn't move/rename the file or something like that.
Does someone know what could cause this strange behaviour ?
I initially thought that it could be the mapping delay of the network share, so it wouldn't be mapped yet when they execute it fast and it would take the hostname instead of the letter...
Thanks in advance.
