B
BryanB
Windows 2000 server sp4. User accounts contains batch
script to mapped network drives to local workstation.
When we change a batch script on the server to let's say a
new share but with the same drive letter assignment when
the user logs into the workstation it still remembers the
old share for the drive letter assignment. The only way I
can get around it is if the user logs on then I go into
command prompt and delete the old share using net use
O: /del then have the user log off and log back on now we
can see the new share being executed by the batch script.
It seems as if the local workstation will not let go of
the old drive letter assignment. Workstations in question
are Windows 2000 and windows XP pro. I don't have this
problem in windows 98SE. Any ideas on how I can get this
to stop so I don't have workstations looking for old
shares at starup and just use the new ones defined in the
batch script without having to go to each workstation and
log each user on to delete it? Please someone help stop
the insanity!
script to mapped network drives to local workstation.
When we change a batch script on the server to let's say a
new share but with the same drive letter assignment when
the user logs into the workstation it still remembers the
old share for the drive letter assignment. The only way I
can get around it is if the user logs on then I go into
command prompt and delete the old share using net use
O: /del then have the user log off and log back on now we
can see the new share being executed by the batch script.
It seems as if the local workstation will not let go of
the old drive letter assignment. Workstations in question
are Windows 2000 and windows XP pro. I don't have this
problem in windows 98SE. Any ideas on how I can get this
to stop so I don't have workstations looking for old
shares at starup and just use the new ones defined in the
batch script without having to go to each workstation and
log each user on to delete it? Please someone help stop
the insanity!