Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 8536 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

Some Clients "Out-Of-Date"

isoffice

Hi All,

We are using Sophos Enterprise Console Version 5.1.0.1839 deploying Sophos Endpoint Security & Control (version 10.0.8) to client PC's (Windows 7) and servers (2003 & 2008).

However, SEC is stating that some clients are out-of-date despite the fact that the client logs state that they have successfully updated. Could someone enlighten me as to what may be going on here and how to resolve it.

Many thanks,

JP

:33759


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

    Hello JP,

    What do you think should be my next step

    wish I had a good suggestion :smileywink: - seriously, the OBJECT_NOT_EXIST is probably not the issue (might be more or less normal as I see it occasionally in the logs). More interesting is the Failed to send message (id=00659510) line, as it signifies that the client can't communicate upstream.

    I can think of two probably more helpful parts in the logs:

    1. the lines mentioning id=00659510 and the ones in between
    2. and the lines following a Getting parent router IOR from ...

    Also the should be a ClientMRInit log in the Windows\temp directory - maybe it is from around the date it started to fail. But anyway it has some information which could be useful in conjunction with the Router log.

    Christian

    :33815
Reply
  • 0

    Hello JP,

    What do you think should be my next step

    wish I had a good suggestion :smileywink: - seriously, the OBJECT_NOT_EXIST is probably not the issue (might be more or less normal as I see it occasionally in the logs). More interesting is the Failed to send message (id=00659510) line, as it signifies that the client can't communicate upstream.

    I can think of two probably more helpful parts in the logs:

    1. the lines mentioning id=00659510 and the ones in between
    2. and the lines following a Getting parent router IOR from ...

    Also the should be a ClientMRInit log in the Windows\temp directory - maybe it is from around the date it started to fail. But anyway it has some information which could be useful in conjunction with the Router log.

    Christian

    :33815
Children
No Data