Discussion Locked
0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have serveral people that all their available drives map to one drive. They may have a: c: d: o: x: and y: mapped at login and then some time during the day any spare drives are mapped to, for instance, the x: drive. Something causes any drive that is available between a: and z: to take the x: drive mapping. This may occur at different times of the day. I have not seen this at login. The users have NT4 sp6, Office 97 and Windows NT login scripts map network drives. One user had it happen when he would go into an Excel 97 document. Any suggestions?
5 replies
by joseph moore
Honestly, this has been seen for years. Drives that you use commonly will map to unused drive letters, so you start getting duplication.
I have never looked up on how to permantely fix this. It was never worth the trouble.
Just have your users log out at the end of the day. When they come in the next day and log back in, that will clean up the extra drive letters.
To really help out, if you use logon scripts, just put this line at the beginning of all of your scripts:
NET USE * /D /Y
Thatwill unmap any mapped drives. When you run that before you map drives, it cleans out the mappings.
hope this helps
The question was auto-closed by TechRepublic
by shelli_2003
Taking "findfast" out of your startup fixed that for me.
The question was auto-closed by TechRepublic
This question was auto closed due to inactivity
This discussion is closed to new replies.
Trending Desktop posts
Sort by Trending
Discussion
How to make light speed agent go away
0 helpful
4 replies
Question
Floppy drive wont work on my 486
0 helpful
1 reply
0 helpful
1 reply
Discussion Locked
Ryzen 7 7700
0 helpful
2 replies
Question Locked
Issue fully resetting my PC
0 helpful
4 replies