Guest User!

You are not Sophos Staff.

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

Disabling Tamper Protection in AWS

Keith Konecke

I had a few Sophos Server Protection agents deployed to AWS instances.  I created images of those instances, launched them in a new VPC, and deleted the originals.  Once the images were launched in a new VPC they lost their connectivity with Central.  I'm unable to do anything with them because I can't disable tamper protection, and it's my understanding that I cannot boot an EC2 instances into Safe Mode without losing connectivity.  What can I do?



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

    We have created the below article to outline steps on how to recover both AWS and Azure instances.

     

    community.sophos.com/.../127602

  • 0 in reply to WomboCombo

    Is this still the only way? 

     Just attempted out first AWS server installation and of course it failed with no explanation (typical) and now I cant disable tamper protection from the console, because it just doesn't work. I also cant use the local password to get into the admin settings, because it also just doesn't work. Not sure the point of it.

     

     

  • 0 in reply to LRB

    Hi Lance,

    Can you confirm what is remaining on the machine after the failed installation? Can you open up SophosUI.exe from C:\Program Files\Sophos\Sophos UI

    If this exists you can then view the tamper protection password in central and manually authenticate using the "Admin Logon" section.

  • 0 in reply to WomboCombo

    Hey WomboCombo,

     

    Found the problem was due to how long the product takes to install.

    The current sequence of spinning up, installing all other required software, joining domain and then rebooting doesn't allow enough time for Sophos to install (by far the longest)

     

    Not really sure what our options are now. 

Reply
  • 0 in reply to WomboCombo

    Hey WomboCombo,

     

    Found the problem was due to how long the product takes to install.

    The current sequence of spinning up, installing all other required software, joining domain and then rebooting doesn't allow enough time for Sophos to install (by far the longest)

     

    Not really sure what our options are now. 

Children
No Data
Unfiltered HTML