Client error state blank

[JamesMcG 0]

Can't figure out what's going on here with the 'worst functionality problem'. This started happening after upgrading the workstations to 6.6. Any ideas?

If we check on the client side it's basic stuff like e-mail or web filtering disabled, which is a whole other issue. The clients in this screenshot have the same policy applied so there's no reason one should have modules disabled and another not...

[Marcos 5,070]

It could be caused by web / email protection or protocol filtering disabled or malfunctioning on the client. It is a known bug that the error message is not shown in the ERA console.

Anyways, if the computer has access to the Internet, I'd strongly recommend keeping protocol filtering and web/email protection enabled, or you'll disable a substantial protection layer that protects users from Internet-borne threats.

[MichalJ 434]

@JamesMcG Can you post a screenshot of the one computer of the affected ones from the section "Computer Details" / "Alerts" ?

Edited January 16, 2018 by MichalJ

[JamesMcG 0]

Looks like Marcos is right! If we manually enable it it clears the state in ERA. I'm going to try and force it on via policy for the other error state clients. Thanks!

[MichalJ 434]

Just to let you know - you can suppress those warnings via policy for Endpoint  / user interface / application statuses.

We will also fix this in the upcoming version.

Edited January 16, 2018 by MichalJ

[JamesMcG 0]

Ok good to know, I do want the functionallity to work however. I have made some progress, most are now showing Web Access protection is non-functional. Seems on those systems even with the policy defined to force it on it fails to start. Locally it's locked/greyed out, and set to off! If I try a manual update I get:

 

If I check into the advanced settings on the client the user/pass is there. Same policy/settings as my fully working clients.

[MichalJ 434]

This is most probably the same issue as described in another thread here on forum.

Please deactivate the clients from ELA and the reactivate them either locally or via era activation task. That should resolve the issue with clients not being able to update.