Machine Account Password Process

Published Apr 04 2019 01:52 PM 5,478 Views
First published on TechNet on Feb 15, 2009

Hi, this is Manish Singh from the Directory Services team and I am going to talk about the machine account password process. Ever wondered what goes on with your machine account in Active Directory? Here is a brief set of question and answers to clear things up.


How often does the machine password account change in AD (is it different for various Windows operating systems)?


The machine account password change is initiated by the computer every 30 days by default . Since Windows 2000, all versions of Windows have the same value. This behaviour can be modified to a custom value using the following group policy setting in Active Directory.

Domain member: Maximum machine account password age
You can configure this security setting by opening the appropriate policy and expanding the console tree as such:

Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options


If a workstation does not change its password, will it not be allowed to log onto the network?


Machine account passwords as such do not expire in Active Directory. They are exempted from the domain's password policy. It is important to remember that machine account password changes are driven by the CLIENT (computer), and not the AD. As long as no one has disabled or deleted the computer account, nor tried to add a computer with the same name to the domain, (or some other destructive action), the computer will continue to work no matter how long it has been since its machine account password was initiated and changed.

So if a computer is turned off for three months nothing expires. When the computer starts up, it will notice that its password is older than 30 days and will initiate action to change it. The Netlogon service on the client computer is responsible for doing this. This is only applicable if the machine is turned off for such a long time.
Before we set the new password locally, we ensure we have a valid secure channel to the DC. If the client was never able to connect to the DC (where never is anything prior the time of the attempt – time to refresh the secure channel), then we will not change the password locally.

The relevant Netlogon parameters that come into play and we can think about changing here are:

ScavengeInterval (default 15 minutes),
MaximumPasswordAge (default 30 days)
DisablePasswordChange (default off).

DisablePasswordChange would prevent the client computer from changing its computer account password.

Key = HKLM\SYSTEM\CurrentControlSet\Services\NetLogon\Parameters
Value = DisablePasswordChange REG_DWORD
Default = 0

Group policy setting:
Computer Configuration\windows Settings\Security settings\Local Policies\Security Options
Domain member: Disable machine account Password changes

Warning: If you disable machine account password changes, there are security risks because the security channel is used for pass-through authentication. If someone discovers a password, he or she can potentially perform pass-through authentication to the domain controller. Here is the article that talks about disabling automatic machine account password change: KB 154501

ScavengeInterval controls how often the workstation scavenger thread runs - the workstation scavenger is responsible for changing the machine password if necessary:

Value: ScavengeInterval REG_DWORD 60 to 172800 Seconds (48 hours)
Default : 900 (15 minutes)

MaximumPasswordAge determines when the computer password needs to be changed.

Key = HKLM\SYSTEM\CurrentControlSet\Services\NetLogon\Parameters
Value = MaximumPasswordAge REG_DWORD
Default = 30
Range = 1 to 1,000,000 (in days)

Group policy setting:
Computer Configuration\windows Settings\Security settings\Local Policies\Security Options

Domain member: Maximum machine account Password age

To clear things up, it is 7 days on Windows NT by default, and 30 days on Windows 2000 and up. The trust password follows the same setting. So Trust between two NT 4 domains is 7 days. Trusts between Windows 2000 and up and anything else is 30 days. So what this means is if:

  • 2000 and NT4 trust password is 30 days
  • 2000 to 2000 is 30 days
  • 2000 to 2003 is 30 days
  • 2003 to 2003 is 30 days

After the Netlogon service starts, the Workstation service scavenger thread wakes up. If the password is not older than MaximumPasswordAge, the scavenger thread goes back to sleep and sets itself to wake up when the password will reach that age. Otherwise, the scavenger thread will attempt to change the password. If it cannot talk to a DC, it will go back to sleep and try again in ScavengeInterval minutes.

The ScavengeInterval setting can be modified to a custom value using the group policy setting in Active Directory.

Group policy setting:
Computer Configuration\Administrative Templates\System\Netlogon\Scavenge Interval

Further we have given the following clarification regarding the behavior described


How do computers actually use passwords?


Each Windows-based computer maintains a machine account password history containing the current and previous passwords used for the account. When two computers attempt to authenticate with each other and a change to the current password is not yet received, Windows then relies on the previous password. If the sequence of password changes exceeds two changes, the computers involved may be unable to communicate, and you may receive error messages.

When a client determines that the machine account password needs to be changed, it would try to contact a domain controller for the domain of which it is a member of to change the password on the domain controller. If this operation succeeds then it would update machine account password locally.

The client first changes the password locally and then attempts to update it in Active Directory. If the domain controller is configured with security policy "Domain Controller: Refuse machine account password changes" (i.e. RefusePasswordChange, see here and here ), then the client rolls back locally to the previous password. If the password change fails, however, the client keeps the new password locally and keeps trying to set it on the scavenge interval until it succeeds.

The local copy of the machine password is stored under:


We store the current password and the previous password under CurrVal & OldVal Keys respectively. In Active Directory, we store the password in unicodepwd and lmpwdHistory. We also store the timestamp in the pwdlastset attribute (the method to convert it into readable format is:

  • Convert the value in the attribute from decimal to hex (using calc.exe)
  • Split the result into two equal parts (8 bits for each part)
  • Run nltest /time: rightsidehex leftsidehex

The resultant value is the date and time the password was set on this computer object in AD. The cases where in you could run into problems that the KB260575 describes would be:
If you use System Restore after the password change interval expired one time, and you restore the computer to a point before the password changes, the next password change may not occur when it is due. Instead, the operating system treats the restore as if the password was changed.

Now consider the scenario, when a machine is not connected to the network for a long period. Supposing on the client:

  • Old password = null
  • Current password = A
  • New random password = B

And on the machine account in AD:

  • unicodePWD = A

After 30 days when the Scavenger thread runs, the value would be:

  • Old Password = A
  • Current Password = B

At 60th day the same process happens again. So now the newly generated password is C and the values are:

  • Old password = B
  • Current Password = C

Now when the client connects to AD, it will try the current password to authenticate. When that fails with error. Otherwise machine should be able to reset its password once it boots even after say 90 days.

Further reading:

How to detect and remove inactive machine accounts;EN-US;197478

How to disable automatic machine account password changes;EN-US;154501

Effects of machine account replication on a domain;EN-US;175468

Domain member: Disable machine account password changes

Domain member: Maximum machine account password age

Account Passwords and Policies

-       Manish Singh

[Updated with a strict clarification of the client local password rollback behavior 7-19-2012; thanks for asking, Joe - Ned]
New Contributor

@Ned Pyle  The last example is confusing:


Now when the client connects to AD, it will try the current password to authenticate. When that fails with error. Otherwise machine should be able to reset its password once it boots even after say 90 days.


in the beginning of the article, you said that the local password is never updated when there is no contact with a Domain Controller so current & previous should exactly be the same on the client as in AD when the PC contacts AD after a long time of "absence"


What am I missing?


I don't understand your question, but let me be clear here:


  • The password change process will attempt to be initiated by the scavenger process - but it will not be completed (nor will the PC’s local registry be updated with a new password), because the PC cannot see/find a DC.
  • When those PCs come back to the office in xxx days (or get VPN connectivity or whatever), the scavenge thread of the local Netlogon process on the PC will wake up and attempt the domain password change process again (it’s been trying it while offline but failing to complete because it couldn’t reach a DC).
    • However, this time, since the PC will be able to find a DC, it will complete the local password change, the DC will update the pwd of the computer object in its copy of AD, then repl that out to other DCs, and all will be well.
    • This assumes:
      • The device is unable to communicate AT ALL with a DC while offline.
      • The device isn’t partially blocked/filtered in communicating to a DC once it gains corp-net connectivity (i.e. some ports are blocked via a firewall)
      • There aren’t any scripts running on-prem that delete/disable computer accts
      • AD replication is working

This is a very old article that I didn't write, so we are working to have an updated, clarified article published as soon as possible by the current owners of the AskDS blog. 

New Contributor

Thanks! 100% clear now


Hello Ned,

my question is how does it work, for the machine account password of the Domain Controller server itself (in case the Domain controller is usually offline, like on the ship etc.). Does DomainController's scavenger wait until other DC or PDC is online or the DC changes its machine account password within itself, because it is DC as well? Does the AD synchronization work well, if the offline DC had changed its machine account password for 3 times and it was brought online? Or any other issues?

Version history
Last update:
‎Apr 04 2019 01:52 PM
Updated by: