code:

---

 net use * /delete 

---

code:

---

 
net use T: /delete
net use T: \\smbserver\share1
net use U: /delete
net use U: \\smbserver\share2
 

---

and so on.. This avoids removing other shares that users have defined. Of course, option 1 is best when you want users to use ONLY the shares set up by the admin (you) in a login script. They will get tired of re-connecting their own shares after you delete them at every login!

Kix is wonderful when it comes to special mappings, like connecting to a share only when a user is a member of a particular group. Make the quick fix to your batch file and keep the users quiet while you experiment with Kix scripts.. When I was learning kix, I defined MY profile's login script to run Kix and everyone else's to run a simple BAT.

To underscore the power of Kix, consider that I've developed a login script that hasn't had a code modification since August 1999 - and yet it's been installed at over 40 customers with multiple sites. It uses an INI file to define drive and printer mappings, along with a few other settings. Even supports detection of applications and installs them on first Admin run if they aren't present. BUT - my first script started out as a replacement for one much like your batch file.

BTW - I still use this original script at home to control what my kids have access to on the LAN.

Glenn

code:

---

use 'k:' '\\smbserver\docs'
use 'l:' '\\smbserver\libs'
use 'p:' '\\smbserver\proj'
use 's:' '\\smbserver\ais'
use 't:' '\\smbserver\transfer'
settime '\\smbserver'

---