Reset AD Users Password Expiration Date

1.In Active directory users and computers, make sure advanced features is enabled
2.Navigate to the user account, there should be an Attribute Editor tab
3.Scroll to the pwdLastSet field. Modify it by entering 0 (zero) in the value field. Click OK. This sets the value to (Never) as in the password has never been set. Click OK on the User Account Properties box.
4.Open the User’s Account Properties again. Go back to the Attribute Editor tab. Scroll to pwdLastSet and modify it with a value of -1. Click OK twice.
5.When you view the pwdLastSet value, it will now indicate today’s date.

Conclusion

While this is not the best solution because it extends the password expiration from today’s date based on our Domain Password Policy instead of just setting it to expire in a few days time. It is better then setting then leaving it set to Never Expire and end up forgetting to change it back. Have used this for remote workers who cannot connect to the vpn as their password has expired.

No Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Active Directory
Preseed Files for DFS Replication using Robocopy

Use Robocopy to Preseed Files for DFS Replication I’ll write this here first, since it’s important: The folder in which you are robo-copying (ex c:\test) must not exist on the destination server (ex. f:\test). If you create the folder manually on the destination server, the file-hashes will not match and DFSr will …

Active Directory
Reset Users Password Expiration Date

1.In Active directory users and computers, make sure advanced features is enabled 2.Navigate to the user account, there should be an Attribute Editor tab 3.Scroll to the pwdLastSet field. Modify it by entering 0 (zero) in the value field. Click OK. This sets the value to (Never) as in the …

Active Directory
How to remove a KMS Server from your infrastructure

We had some rogue KMS server hosts in our infrastructure. My guess is someone inadvertently installed the wrong key. We can easily look up KMS hosts as they are published to DNS. from a command prompt run: nslookup -q=srv _vlmcs._tcp.contoso.com Run this for all your subdomain’s fqdn to list all …