[Samba] somewhat OT--windows logon script

[Aaron Kincer]

Not using persistent shares is not a particularly good idea. If our 
domain controllers are down or for some unknown reason do not respond to 
a login request, those folks will not have their network drives. But 
with cached login information (and persistent shares), they can still 
open their network drives as if nothing is wrong. Of course, if a Samba 
machine is unable to authenticate, that's a whole different issue.

Edmundo Valle Neto wrote:
> Another way to do:
>
> I verify if the workstation is a Windows XP and if it is I do:
> net use /persistent:no > nul
> before the mappings.
>
> Then the mappings are not made persistent.
> PS: If I remeber right, one time made persistent you must delete them 
> all before try to map them with no persistence.
>
>
> Edmundo Valle Neto
>
>
>
> Aaron Kincer escreveu:
>> Rory,
>>
>> I can't speak for anyone else, but in my logon scripts, I delete shares
>> before mapping them because Windows exhibits very strange behavior 
>> sometimes
>> with shares. Anyone who has ever gotten the amusing error "connection 
>> cannot
>> be restored" or whatever it says knows what I mean. Deleting and 
>> recreating
>> shares every login guarantees that the shares are good at that moment.
>>
>> The downsides are that the time to execute the login script goes up. 
>> Well,
>> rather it stays approximately the same speed each time. Also, users
>> sometimes try to open networked files before the drive using that 
>> file is
>> deleted and restored or even worse, they open the file using the 
>> previous
>> day's share information and the share is deleted while they have the 
>> file
>> open. I urge anyone using this method to put the most commonly used 
>> drives
>> in the script first to avoid this problem.
>>
>> Aaron
>>
>> On 10/10/06, Rory Vieira <rory.vieira at gmail.com> wrote:
>>>
>>> Steve,
>>> I agree with Aaron on this...
>>> Unmap anything that *might* be mapped and then map your drives...
>>> I do the same using kix...
>>> And why do you need to 'remove' them in the first place?
>>> It's not like you are connectiong them persistently, after which a
>>> logon script seems pretty useless if all it does is mount shares...
>>>
>>> PS Here's the kix equivalent of what Aaron meant:
>>> ...
>>> function map_share( $What, $Where )
>>>         use $What /del
>>>         use $What $Where
>>> endfunction
>>>
>>> map_share("W:", @LSERVER+"\contract_maintenance")
>>> map_share("T:", @LSERVER+"\fleet")
>>> map_share("U:", @LSERVER+"\field")
>>> ...
>>>
>>> Just two side notes:
>>> You realy need a letter as low as E: ?!?
>>> And if your using [homes] than U: seems obvious for a 'user' share ;)
>>>
>>> > (why not use active directory to configure NTP?)
>>> > REM net time \\server5 /set
>>> Or assign both NTP/Time servers using DHCP ;) (Works for XP hehe)
>>> And you can do this in kix too using: settime "*"
>>> This will scan my domain in search of a time server...
>>>
>>> > (you do realize you have "t" declared twice, right?)
>>> hehe
>>>
>>> -- 
>>> Rory Vieira
>>> rory dot vieira at gmail dot com
>>>
>