Synchronised User ID on Windows 7

Which Endpoint SKU and which version is currently installed on the win7? 

Versions are as follows for Windows 7 and Windows 10 endpoints I sampled:

Agent Version - 10.8.3 VE3.74.1
Core - 2.2.2
Intercept X - 2.0.12
Endpoint Advanced - 10.8.3

James

The new EDR SKU? No the customer has not licensed that at this time.

James

Do you see any failed Authentication attempts in Live Log on XG? 

I've checked the authentication (and all other logs), and also the logfiles in /log. There is no reference to authentication failures, and no reference to either the username or computer name of the devices that are not authenticating. It's more like they are not even trying to authenticate, as opposed to trying and failing.

The only difference between the authenticating and the non-authenticating endpoints is the OS. I am actually seeing a small number of users who use Windows 7 devices in the authentication user list, but I believe the client has installed the authentication agent to get around this issue for now, or alternatively the user has logged into the portal and that's why their are showing up.

James

First of all, you should see under Liveuser the Facility used to authenticate.

So there is no Win7 Client with Heartbeat? 

I do not have any Win7 Client right now to reproduce, but as far as i know, this should still be supported and work. 

Heartbeat appears to be working fine, just no authenticated user.

Hi James,

There is a bug open for this, you can test it yourself by disabling tamper protection and re-logging in and it should work. 

Is there a bug number I can track? Do you know what the ETA is?

Does the workaround require that tamper protection remain off, or could I turn if off for a bit and then users will remain authenticated?

thanks

James

Hello James,

At the moment the workaround is to disable tamper protection on windows 7 Machine without disabling the global policy. The issue is reported with us.

ref: WINEP-18113

\

Hi any news regarding this case ?

I see this is still a problem or was it fixed? 

Have same thing happening with some Win7 clients. Win10 is okay.

I see this is still a problem or was it fixed? 

Have same thing happening with some Win7 clients. Win10 is okay.