Issue:
When attempting to log on to a Windows system, the error message: "Your account is configured to prevent you from using this computer. Please try another computer." is received. The system then returns to a logon screen.
Environment:
Windows workstation. Non-Administrator account login.
Symptoms:
An administrator account appears to be able to log into a target system, but "standard" users cannot. The standard account is not locked.
Solution:
There was a corrupt entry in the registry for the item: "HKLM\System\CurrentControlSet\Control\LSA\CrashOnAuditFail" This should be a DWORD of 0 or 1 only. I recommend 0. Unsure as to the root cause of the corruption. Review the system's event logs. This issue is likely to take effect if the logs are full, thus impacting the ability to perform "audits".
It is worth reviewing all of the system logs and clearing them off.
Even after doing all this, the issue may still remain. It may take a reboot or a little bit of time before the system will allow for a login, especially if the computer is "slow".
Note:
If the solution provided does not resolve the issue, the following may help:
In ADUC on a domain environment, the account may be limited as to which systems it is allowed to "Log On To..."
The login hours of the account may be impacting the abillity to login.
When attempting to log on to a Windows system, the error message: "Your account is configured to prevent you from using this computer. Please try another computer." is received. The system then returns to a logon screen.
Environment:
Windows workstation. Non-Administrator account login.
Symptoms:
An administrator account appears to be able to log into a target system, but "standard" users cannot. The standard account is not locked.
Solution:
There was a corrupt entry in the registry for the item: "HKLM\System\CurrentControlSet\Control\LSA\CrashOnAuditFail" This should be a DWORD of 0 or 1 only. I recommend 0. Unsure as to the root cause of the corruption. Review the system's event logs. This issue is likely to take effect if the logs are full, thus impacting the ability to perform "audits".
It is worth reviewing all of the system logs and clearing them off.
Even after doing all this, the issue may still remain. It may take a reboot or a little bit of time before the system will allow for a login, especially if the computer is "slow".
Note:
If the solution provided does not resolve the issue, the following may help:
In ADUC on a domain environment, the account may be limited as to which systems it is allowed to "Log On To..."
The login hours of the account may be impacting the abillity to login.
