This is a cracker - shortcut to share

[mizzy]

I've never seen this before...but I suppose in a way it could have its uses.

I copied (robocopy) an 800Gb folder (in a shared folder) to a new server. The users were happily able to access the data on the new server (via a mapped drive).

The original folder was then MOVED to a new location (I can never trust robocopy totally so I always keep the source for a few days)...I did share it just in case the local admin guys needed access to it (hidden share read only access).

Anyway...SOME of the users had a shortcut to the original folder on their desktop...guess what...they double click on it and volia..it finds its way to the OLD folder (I move it and created a hidden share)...hows about that!

Can somone explain to me how this happened?
many thanks.

 

[xmsre]

explorer first attempts to resolve the UNC path of the shortcut. If that does not resolve, explorer then tries the "relative path" or local path to the file. If that resolves, the unc path is updated.


All the way back to NT 4, you could control the resolution behavior through policies; LinkResolveIgnoreLinkInfo would ignor the UNC path and force the local path to resolve for instance.

The link updates becase the drive is mapped and the local path resolves. If you did not have the mapped drive, the local path would not resolve and the UNC link would not update.

 

[mizzy]

Many thanks for your quick responce.

Next time now more Mr Nice guy...I'll make the original source totally unaccessable.