Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Possible Duplicate:
What Win-2003 security policy expired all passwords, and how did it do it?

Most of our user passwords were reset at 4:30pm local time over the weekend (non working day). Not the administrator account, but it did include some security enabled user groups that aren't actually login accounts.

It's possible that this was a virus or a break-in, but I'm thinking more likely it was an unknown act of stupidity and ignorance.

What kind of policy or security setting would cause the passwords to all expire at the same time? The accounts that are login accounts are all set to never expire.

I am asking for SPECIFIC information about Group Policy or Active Directory Account Settings. If you do not think this was caused by Group Policy or AD Accont Settings, please say so. All of the Accounts that reset were in one OU.

Clarification/Correction: The passwords were not changed, they were only expired. (This has the effect that offsite users could not connect, but when users arrived on-site, they were able to connect using the expired password).

Further information: event log shows SceCli event 1704 at the critical moment: "Security policy in the Group policy objects has been applied successfully."

I'm painfully going through the group policy settings now. Specific suggestions would be welcome. I do not know how a Group policy could be applied without me knowing. Specific explanations would be welcome.

moved to new question: What Win-2003 security policy expired all passwords, and how did it do it?

PS: There is a comment here: let me know and I'll re-open this one. – voretaq7♦ yesterday

But no contact information.

PSS: There is a comment here: If this question and the other are identical please edit the other one as needed to incorporate all relevant information and delete this one. >But I started a new question because there are comments here telling me I should start a new question, because the new question is not identical. If you don't agree with them, tell us why they are wrong. I'm in the middle of a war about when new questions should be started???

share|improve this question
    
It seems like @MichaelHampton answered your initial question of why the passwords expired. You may want to open a new question to figure out if policies are being applied at incorrect times or without you knowing. This thread will get overly confusing for future visitors otherwise. –  Brent Pabst Jan 29 '13 at 3:48
    
I have to agree; it should be a separate question. –  Michael Hampton Jan 29 '13 at 3:59
    
    
If this question and the other are identical please edit the other one as needed to incorporate all relevant information and delete this one. If they are in fact distinct questions (about separate problems) let me know and I'll re-open this one. –  voretaq7 Jan 30 '13 at 8:31

1 Answer 1

up vote 5 down vote accepted

Look in your security event log on the domain controller for event ID 628. If passwords were reset by someone other than the user himself, this event should have been recorded for each user whose password was reset. The details should tell you who changed the password.

If passwords had simply expired, you would see event ID 535 logged when an affected user tries to log in.

Also look for other events around the time period that you believe this happened. You may find other events logged that will give you a clue as to what happened.

share|improve this answer
    
Yes, security log showed events. Thank you. See modified question for more details. –  user165568 Jan 29 '13 at 3:44

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.