topic Identity Awareness: Bad Connection Error After Windows Patching in Firewall and Security Management

Identity Awareness: Bad Connection Error After Windows Patching

Enyi_Ajoku — Fri, 05 Jun 2020 17:54:54 GMT

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

Re: Identity Awareness: Bad Connection Error After Windows Patching

PhoneBoy — Mon, 08 Jun 2020 02:13:45 GMT

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

Re: Identity Awareness: Bad Connection Error After Windows Patching

MartinTzvetanov — Mon, 08 Jun 2020 08:01:31 GMT

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

Re: Identity Awareness: Bad Connection Error After Windows Patching

Enyi_Ajoku — Mon, 08 Jun 2020 13:19:43 GMT

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.

Re: Identity Awareness: Bad Connection Error After Windows Patching

MartinTzvetanov — Mon, 08 Jun 2020 13:21:04 GMT

expect the unexpected from MS 🙂

Re: Identity Awareness: Bad Connection Error After Windows Patching

Enyi_Ajoku — Mon, 08 Jun 2020 13:57:13 GMT

I got a generic answer on what was installed.

Take 76/R80.30

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