• ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
The HP Community is where owners of HP products, like you, volunteer to help each other find solutions.
HP Recommended

Hi,

 

we have been having issues with AD users not being able to login (incorrect password/ login) when we know the detials ar correct and the console was accepting AD users onto the console ok though.

 

Our supplier hasn't been any help and given the product is end of life (so they told us) we reset the AD settings and when that didnt work, we tried a restore of the database from before the issue occured.

 

The issue we have now is the restore appears stuck after "Configured Certificates have been restored" - its been at this stage for about 3 hours.

 

Is this normal - can we get out of it?

 

Thanks in advance

1 REPLY 1
HP Recommended

Your initial problem was caused by a Microsoft patch, KB3002657, that was release about 6 weeks ago and most likely was just recently installed on the AD server. The patch changes the way the NETLOGON process validates computer accounts. There are 3 workarounds:

 

1) Use local accounts rather than AD accounts when logging in with CMAD or RPD.

2) Open a service request. There is a workaroung where we can determing the NETBIOS name the CMA is using and create a new computer account in AD based on that. The biggest disadvantage of this it that it won't survive a reboot of the CMA server. You would have to run the whole procedure again.

3) Wait for the CMA patch that is tentatively scheduled for sometime around the end of May.

 

As for the database restore issue, since this post is over a week old I'm assuming you have already address that. probably by rebooting the server. Normally I would be concerend about database corruption by doing that but since you waited 3 hours there was a good chance that the system came back up after the reboot.

 

 

† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.