I need some help from one of you ADSM/NT double gurus out there.

One of my clients has ADSMV2 on an NT server and all the workstation clients
run ADSM from the server.  She has the subdirectory ADSMV2 defined as a share
(forgive me if my terminology is wrong) so that the path in the properties
portion of the desktop shortcut pointing to the ADSM executable reads:

X:\baclient\dsm.exe -optfile=myoptfile.opt

She is in the processing now of upgrading to the version 3 workstation
client.  She created a new subdirectory called ADSMV3 and created a share for
that subdirectory.  She also moved all the options files into another folder.

She disconnects the old mapped X: drive (and the ADSMV2 share) and remaps to
the X: drive and the ADSMV3 share.

She Reboots the workstation.

She updates the properties path to point to the new location for the options
files.  Executes the shortcut and gets an error.   When she checks the
properties for the shortcut they have "reverted" to the old path.  She
changes them again and then everything works just fine.

Mind you I haven't seen this happen and she may be leaving something out in
her explanation to me (or in my NT ignorance I may be misrepresenting
something here), but she's a pretty thorough, conscientious administrator.
Anybody have any ideas what might be going on here?