Identity Awareness: Bad Connection Error After Windows Patching

[Enyi_Ajoku]

Hi,

I have Identity Awareness configured using AD Query to fetch user and machine credentials from the Domain Controller. 

Server Team did a patch update on the DC and when i do adlog a dc i get the bad credentials error. Has anyone come across this scenario and how where you able to permanently resolve it.

Thank You

[PhoneBoy]

Which precise patches did they apply?
Which version/JHF of gateway?
Also, have you considered using Identity Collector instead?

[Enyi_Ajoku]

I got  a generic answer on what was installed.

Take 76/R80.30

Identity Collector is an option i'm looking into as well

[MartinTzvetanov]

Check the user permissions and group memberships in AD. I had an issue where "somehow" the system user was not part of the right groups after patching AD

[Enyi_Ajoku]

Thank You,

Will watch out for those in the next patch update.

I also found out the account was locked and unlocking the account resolved the issue but i think the root cause is what i need to investigate in the next patch update. 

There's been previous updates and those have not impacted IA.  

[MartinTzvetanov]

expect the unexpected from MS 🙂