This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Started using Synchronized User ID. It works for my clients, but not servers?

Hi all,

 

I Started using Synchronized User ID and all the client users are listed as "Heartbeat" awesome!

However, we also use server protection and it seems that the authentication of the users aren't working.

Its a domain account not a local account i'm testing, sam and upn match as per the documentation, and the account work fine on a "client" OS rather than a "Server" OS.

I've concluded that it's something to do with the endpoint heartbeats on the server platforms.

I've made sure that the "Heartbeat" is enabled in sophos central for the servers also.

The client Endpoint version is as follows:

Core:2.2.2

Endpoint Advanced:10.8.3

Sophos InterceptX:2.0.12

The server endpoint versions are as follow:

Server Core:2.1.3

Server Anti-Virus:10.8.2

Server InterceptX:2.0.4

 

I'm forced to use the client auth agent at the moment which i wasn't expecting to.

 

Is this all by design or have i done something wrong?

 

We've remove STAS and no longer want to use it.

 

Thanks all.



This thread was automatically locked due to age.
Parents Reply Children
No Data