A user on our domain had his network password saved in a service that constantly authenticates through the PDC.
The user changed his password.
His account was continually locked, no matter how many times unlocked, it would return to being locked.
This was resolved by removing his credentials from the service described in the beginning of this post.
TIP:
A network password should never be saved into a service that will not automatically update the password credentials upon changing through AD or the Windows password prompt/service.
Labels
DNS
(3)
Google Apps
(3)
Services
(3)
Spiceworks
(3)
Spiceworks Scans
(3)
Toshiba
(3)
Active Directory
(2)
Network Password
(2)
Network Scans
(2)
Password
(2)
Phone
(2)
SQL Database
(2)
email
(2)
gmail
(2)
proxmox
(2)
Account Locked
(1)
Fidlar
(1)
Fortis
(1)
Forward DNS Look Up
(1)
Forward Reverse Look Up
(1)
Google Apps Sync
(1)
IP Addresses
(1)
Internet Temporary Files
(1)
Laredo
(1)
Microsoft Word
(1)
Reverse DNS Look Up
(1)
Running Processes
(1)
Scheduled Tasks
(1)
Sonicwall
(1)
Sophos
(1)
Spiceworks Inventory
(1)
Temporary Document
(1)
UCCEzFileOnline
(1)
VPN
(1)
Web Hosting
(1)
Win server 2003
(1)
Windows 8
(1)
Windows Password
(1)
Windows Profile
(1)
Windows Server 2003
(1)
Windows7
(1)
black list
(1)
copy
(1)
crystal reports
(1)
database
(1)
datasource
(1)
dhcp
(1)
disc usage
(1)
drag and drop
(1)
google
(1)
google apps configuration
(1)
google apps organizations
(1)
google apps settings
(1)
google hangouts
(1)
install
(1)
mail
(1)
microsoft
(1)
move
(1)
network devices
(1)
openvz
(1)
printer reset
(1)
sage
(1)
spam
(1)
storage
(1)
ubuntu server 12.04
(1)
vi
(1)
windows 2008 server
(1)
windows 7
(1)
Thursday, November 7, 2013
Active Directory - Persistently Locking an Account
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment