Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 15 subscribers
  • Views 2965 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

Installation of Sophos Endpoint Protection failed on Windows 2012 R2 Standard.

chris jordan2

Good day, everyone! My name is Chris, and I'm in desperate need of your help with a problem we're having. On one of our Windows 2012 R2 STD servers, You can go or Check All Method But  we installed the Sophos Endpoint agent. It worked for a while, but eventually failed. We've attempted multiple times to install Sophos antivirus and have filed a support issue. However, the issue stays the same. Is there anyone who can assist us with this problem?



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

    I assume it's the Sophos Central client.  If you ran the installer interactively it would log here:

    \ProgramData\Sophos\CloudInstaller\Logs

    That log would give you the overview of the install.

    For each component being installed, the logs would be under the installing user's temp location, e.g. %temp%.

    If it gets as far as installing AutoUpdate, that will then pickup where the Central installer left off, and attempt to install any components that failed. This runs as local system so the logs then go to \windows\temp\

    If you can isolate the component that is failing, the component log or logs will be of interest.

Reply
  • 0

    I assume it's the Sophos Central client.  If you ran the installer interactively it would log here:

    \ProgramData\Sophos\CloudInstaller\Logs

    That log would give you the overview of the install.

    For each component being installed, the logs would be under the installing user's temp location, e.g. %temp%.

    If it gets as far as installing AutoUpdate, that will then pickup where the Central installer left off, and attempt to install any components that failed. This runs as local system so the logs then go to \windows\temp\

    If you can isolate the component that is failing, the component log or logs will be of interest.

Children
No Data
Unfiltered HTML