Guest User!

You are not Sophos Staff.

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

Issue: Sophos Central Admin – US-West region - Delays with the enforcement of Central policies on managed endpoints.

**Update 9** Root cause analysis KBA has been published: see knowledge base article for the latest.

**Update 8** As part of a routine database maintenance task customers may notice a few intermittent install and policy rendering failures. Please retry before contacting support. 7/17/2017 8:00 AM PST

**UPDATE 7** Some customers may notice a few intermittent install failures, please retry before contacting Sophos Support. 7/14/2017 2:00 PM PST

**UPDATE 6** Installations are being processed normally, service is restored. Please re-download installer from Central. 7/14/2017 9:00 AM PST

**UPDATE 5** Installations are now working as of July 13, 2017 19:00 UTC-5. See knowledge base article for the latest.

**UPDATE 4** New installs likely to still fail. http://centralstatus.sophos.com/#!/ has latest update. 

**UPDATE 3** System is now processing backlogs. Please see last updates here.

**UPDATE 2** Issue is ongoing, apologies. Impacts all areas within Central that rely on MCS communication between client and Central. 7/13/2017 8:00 AM PST

**UPDATE** Development has identified root cause and is working on a fix. 

Hello,

We are seeing delays with policy changes and enforcement in Sophos Central (US-West region) as well as installation failures due to inability of new endpoint installations to initially register. Our engineers are working to restore latency. Please note your endpoints remain protected. Updates will be provided on this thread.

KBA: https://community.sophos.com/kb/en-us/126477

Thank you,

Bob



This thread was automatically locked due to age.
Parents
  • We are experiencing the same issues as other companies.  We are experiencing the new install machines failing, we are seeing that when we run a diagnostic on the machines the computer management is having issue and provides an error with 504 gateway timeout.  Our laptop machines are loosing wifi connectivity although they are in the policy that allows wifi.  we are getting failed updates although the desktop console is update on the Sophos central console it shows out of date. 

     

    This is becoming to frequent and to often in our environment especially when you have Ransomware and Breachs at an all time high.  What is being done to resolve this issue and get our companies running at a smooth pace? are we really secure when you tell us that?  Many of us have invested great amounts of money and we are experiencing issues that last months with no true resolution that does not look good for us who truly believed in Sophos. 

     

  • This week all of our Laptops have lost WiFi connectivity.  We have Chiefs in meetings and they all lost connectivity and it has been taking hours to get them back online with wifi.  This is definitely not a good look.  As this has been happening for about 2 to 3 weeks.

     

    I have a laptop that took about 2 hour to get updated with the Communication Management and still not updating on the Sophos Central Console.  There is a huge communication delay

    in the Diagnostic Tool it show that Management Communication is failing with the error "504 Gateway Timeout.  With 4 failed attempts. the server address we are connecting to is 52.25.245.140

Reply
  • This week all of our Laptops have lost WiFi connectivity.  We have Chiefs in meetings and they all lost connectivity and it has been taking hours to get them back online with wifi.  This is definitely not a good look.  As this has been happening for about 2 to 3 weeks.

     

    I have a laptop that took about 2 hour to get updated with the Communication Management and still not updating on the Sophos Central Console.  There is a huge communication delay

    in the Diagnostic Tool it show that Management Communication is failing with the error "504 Gateway Timeout.  With 4 failed attempts. the server address we are connecting to is 52.25.245.140

Children