M
MJ
Guest
Recently I have been SURPRISED that shortcuts to applications and files seem
to have become "dynamic" in the sense that if you rename the target file the
shortcut picks up the new name. In the past, shortcuts were static, and if
you changed the name of the target you needed to revist the short cuts.
The problem is that we are moving many of our files/applications from an
older server to a new server location and renaming the old files it show that
they have been copied to the new location. With static shortcut targets,
renaming the files "BROKE" the link and will cause the user to think, but
with the shortcuts picking up the name change the link is not broken and
risks are: (1) a user might be pointed at wrong location until the old server
is retired; (2) loss of crucial data; and (3) possible corruption of existing
data by going to the wrong place.
Is there a way to "break" the links with the old shortcuts until they have
been replaced with new ones?
Thanks for your insight.
--
MJ
to have become "dynamic" in the sense that if you rename the target file the
shortcut picks up the new name. In the past, shortcuts were static, and if
you changed the name of the target you needed to revist the short cuts.
The problem is that we are moving many of our files/applications from an
older server to a new server location and renaming the old files it show that
they have been copied to the new location. With static shortcut targets,
renaming the files "BROKE" the link and will cause the user to think, but
with the shortcuts picking up the name change the link is not broken and
risks are: (1) a user might be pointed at wrong location until the old server
is retired; (2) loss of crucial data; and (3) possible corruption of existing
data by going to the wrong place.
Is there a way to "break" the links with the old shortcuts until they have
been replaced with new ones?
Thanks for your insight.
--
MJ