Wednesday, January 30, 2013 3:12 AMHello All,
I'm experiencing some funny issues with my network and client PC.
Clients: 4 x Win XP SP3, 2 x Win 7
Currently there are 6 network drives mapped to each PC. This is done via a logon script. I don’t run a log off script but I do make sure that all network drives are removed before remapping in my script.
Two of the client PC have an issue with their drive maps, one is an XP and the other Win7 client. The issue occurs randomly during the day, all of a sudden the network drives have been mapped over and over again on one of these client machines. The only reason it seems to stop mapping is because it runs out of drive letters.
Another interesting point is that it’s not remapping all the 6 drives, occasionally it only maps 2 drives over and over again.
This started happen after I stopped using group policy to map drives and used the active script as I was having too many issues with GP.
All other PC’s are working perfectly, only these two experience this issue.
I don’t believe it’s the script as the script assigns a specific drive letter to every drive and if the drive letter is taken it ignores that line of code and doesn’t map that specific drive.
On another note, is there a way on the client machines to see a log of what is activating the maps?
Saturday, February 02, 2013 12:04 AMModerator
Assuming your script first deletes any existing mapping from the last time it was run, then remapps the drives. One thing you might try is a pause statement in the script after the intial logon to verify if it is that script. However, as a general rule you should be doing drive mapping with GPO in Server 2008 and newer, and it might be better if you explored the issues you were having with the gpo.
- Marked As Answer by Andy QiMicrosoft Contingent Staff, Moderator Monday, February 04, 2013 9:38 AM