This was my biggest con for Windows XP and it's still an issue in Windows 7.
It is a pain in my *** to modify the properties of a shortcut on the remote machine (via UNC). Windows looks at the local machine to verify the target instead of looking at the remote machine. This often results in a "Invalid Target" error. To remedy, I have to create the target folder and a dummy file on the local machine - or - use a UNC path for the shortcuts target.
I don't understand why Windows was not programmed to look at the SOURCE when pertaining properties are modified. Has anyone else had to deal with this nuisense? Any way around it?
It is a pain in my *** to modify the properties of a shortcut on the remote machine (via UNC). Windows looks at the local machine to verify the target instead of looking at the remote machine. This often results in a "Invalid Target" error. To remedy, I have to create the target folder and a dummy file on the local machine - or - use a UNC path for the shortcuts target.
I don't understand why Windows was not programmed to look at the SOURCE when pertaining properties are modified. Has anyone else had to deal with this nuisense? Any way around it?
