asked on

Edit Shortcut Porperties on Remote Machine

Hi.

Some shotcuts on remote machines are in the form "\\thiscomputername\c$\program files\myapp\myapp.exe". This was done some time ago as a quick and easy way to edit or create shortcuts on remote machines by mapping to the machine (rather than having to Remote Desktop) and, for the path, using the form \\theremotecomputername\c$\ rather than c:\ which would refer to the c: drive back here on my machine.

Following a tightening of security and permissions on the network these remote machines are now asking for a username and password to run the shortcut. I don't want to look at permissions at this stage, I just want to change \\theremotecomputername\c$\ back to c:\ without having to Remote Desktop and without the shortcut on the remote machine thinking that the program is here on my c: drive!

Hope this makes sense!

TIA.

SOLUTION

Henrik Johansson

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Sat2b

ASKER

Thanks henjoh.

I think we're in this position because we tried that. On the local machine we tried creating a shortcut to, say, c:\program fles\myapp\myapp.exe mirroring what we wanted on the remote machine. We then copied this shortcut to the remote machine but the shortcut thought the app was back on the local machine and tried to run it across the network. To solve this we created a shortcut locally \\theremotemachine\c$\program files\myapp\myapp.exe and copied that over, the remote user had admin rights on their own machine so it worked OK.

If the shortcut wasn't a shortcut but a batch file we'd just edit \\theremotemachine\c$\ to c:\, what we're trying to do is the same but for a shortcut. Shortcuts seem to be too clever, i.e. when I make a mapping to the the remote machine to edit the shortcut and change \\theremotemachine\c$\ to c: it assumes that the app is on the c: drive on my machine.

This is potentially a problemn on hundreds of shortcuts so all we wanted to do when it was reported was a quick map-edit-save. We don't want to change shares or permissions, that would be overkill. It looks like Remote Desktop-edit-save may be what we have to do.

Thanks again.