You're right - it's simple to fix - delete the drive mappings and make them non-persistent
net use p: /home /persistent:no net use p: /delete net use /? If using Windows Scripting take a look at the properties of WScript.Network.RemoveNetworkDrive(). When the change is saved to the user's profile it is persistent. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Robert VadeBonCoeur Sent: Thursday, October 25, 2001 10:58 AM To: NT 2000 Discussions Subject: Drives mapped never want to leave! 2k clients. This is probably something simple, however I am unable to find any information on TechNet regarding this. On 2000 (client, server, ...) drives are mapped with the login script (which is standard method of getting drives to the computer of course). However, the drives seem to be cached so that they appear offline as well. This is fine. The problem occurs when we change the login script to go to a different mapping - the old drive still appears, never wanting to leave. What is the work around for this? Is it necessary to turn off this caching, or what options exist? Thanks for any help you can provide, Robert VadeBonCoeur LAN / WAN Administrator [EMAIL PROTECTED] ------ You are subscribed as [EMAIL PROTECTED] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED] ------ You are subscribed as [email protected] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED]
