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

Install Sophos Cloud Endpoint on Master Image

StevenGear

Recently a new sophosinstall.exe was released on the cloud portal and we had been having success in deploying the client to our master image PC and then capturing that image to be installed via MDT.  Ever since the release of the new client (the old one expired), we have had an issue where each new client we image cannot start the health service and does not report back to the portal.  This also makes it impossible to uninstall the client since we cannot get a tamper protection password to disable the client.

Are there updated instructions on how to deploy the software to an image before running sysprep to capture it?

 

Thanks,

Steve Gear

Henderson Engineers



This thread was automatically locked due to age.
Parents Reply
  • 0 in reply to jak

    Thanks for the links, I don't think that information has changed since we began deploying the client so that all looks good.

     

    On an imaged computer, I looked at the health logs and found that it is reporting it cannot start the service because it cannot write the Key:

    SOFTWARE\Sophos\Health\ThreatNotification  Value=Severity

     

    When I look, the Health Key doesn't exist so I can assum this is the problem?

     

    Thanks!

Children
No Data
Unfiltered HTML