I'd think klist would be more like if that was the chosen route as it's CLI
________________________________ From: Devin Meade [mailto:[email protected]] Sent: Thursday, February 05, 2009 10:26 AM To: NT System Admin Issues Subject: Re: Scripting: How to tell if login was cached or domain? kerbtray - I don't know if it can be scripted. hth Devin On Thu, Feb 5, 2009 at 11:04 AM, Stephen Wimberly <[email protected]> wrote: I have a script that I want to run, but only when the user login was cached. Is there a way to tell whether the current user login was cached or verified by a domain controller? I _thought_ I'd use the %logonserver% variable, but apparently it shows the domain controller that last authenticated the user even when the current login was cached. Most scripts I've seen ping a server that is only available on the LAN and look for the reply. In this case though I don't care if they are on LAN or not, I care if they are cached or not. I found a script that looks through the event log for "Last cache login" and displays the date/time, but it doesn't effectively tell me what my current login is. Anyone know a way to tell? I know the XP firewall has settings for a domain profile, is it using a domain profile for all cached logins? Thanks In Advance for pointers! ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ -- Devin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
