Client is out of date

Question

Hi, 
 how long is the interval for the "out of date" message? A new setup client sends this event right now after 2 days of working correctly, but the client localy tells it's all fine.

K_M · Answer

Hi Aza, 
 This worked for some of our Endpoints that were not reporting correctly:

For Endpoint not checking in to Central Console:

Disable Tamper Protection Globally

Stop the Sophos MCS Client service

Go to: C:\Programdata\Sophos\Management Communications System\Endpoint\Persist\

Delete the files: Credentials EndpointIdentity.txt All files with '.xml' extensions

Go to: C:\ProgramData\Sophos\AutoUpdate\data\

Delete the file &lsquo;machine_ID.txt&rsquo;

Go to: C:\Programdata\Sophos\Management Communications System\Endpoint\Config\

Create text file 'registration.txt'.

The file must contain the following: [McsClient] Token=YOUR_TOKEN_CODE

The TOKEN CODE should be located in this file: c:\windows	emp\Sophos MCS Install Log.txt

Search for: Property(S): TOKEN = If you don't see it in that file, try another endpoint (I had to try 3 before I found one with the TOKEN CODE).

Start the Sophos MCS Client service

Re-enable Tamper Protection Globally