Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 1 subscriber
  • Views 877 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

Shh/Updater-B server fix

jcetas

I repaired the sophos server soon after the problem appeared, however I failed to realize that the sophos agent running on the sophos server was also affected.  Should I run FixUpdate.vbs on the server to repair the local agent?  The CID is working fine and I'm worried about breaking a working server, which would affect 1000 agents.  If the script may cause problems with the server, how can I repair the local agent manually?

:36177


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

    Hi,

    When you say the Sophos agent, do you mean, the 'client side' components, e.g.

    • Sophos Anti-Virus
    • Sophos AutoUpdate

    Do you know which component specifically has the problem?

    It might be safer to just re-bootstrap the server from the CID, e.g. just run:

    \\[server]\sophosupdate\cids\s000\savscfxp\setup.exe

    (You mway want to double check the file iconn.cfg under: "C:\programdata\sophos\autoupdate\config") to ensure you get the right path if you have multiple subscriptions.

    Regards,

    Jak

    :36179
Reply
  • 0

    Hi,

    When you say the Sophos agent, do you mean, the 'client side' components, e.g.

    • Sophos Anti-Virus
    • Sophos AutoUpdate

    Do you know which component specifically has the problem?

    It might be safer to just re-bootstrap the server from the CID, e.g. just run:

    \\[server]\sophosupdate\cids\s000\savscfxp\setup.exe

    (You mway want to double check the file iconn.cfg under: "C:\programdata\sophos\autoupdate\config") to ensure you get the right path if you have multiple subscriptions.

    Regards,

    Jak

    :36179
Children
No Data