|
|
|||||||
We used batch scripts to map drives in our win 2000 network. When I now use kix to map drives it doesn't remove my old connections. I then put in the net use f: /d in the batch script and it then worked out. I know that this shouldn't be any problem but it happend on about 50 computers so I wonder if someone know if its a bug or what it can be. I map the drives thru a script which uses ingroup. if ingroup... use f: /delete use f: \\server\drive |
||||||||
|
|
|||||||
More than likely, you need to add a /PERSISTENT switch in addition to the /DELETE to remove these mapped drives.. Kent |
||||||||
|
|
|||||||
Thx it works! When I look in cmd with net use command and I have connected to I: it says connected. When I then use USE I: /del and then type net use, it says I: not availble, and I cant see it under my computer. If I then try to use USE I: /Del /Persistent It dissapear totaly from net use view. Thats good. The strange is, even if I use USE I: \\server\share /Persistent:no USE I: /del It says not available when I type net use. Doesn't Persistent:no works with kix, I think I have read i should? |
||||||||
|
|
|||||||
The Persistent switch does not work the same with KiX USE as it does with NET USE. |
||||||||
|
|
|||||||
Yes, and no ... 'Persistent:no' would be the same as ommiting it completely in kix ... so only use /persistent if you want it persistent and omit if you want it non-persistent... What happened might be that it ignored the :no part and made it persistent |