sodcalculator

10 Tech How-To

Fix Access Denied When Changing Active Directory Password

Guide 10-55763 · Updated · Step by step

If you’re getting an “Access Denied” error when trying to change a user’s Active Directory password, it usually means the account you’re using lacks the necessary permissions, or the password policy is blocking the change. This guide walks you through the most common causes and the exact steps to resolve them, so you can get the password reset working again.

What You’ll Need

  • An account with sufficient privileges (Domain Admin or delegated permissions) to reset passwords.
  • Access to Active Directory Users and Computers (ADUC) or PowerShell with the Active Directory module.
  • Knowledge of the user’s username and the domain name.
  • If you’re using a non-admin account, you’ll need to know how to delegate permissions (covered in the steps).

Step-by-Step

  1. Verify your account has the right permissions. The most common cause of “Access Denied” is that your account doesn’t have the “Reset Password” permission on the user object. By default, Domain Admins and Account Operators have this right, but if you’re using a delegated admin account, it may not. To check: open ADUC, right-click the user, select “Properties,” go to the “Security” tab, and click “Advanced.” Look for your account or a group you’re in. If it’s not there, you need to get the permissions added (see step 2).
  2. Delegate the necessary permissions (if needed). If you’re not a Domain Admin, ask a Domain Admin to delegate the “Reset Password” permission to your account or a group you belong to. In ADUC, right-click the OU where the user resides, select “Properties,” go to the “Security” tab, click “Advanced,” then “Add.” Select your account or group, and in the “Apply to” drop-down, choose “User objects.” Then check the “Reset password” permission under “Permissions.” Click OK.
  3. Use the correct method to change the password. There are two ways: resetting the password (admin sets a new one) or changing the password (user knows the old one). If you’re trying to change a password (user must know the old one), you can’t do that from ADUC—you’d need to use the “Change Password” option in the user’s own login screen or via a self-service portal. If you’re resetting (admin sets a new one), right-click the user in ADUC and select “Reset Password.” Enter the new password and confirm.
  4. Try using PowerShell. If ADUC is giving you an error, PowerShell might give a clearer message. Open PowerShell as an administrator and run: Set-ADAccountPassword -Identity "username" -Reset -NewPassword (ConvertTo-SecureString -AsPlainText "NewPassword" -Force) Replace “username” and “NewPassword” with your values. If this fails, it will show a more detailed error.
  5. Check the password policy. If the password you’re setting doesn’t meet the domain’s password policy (length, complexity, history), you’ll get an “Access Denied” or “Password does not meet policy” error. Make sure the new password is at least 8 characters (or whatever the policy requires), includes uppercase, lowercase, numbers, and symbols, and isn’t one of the last few passwords the user had.
  6. Verify the user account isn’t locked or disabled. If the account is locked out or disabled, you might get an error when trying to reset. Check the account properties in ADUC under the “Account” tab. If it’s locked, uncheck “Account is locked out.” If it’s disabled, uncheck “Account is disabled.” Then try the reset again.
  7. Ensure the user is not a protected account. If the user is a member of a protected group (like Domain Admins, Enterprise Admins, or Schema Admins), the password reset may be blocked by AdminSDHolder. In that case, you must be a Domain Admin (or higher) to reset the password, and even then, you might need to take ownership of the object temporarily. This is rare, but if you’re trying to reset a domain admin’s password and getting denied, this is likely the cause.
  8. Check if the password is being changed by the user. If the user is currently logged in and has changed their password recently, there might be a replication delay. Wait a few minutes and try again.

Common Mistakes

  • Using the wrong account. Trying to reset a password with an account that doesn’t have the “Reset Password” permission is the #1 mistake. Always verify your permissions first.
  • Setting a password that doesn’t meet policy. Many admins forget the complexity requirements. Use a strong password that meets the domain policy.
  • Confusing “Reset” with “Change.” A reset is when an admin sets a new password without knowing the old one. A change requires the user to know the old password. If you’re trying to do a change from ADUC, you’ll get an error because ADUC doesn’t support that.
  • Not checking the account status. If the account is locked or disabled, the reset might fail. Always check the account tab first.
  • Delegating permissions incorrectly. When delegating, you must select “User objects” in the “Apply to” field. If you leave it as “This object and all child objects,” the permission might not apply correctly.

Tips

  • Use the “Reset Password” dialog in ADUC correctly. When you right-click a user and select “Reset Password,” you’ll see a checkbox for “User must change password at next logon.” If you check that, the user will be forced to change the password the first time they log in. This is a good practice for temporary passwords.
  • Test with a test user. If you’re new to AD, create a test user in a test OU and practice resetting passwords there before doing it on a production account.
  • Use a strong password generator. To avoid policy issues, use a password generator that creates a random string of 12+ characters with uppercase, lowercase, numbers, and symbols.
  • Document your delegation. Keep a record of who has been delegated the “Reset Password” permission, so you don’t have to troubleshoot later.
  • Check replication. If you have multiple domain controllers, make sure the one you’re working on is up to date. You can use repadmin /replsum to check replication status.

Troubleshooting

If the steps above don’t resolve the issue, try these additional checks:

  • Look at the exact error message. The error might say “Access is denied” or “Insufficient access rights.” If it’s the latter, it’s a permissions issue. If it’s “The password does not meet the password policy,” it’s a policy issue.
  • Use ADSI Edit to check permissions. Open ADSI Edit, navigate to the user object, right-click and select “Properties.” Go to the “Security” tab and check the effective permissions for your account. This will show exactly what you can do on that object.
  • Check if the user is in a protected group. As mentioned, if the user is in a protected group, the AdminSDHolder process will reset permissions on the object every 60 minutes. You might need to temporarily remove the user from the protected group, reset the password, and then add them back. This should be done carefully and only if you have the authority.
  • Try a different domain controller. Sometimes a domain controller might have a stale copy of the user object. Connect to a different DC by opening ADUC, right-clicking the domain, selecting “Change Domain Controller,” and choosing another one.
  • Check if the user’s password is being managed by a third-party tool. If you have a password management solution (like a self-service password reset tool), it might be interfering. Check the tool’s logs.
  • Verify the user’s UPN and SAM account name. If you’re using PowerShell, make sure you’re using the correct identity. Use Get-ADUser -Filter * | Select Name, SamAccountName to see the exact names.

Frequently Asked Questions

Why do I get “Access Denied” even though I’m a Domain Admin?

If you’re a Domain Admin and still getting denied, it’s likely because the user is a member of a protected group (like Domain Admins) and the AdminSDHolder process has tightened permissions. You might need to take ownership of the object temporarily or use a different method.

Can I change a user’s password without knowing the old one?

Yes, that’s called a “reset.” You can do it from ADUC by right-clicking the user and selecting “Reset Password.” The user will then need to use the new password you set.

What’s the difference between “Reset Password” and “Change Password”?

Reset is done by an admin and doesn’t require the old password. Change is done by the user and requires the old password. ADUC only supports reset, not change.

How do I delegate password reset permissions to a helpdesk user?

In ADUC, right-click the OU, go to Properties > Security > Advanced > Add, select the user or group, set “Apply to” to “User objects,” and check “Reset password” under Permissions.

What should I do if the password reset works but the user can’t log in?

Check if the account is locked or disabled. Also, if you checked “User must change password at next logon,” the user will be prompted to change it. Make sure the user is using the correct domain (e.g., DOMAIN\username).

Can I reset a password using PowerShell?

Yes. Use Set-ADAccountPassword -Identity "username" -Reset -NewPassword (ConvertTo-SecureString -AsPlainText "NewPassword" -Force). You need the Active Directory module installed.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →