Avatar of phil435
Flag for United States of America asked on

Exchange 2007 and AD password

Hello All. I have noticed that when I change my password in windows that exchange 2007 will still let me log-on with both the old password and the new password. However I cannot use the old password to login to windows, only the new password. Is there something in exchange that remembers the last password and still considers it valid? I am running a 2003 environment in 2003 mode and have two DC's that I forced replication on to make sure that wasnt the issue.
ExchangeActive DirectoryWindows Server 2003

Avatar of undefined
Last Comment

8/22/2022 - Mon
Kent Dyer

You may need to run from a command-line the following:


Otherwise, you may need to look at the replication partners to be sure that something is not broken.



Ok correct me if I am wrong here but the new password is recognized on the exchange server through OWA along with the old password. Does this not prove that replication did occur? Also the dc recognizes the old password is no longer valid since it will not allow me to logon to windows with the old password.
Neil Russell


GPUPDATE /force  has absolutely nothing at all to do with passwords. Please do not offer advice on subjects you do not understand.
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question

Have not received another solution form expert. Did not award myself points but did find the article that addressed this from Microsoft KB.