Guest User!

You are not Sophos Staff.

Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 13 subscribers
  • Views 30603 views
  • Users 0 members are here
Options
Suggested
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

Client is out of date

SAATEN-UNION GmbH

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.



This thread was automatically locked due to age.
Parents
  • 0

    I am seeing the same error on several clients. The central console says they're out of date, but the local clients say they are up to date. Version 9.6.1 on Mac OS 10.12.3

    Post reinstall, and manually initiated update on the client side, and it still shows out of date.

     

    Any Suggestions would be appreciated. Thanks

  • 0 in reply to Aza Rainey

    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 ‘machine_ID.txt’
    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\temp\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
Reply
  • 0 in reply to Aza Rainey

    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 ‘machine_ID.txt’
    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\temp\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
Children
Unfiltered HTML