You can find this information in the Security section of the Event Viewer IF you have auditing set to log successful logins. With such auditing turned on, local machines will log successful logins to that box only, while domain controllers will log successful logins to the domain regardless of which computer the user logged into.
You can set auditing options via Local Security Policy or Group Policy of the domain.
- Zoe, that's ZOH-EEE, get it right please
- Just a little ol' MCP at Solien Technology
-
Thanks alot. i found what you told me about and I just have one other question. Does the service start to run when I reboot the server or do i have enable auditing for it to automatically startup when i selected to audit something?
I'm not sure if I understand the question, so forgive me if my answer isn't what you were looking for.
Since auditing is set up in the policy, it will take effect once the policy is propogated. A reboot should make a computer get the most recent security/group policy, but it isn't necessary. You can make a computer update its policy by going to the command prompt and typing...
secedit /refreshpolicy machine_policy
From that point on all the items you told the policy to audit will be audited, even after subsequent reboots. It's ok if you don't refresh the machine's policy right away. It will automatically update its policy according to the set interval. I believe the default is 20 minutes.
- Zoe, that's ZOH-EEE, get it right please
- Just a little ol' MCP at Solien Technology
-
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.