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
  • Sorry for confusing that I wasn't entirely sure.

    Currently our desktop machines do not have a secondary location.

    They have a single primary location set for updating from, so I don't think they could have gotten ahead of the local SUM by updating from another.

    If is possible that there database on the SUM was "stuck" in some way?

    Perhaps it became busy. Or there was a momentary freeze in the system that caused it to stop logging correctly.

    This might explain why it only affected a handful of machines instead of every single machine...

    Not to sure..

    Cheers

    :7519
Reply
  • Sorry for confusing that I wasn't entirely sure.

    Currently our desktop machines do not have a secondary location.

    They have a single primary location set for updating from, so I don't think they could have gotten ahead of the local SUM by updating from another.

    If is possible that there database on the SUM was "stuck" in some way?

    Perhaps it became busy. Or there was a momentary freeze in the system that caused it to stop logging correctly.

    This might explain why it only affected a handful of machines instead of every single machine...

    Not to sure..

    Cheers

    :7519
Children
No Data