How to prevent user password being reset to the same password?

Question

Hi,
As you all know, domain admin has the power to reset user password.  Let's think of the following scenario:
if an admin lets a user reset his password to use the same string, this action means he could nullify company policy on password which requires user's last N passwords being recorded in the history.
We could very well imagine that the admin reset his own personal password in order to bypass company policy.
I have asked partner forum to see if there's a way to prevent such thing, but the reply I got is "No".
I wanted to know if anyone of you have any idea to prevent such thing from happening?
Or if it's possible to get the hash value of users past N password to see if he's always using the same password?
Thanks in advance for your ideas.

Answer 1

Good rules is better alternative to complex policy.
Combine password history with time interval between changes.
Regards
Milos
You don't understand what I mean.
He knows exactly what you mean. 
check out this link below:
http://technet.microsoft.com/en-us/library/cc757692%28v=ws.10%29.aspx
Enforce password history
The Enforce password history policy setting determines the number of unique new passwords that must be associated with  a
user account before an old password can be reused .
The possible values for this Group Policy setting are:
A user-defined number from 0 through 24.
Not defined.
Discussion
Password reuse is an important concern in any organization. Many users want to reuse the same password for their account over a long period of time. The longer the same password is used for
a particular account, the greater the chance that an attacker will be able to determine the password through brute force attacks. If users are required to change their password, but nothing prevents them from using the old password or continually reusing a
small number of passwords, the effectiveness of a good password policy is greatly reduced.
Specifying a low number for Enforce password history allows users to continually use the same small number of passwords repeatedly. If you do not also set Minimum
password age, users can change their password as many times in a row as necessary in order to reuse their original password.
If you set Enforce password history to a number greater than zero, users must come up with a new password every time they are required to change their old one. This
improves security, but it can increase the risk that users will write down their passwords so they do not forget them.
If you set the value to the maximum of 24, it helps to ensure that vulnerabilities caused by password reuse are kept to a minimum.
For this policy setting to be effective in your organization, configure Minimum password age so that you do not allow passwords to be changed immediately. Enforce
password history should be set at the level that combines a reasonable maximum password age with a reasonable password change interval requirement for users.
Location
GPO_name\Computer Configuration\Windows Settings\Security Settings\Account Policies\Password Policy\
Every second counts..make use of it. Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
IT Stuff Quick Bytes