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 computers - Up to date status: unknown

Hey,

Enterprise Console: v 4.5.1

Endpoint: v 9.5

I have a problem that has quite literally come out of the blue.

I have 42 computers of about 280 total that are currently reporting that their "Update to date" status is "Unknown"

This appeared around 11:30 a.m. today.

When I had checked the Sophos Enterprise Console  this morning there were no such reports.

Each machine is reporting a status of:

Up to date: Unknown

Time installed package becamse available: Unknown

Time next package became available: Unknown

I ran across this thread:

It describes the exact same problem that I am having.

This issue though was reported way back in June and has already been corrected.

Is anyone else experiencing this same issue?

I have not made any changes to any of the policies and we have not made any changes to the network or the server.

Any ideas as to what might be causing this?

Thank you

Cheers

:7481


This thread was automatically locked due to age.
Parents
  • The entry in the agent log regarding SUM would only be on the SUM machine, not on all the clients.

    As for "one taking longer to update" I'm referring to SUM pushing out CIDs.  If SUM is having to write a second or third CID over a slow link that could take longer and therefore increase the overall time SUM takes to update all the CIDs, this in turn would extend the period between the first CID being updated (and possibly a client updating) and the status message from the SUM regarding the package info.

    As you only have a single SUM and a single CID, this wouldn't be the case.

    Do the clients update from Sophos as a secondary location, could this have happened? Could the clients have gotten "ahead" of the local SUM and therefore reported in a package unknown to SUM until SUM caught up?

    Jak

    :7517
Reply
  • The entry in the agent log regarding SUM would only be on the SUM machine, not on all the clients.

    As for "one taking longer to update" I'm referring to SUM pushing out CIDs.  If SUM is having to write a second or third CID over a slow link that could take longer and therefore increase the overall time SUM takes to update all the CIDs, this in turn would extend the period between the first CID being updated (and possibly a client updating) and the status message from the SUM regarding the package info.

    As you only have a single SUM and a single CID, this wouldn't be the case.

    Do the clients update from Sophos as a secondary location, could this have happened? Could the clients have gotten "ahead" of the local SUM and therefore reported in a package unknown to SUM until SUM caught up?

    Jak

    :7517
Children
No Data