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

Security center shows virus protection is "out of date"?

MikeG

I get the red shield with the white cross in the tray area, when I click it I see that virus protection is "out of date". This seems to have happened to several pc's on our network. If I click the sophos shield though it seems to be up to date.

I'm running XP Pro SP2. Sophos version is endpoint security and control version 9. Right now it shows that last updates were checked 10/11/2010 i.e. today, and on-access scanning is enabled.

Can anyone help?

:5886


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

    Well it looks like the client is happily "checking" for updates from:

    \\YMCA-SVR1\SophosUpdate\CIDs\S014\EECSXP\

    The next question is, is:

    \\YMCA-SVR1\SophosUpdate\CIDs\S014\EECSXP\

    being updated by SUM correctly?  If you look in that location and order by the file type and find the  ".ide" files, what is the most recent time?  It should be from today.  If not, you would then need to check Sophos Update Manager is ok and if that is updating from Sophos.

    Also are all the clients that are working/not working using this same location?

    The server is requesting a reboot but this would only be for the endpoint protection software on the machine and wouldn't affect the management of the other machines. That being said I would suggest rebooting the server if you can.  The reboot might sort out Sophos Update Manager as well if that is currently failing.  After the reboot, maybe check:
    \\YMCA-SVR1\SophosUpdate\CIDs\S014\EECSXP\ 

    15 minutes after start-up to see if a new ide has been added.  If it has, then you can force an update on your failing client and see if the new update is taken.

    As a slight aside, I also notice you are getting:

    "Could not find a source for updated package Sophos PureMessage"

    This would suggest that PureMessage is installed on the server machine, I.e. PureMessage is registered with AutoUpdate, so AutoUpdate is looking for Spam rule updates: it won't however find them from the local CID, it would need to update from Sophos to get those or at least I think that's correct, I've not used PureMessage for quite some time.  So for the server at least you would need to configure the secondary location to be Sophos.

    As there are quite a few questions outstanding and if you get stuck after the reboot it might be best to give Support a quick call mentioning you have a machine which is updating from the CID \\YMCA-SVR1\SophosUpdate\CIDs\S014\EECSXP\ ok but the last actual install time is old.  Can they help you check that Sophos Update Manager is updating the CID correctly.

    I'd also mention you have PureMessage and you'd like to check if the Spam rules are being installed and that AutoUpdate on the machine is configured correctly to obtain them.

    Good luck.

    Thanks,

    Jak

    :5893
Reply
  • 0

    Well it looks like the client is happily "checking" for updates from:

    \\YMCA-SVR1\SophosUpdate\CIDs\S014\EECSXP\

    The next question is, is:

    \\YMCA-SVR1\SophosUpdate\CIDs\S014\EECSXP\

    being updated by SUM correctly?  If you look in that location and order by the file type and find the  ".ide" files, what is the most recent time?  It should be from today.  If not, you would then need to check Sophos Update Manager is ok and if that is updating from Sophos.

    Also are all the clients that are working/not working using this same location?

    The server is requesting a reboot but this would only be for the endpoint protection software on the machine and wouldn't affect the management of the other machines. That being said I would suggest rebooting the server if you can.  The reboot might sort out Sophos Update Manager as well if that is currently failing.  After the reboot, maybe check:
    \\YMCA-SVR1\SophosUpdate\CIDs\S014\EECSXP\ 

    15 minutes after start-up to see if a new ide has been added.  If it has, then you can force an update on your failing client and see if the new update is taken.

    As a slight aside, I also notice you are getting:

    "Could not find a source for updated package Sophos PureMessage"

    This would suggest that PureMessage is installed on the server machine, I.e. PureMessage is registered with AutoUpdate, so AutoUpdate is looking for Spam rule updates: it won't however find them from the local CID, it would need to update from Sophos to get those or at least I think that's correct, I've not used PureMessage for quite some time.  So for the server at least you would need to configure the secondary location to be Sophos.

    As there are quite a few questions outstanding and if you get stuck after the reboot it might be best to give Support a quick call mentioning you have a machine which is updating from the CID \\YMCA-SVR1\SophosUpdate\CIDs\S014\EECSXP\ ok but the last actual install time is old.  Can they help you check that Sophos Update Manager is updating the CID correctly.

    I'd also mention you have PureMessage and you'd like to check if the Spam rules are being installed and that AutoUpdate on the machine is configured correctly to obtain them.

    Good luck.

    Thanks,

    Jak

    :5893
Children
No Data
Unfiltered HTML