Alan Posted November 21, 2018 Share Posted November 21, 2018 Just noticed this today. On Oct 8 we updated to build 8491 from build 8411. Ever since then the heartbeat checks for local windows OS accounts for domain member servers is failing. The passwords are correct but the validation checks fail. Just updated today to build 8537 and the heartbeat checks are still failing. Heartbeat checks for AD domain accounts are working, just not the local Windows accounts. All of the servers being checked are domain member servers. Link to comment Share on other sites More sharing options...
support Posted November 22, 2018 Share Posted November 22, 2018 Hi Alan, Sorry you're having some issues. Could you share the auditing data for this failure? Thanks very much. Regards Click Studios Link to comment Share on other sites More sharing options...
Alan Posted November 26, 2018 Author Share Posted November 26, 2018 Here's the audit log entry. To reiterate all these systems are domain member servers on the same domain as the PasswordState server. A scheduled Account Heartbeat check failed to validated the password for account {obscured} (\OS Accounts\Windows Local) of Account Type 'Windows' on Host {obscured}. Error = Failed to validate the local password for account '{obscured}' on Host '{obscured}' - This account is not authorized to connect to '{obscured}'. If '{obscured}' is a Workgroup machine, '{obscured}' must be a Local Administrator, and the 'LocalAccountTokenFilterPolicy' registry key must be set correctly. Link to comment Share on other sites More sharing options...
support Posted November 27, 2018 Share Posted November 27, 2018 Hi Alan, Thanks for the information, and we think we might have a fix for this now. Can you contact us via our support page here https://www.clickstudios.com.au/support.aspx and we can email you a new script to try. Thanks again. Regards Click Studios Link to comment Share on other sites More sharing options...
support Posted November 30, 2018 Share Posted November 30, 2018 Hi All, Just reporting back here that we are including this fix in build 8549, which we are due to release within the next hour. Regards, Support Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now