Skip to main content

Password cannot be changed because it was changed in the last 10 days.

When you try to change your network user password, you receive this error "password cannot be changed because it was changed in the last 10 days." This is a Password Policy setup in your Windows Active Directory security policy.

Here's where you can check your Password Policy. Please note, you need Active Directory administrator rights to manage your AD Server.
  • Login to your Active Directory (AD) server using Administrator or equivalent rights.
  • Click on Start, All Programs, Administrative Tools, then Domain Security Policy.
  • In Default Domain Security Settings, click on + sign in Account Policies. This will show you the Password Policy, Account Lockout Policy and Kerberos Policy.
  • Click on Password Policy, you will see in the right box the following policies e.g. Enforce password history, Maximum password age, Minimum password age, Minimum password length, etc.
  • Double click on Minimum password age to see the properties.
  • In Security Policy Setting tab, this is where you can manage the number of days you want your password can be changed after.
  • Let's try, 3 day
  • Click on Apply to execute.
With this example, you just change your password age to 3 days. Meaning, when you change your password on September 11 you can only change it after 3 days on Sept 14. This is required to enforce password history policy.

Here's a good reference to read: http://technet.microsoft.com

Popular posts from this blog

Alternative Social Networks

If you are planning to create your social network e.g. similar to Facebook. Here's a short list of alternative software's:

Open Source and Free​
http://buddypress.org/ - Wordpress (Open Source and Free)http://elgg.org/ - (Open Source and Free)Commercial Social Networks software
http://www.socialengine.com/ ($299 Stand Alone, $29/mo Cloud)http://www.jomsocial.com/ (run with Joomla, need to know CMS)http://www.boonex.com/ (very expensive, $399 for Standard)http://www.anahitapolis.com/http://www.oxwall.org/http://sharetronix.com/http://www.moosocial.com/http://www.jcow.net/http://phpdolphin.comhttp://www.grou.ps (from free to Commercial, I left my networks and they are selling it http://www.phpfox.com/ (I used this before, it's hard to maintain. I moved to NING but left too after it was sold to another company)http://www.ning.com (I don't recommend using this service, it's hard to export your data when it's time to move)Something to check when selecting your next soc…

Example of Out of Office Reply for Terminated Employee

This is a sample message that I used for terminated employees, unless HR staff specified a different message.
=== Example for KING.NET Employee === John Doe (employee or consultant) is no longer with KING.NET effective June 1, 2008 (termination date). For matters relating to "Project Name here" please direct your concerns to John Smith at johnsmith@king.net (Manager or Supervisor). For all other matters, please direct your email to Mary Smith HR at marysmith@king.net.
Please call our main office 703-345-6789 if you have other concerns.
Thank you.
=== end of message ===

Frequent Account Lockout in Active Directory

I have a user in Windows Pro 7, and Windows Server 2003 environment that is frequently account locked out. I tried many different scenarios to resolve this account lockout issue, from resetting his password, changing a new password, remove and re-join the domain, rebooting the workstation and active directory servers.

I tried to use the command prompt utility to run "rundll32.exe keymgrdll, KRShowKeyMgr" (case sensitive) to delete the account in Windows 7 password cache, and still no luck.

Still searching for answer ... Let me know if you encounter a similar issue in Windows Pro 7 and Windows Server 2003.

Continue reading updated post here:
http://www.whaddya.com/2011/09/windows-needs-your-credentials.html