Actually <Computer Configuration>Windows Settings>Security Settings>Local
Policies>Security Options, look at the "Interactive Logon:> specifies the
number of accounts to be cached locally on the computer (1 can be enough if
only one user is using the laptop - this way windows will remember only the
last user that logged on). If they want to logon faster tell them to remove
the network cable, log on, and then plug the cable back again.
--
Regards,
Andrei Ungureanu
www.eventid.net
Test our new EventReader!
http://www.altairtech.ca/eventreader...lt2.asp?ref=au
"rovert506" <(E-Mail Removed)> wrote in message
news:FB013DBE-77C3-4BE4-90D7-(E-Mail Removed)...
> The number of cached credentials can be controlled via group policy.
> Under
> Computer Configuration>Windows Settings>Security Settings>Local
> Policies>Security Options, look at the "Interactive Logon: Number of
> previous logons to cache" setting. If your current GPO sets it as 0, then
> the user will ALWAYS contact the DC to authenticate. Set the number to
> anything you desire (such as 3 or 5 or 10) and users will be able to
> authenticate themselves into the domain while not being directly connected
> (thus the whole cached concept).
>
> Hope this helps!
>
> -TM
>
> "OM" wrote:
>
>> Hi
>>
>> I would like to know if Windows has any build-in feature that allow you
>> to force user logon using cashe credential instead of checking the
>> availability of domain controller in the network first. Our laptop users
>> experience a very long delay when they logon to their laptop at home or
>> locations other than the corporate network. We do not want them to logon
>> locally when they are out of office as they will be using multiple
>> profiles in they laptops.
>>
>> Any suggestion would be appreciated.
>>
>> Thanks
>>