..I'd also then keep an eye on the account and if it's changed again check the security logs to see who manipulated that account. Check after you change their access rights so you can get the event ID to look for (it escapes me right now).
I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.
There are no more PDC's! There are DC's with FSMO roles!
That is the problem isn't I have no idea who created it. At that time the event logs were set to store only a small amount of data then rewrite, I have changed that and forced all to change passwords.
You should change the password on the rogue user to deny him access. If the rogue user is forced to change it him/herself then all that will show in the security log is that the rogue user changed their password not who the rogue use is.
Also, did you follow Davetoo's other suggestion and remove the rogue user from the admin group?
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.