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

Unable to update clients auto or manually?

Farhan

Computer on my network stop getting updates from server also unable to update them manualy from console, to update them i have to start indexing service on each client machine!!! is there any simple an easy way to resolve this issue? any or any group policy to start indexing service on all computers?

:6011


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

    Jak,

    Interesting though the guy says 'start the indexing service' to make it work. Think that's a typo?

    If it's the problem you're desribing Jak then here's how I diagnose and fix remotely. Symptom initially the machines won't update and when I look across remotely at their c$ share in the c:\program files\sophos\autoupdate\cache (xp/2000) or c:\programdata\sophos\autoupdate\cache (vista/7) folder, you see a tempsavxp folder partially filled and if you try, you can't delete it manually.

    Seeing this, I remote manage the PC (right-click my computer (or computer on vista/7), select manage, at the top, click action, connect to another computr and enter the name of the failing machine, then in services and applications\services, stop the 'indexing service'. I then in the same management screen, open the 'System' index right at the bottom of the management screen and under directories, right click and 'new' directory then add "c:\program files\sophos" (or obviously c:\programdata\sophos) and 'exclude' this then restart the indexing service. Once restarted, kick off an update from the console which should then get the client up and running again.

    Close examination shows that the indexing service gets hold of one or two htm files in the cache folder which causes this. I just exclude the entire Sophos folder for safety sake since just excluding the cache doesn't stop the indexer holding a file in the main folders and preventing update again.

    Matt

    :6021
Reply
  • 0

    Jak,

    Interesting though the guy says 'start the indexing service' to make it work. Think that's a typo?

    If it's the problem you're desribing Jak then here's how I diagnose and fix remotely. Symptom initially the machines won't update and when I look across remotely at their c$ share in the c:\program files\sophos\autoupdate\cache (xp/2000) or c:\programdata\sophos\autoupdate\cache (vista/7) folder, you see a tempsavxp folder partially filled and if you try, you can't delete it manually.

    Seeing this, I remote manage the PC (right-click my computer (or computer on vista/7), select manage, at the top, click action, connect to another computr and enter the name of the failing machine, then in services and applications\services, stop the 'indexing service'. I then in the same management screen, open the 'System' index right at the bottom of the management screen and under directories, right click and 'new' directory then add "c:\program files\sophos" (or obviously c:\programdata\sophos) and 'exclude' this then restart the indexing service. Once restarted, kick off an update from the console which should then get the client up and running again.

    Close examination shows that the indexing service gets hold of one or two htm files in the cache folder which causes this. I just exclude the entire Sophos folder for safety sake since just excluding the cache doesn't stop the indexer holding a file in the main folders and preventing update again.

    Matt

    :6021
Children
No Data