Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

RD Web Access: "Your password is expired. Please contact your administrator for assistance."

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

Two different messages appear on the RD Web Access sign-in page, and they need different fixes. "The user name or password that you entered is not valid. Try typing it again." means a wrong user name or password, or a locked account, because Microsoft's page says a locked account shows the same message. Microsoft's page sends the user to the Active Directory administrator to reset the password and, if needed, to unlock the account. "Your password is expired. Please contact your administrator for assistance." means the password has expired and the website has not been set up to let people change it; an administrator can switch on a link that lets users change an expired password themselves.

What the error means

RD Web Access is the website that lets people use a web browser to reach RemoteApp and Desktop Connections. Microsoft's Remote Desktop Services roles page describes it as a web portal that launches desktops and applications through the device's native Remote Desktop client, and says it needs Internet Information Services (IIS) to work. For a forgotten password, a locked account and an expired password with no change link, Microsoft's page sends the user to the Active Directory administrator.

That has one practical result. A password problem is a domain account problem that happens to surface on a web page. For a forgotten password, the page says you must contact your Active Directory administrator, and when the cause is a lockout the sign-in page shows the same wording as for a mistyped password, so the screen alone cannot tell the two apart.

Microsoft's page describes four situations:

  • The user name or password is wrong. Microsoft's page shows "The user name or password that you entered is not valid. Try typing it again."
  • The account is locked because of too many incorrect sign-in attempts. The same message appears.
  • The password does not meet the criteria for the domain. The user is told to contact the Active Directory administrator.
  • The password has expired. If an administrator has not enabled password reset, Microsoft's page shows "Your password is expired. Please contact your administrator for assistance." If password reset is enabled, a link appears that leads to a change-password form asking for the old password, the new password and a confirmation of the new password.

Likely causes

Cause What you see How to confirm
Wrong user name or password "The user name or password that you entered is not valid. Try typing it again." The same account signs in to another domain service with the same password, or fails everywhere
Account locked after too many incorrect attempts The same "not valid" message, even with the right password An administrator sees the account as locked in Active Directory; the Security log shows event 4740
Password expired and web password change not enabled "Your password is expired. Please contact your administrator for assistance." and no change link The PasswordChangeEnabled application setting for RDWeb is not true
New password rejected A message that the password does not meet the criteria for the domain, or the length, complexity or history requirements The password policy of the domain; the administrator can state the requirements
Forgotten password The user cannot supply the old password to the change form The user does not know the current password

Prove the cause before changing anything

Start with the exact words on the screen. Get a screenshot or the full message text from the user. The two messages above point to different causes, and a guess here sends the wrong person to the wrong server.

If the message is "The user name or password that you entered is not valid. Try typing it again.", do not ask the user to try again several times. Microsoft's account lockout page explains why: the account lockout threshold setting sets the number of failed sign-in attempts that will cause a user account to be locked, and a locked account can't be used until it is reset or until the lockout duration expires. The same page lists 0 as the default for the default domain policy, which it describes as accounts not being locked. That lockout page is a Windows 10 and Windows 11 policy page and does not say what your domain controllers use, so a threshold may or may not be set. Ask the Active Directory administrator what the domain's threshold is before assuming a lockout.

Then ask the Active Directory administrator to look for event 4740, "A user account was locked out." Microsoft's page says this event is generated every time a user account is locked out, on domain controllers, member servers and workstations. The event carries a field named Caller Computer Name, described as the name of the computer account from which the logon attempt was received and after which the target account was locked out. Microsoft's page defines the field only that way, so what it shows is a lead, not proof: if the field names the RD Web Access server, look at the website first; if it names another machine, look at that machine first.

If the message is "Your password is expired. Please contact your administrator for assistance.", read the current RDWeb setting without changing it:

  1. On the server that runs RD Web Access, open Server Manager.
  2. Under Tools, open Internet Information Services (IIS) Manager.
  3. Locate the server and go to Sites > Default Web Site > RDWeb > Pages.
  4. Select Application Settings and read the value of PasswordChangeEnabled. Write the value down.

If the value is not true, that explains why no change link appears. This step changes nothing.

Fix

Wrong password. The user retypes it once, slowly. If it fails again, Microsoft's page directs them to the Active Directory administrator to reset the password.

Locked account. An Active Directory administrator resets the password and, if needed, unlocks the account. Microsoft's pages describe the outcome (a locked account is unusable until it is reset by an administrator or the lockout duration expires) but Microsoft's pages give no unlock command, so use your normal directory administration tools.

Password rejected by domain rules. The user chooses a different password, or the administrator tells them the requirements. Microsoft's page says to try a different password or ask the administrator what the length, complexity or history requirements are. Nothing on the web server needs to change.

Expired password with no change link.

Save first: record the value you read earlier.

Disruptive step: switching on the password-change link changes how the RD Web Access sign-in page behaves for every user of that site. Impact: users with an expired password get a link to a form that takes the old password, a new password and a confirmation.

An administrator can switch the link on:

  1. In IIS Manager, go to Sites > Default Web Site > RDWeb > Pages.
  2. Select Application Settings.
  3. Select PasswordChangeEnabled and change the value to true.

Back-out: return to the same screen and set PasswordChangeEnabled back to the value you wrote down. Microsoft's page mentions no restart; it says that after the change, users who try to sign in with an expired password see a link to reset the password.

Microsoft's page carries an Important note that this option isn't helpful for users who forgot their password, because the old password still needs to be entered before selecting a new password. For forgotten passwords the page says you must contact your Active Directory administrator.

Example (illustrative): A staff member at contoso.com.au returns from leave and signs in to RD Web Access on rds01. The page shows "Your password is expired. Please contact your administrator for assistance." and no link. The administrator opens IIS Manager on rds01, goes to Sites, Default Web Site, RDWeb, Pages, Application Settings, and writes down that PasswordChangeEnabled is False. The administrator sets it to True. On the next attempt the staff member sees the change link, enters the old password, a new password that meets the domain rules, and the confirmation, then signs in. If the staff member had forgotten the old password as well, this route would not work and the Active Directory administrator would reset it.

Confirm the fix

For the expired-password case, ask a user with an expired password, or a test account an administrator has deliberately expired, to try signing in. The change link should appear, and the form should accept the old password, the new password and the confirmation. Do not expire a real user's password just to test.

For the lockout case, the user signs in once after the administrator's reset. Then the administrator checks that no new event 4740 appears for the account in the following minutes. A new event whose Caller Computer Name names a device points to that device as the place the logon attempt came from; look at what is signed in there with the old password. Microsoft's event 4740 page defines the field only as the computer from which the attempt was received, so what is sending it is for you to find.

What to watch afterwards

Keep an eye on event 4740 for the accounts that use RD Web Access. Microsoft's lockout page warns that apps differ in how they handle sign-in attempts and that a connection that drops repeatedly can make later failed attempts count toward the lockout threshold, so repeated lockouts from one device deserve a closer look at that device.

After a policy change on password expiry or lockout, tell staff what they will see. The expired-password message and the wrong-password message look alike to users but need different fixes, so a short note to the help desk with both wordings saves calls.

Microsoft's page also covers changing a password from inside an established session: connect to the server using RemoteApp and Desktop Connections, press Ctrl+Alt+Del, select Change a password, then enter the old password, the new password and the confirmation. That route needs a working sign-in first.

If the server runs in Azure, Microsoft's page notes that you need to create an endpoint for public port 443 in the Azure management portal so that users can reach the RD Web Access portal. The Remote Desktop Services roles page, which describes deployments in Azure with tenants, adds that the RD Web Access virtual machine must allow inbound TCP connections on port 443 and must present a certificate whose name matches the FQDN used to reach it.

Risks and limits

  • Microsoft's page does not name the Windows Server versions it covers, and it gives no setting path other than the IIS one above. If your portal looks different, confirm the path on your own server.
  • Microsoft's pages give no command to unlock an account or to read the lockout threshold; use your directory tools or Group Policy management.
  • Enabling the password change link turns on a form that accepts old and new passwords on the website. Decide whether that is acceptable for how the site is published before you switch it on, and note that it does not help users who forgot the password.
  • A lockout threshold of 0 means accounts are never locked (the page's default for the default domain policy). Changing that value is a domain-wide decision for the Active Directory owner, and the Microsoft page itself says a denial-of-service attack "could be performed on a domain that has an account lockout threshold configured".
  • These steps have not been run or lab-tested. The IIS setting is given only through IIS Manager, which is how Microsoft's page describes it; no PowerShell or command-line route is offered.
  • If the sign-in page never loads, or the browser shows a certificate warning, this is a different fault. Fix the certificate or the network path first.

Sources