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

Sophos Enterprise Console - Secondary Update Server

Hi All,

 

Currently having an issue where we have the Primary and Secondary Update servers listed on the SEC.

The primary, which is our on-prem server shows up on client machines but the secondary does not (this is linked to the account username and licencing key).

Is there a reason the secondary is not showing up?

 

All help appreciated.

 

Kind Regards

Stephen



This thread was automatically locked due to age.
  • Hi Stephen,

    Are there any other client machines connected to SEC and do they show up under client machines as connected?  Can the secondary update server connect to SEC on ports 8192/8194 and the SEC server to the secondary update server?  You can test this by installing telnet client or using Putty via telnet.

  • Hi Stephen,

     

    Is this secondary SUM newly installed?

    Can you confirm that you applied the SUM to the applicable machines AutoUpdate policy?

    Please see the following article on configuring policies to use a secondary update location for failover purposes, the article does specify using Sophos, but you can use which ever update location you choose: https://community.sophos.com/kb/en-us/12354

     Let me know if this helps.

    Thanks,

  • SUM already existed 

     

    Client machines do not see it, but the installed client on the server sees the secondary location???

    All client machines have the message awaiting transfer policy

  • Hello Stephen,

    it's not clear what you mean by machines do not see it. As you mention Awaiting policy transfer - are you perhaps talking about the Update Details view in the Console and the Secondary location is blank? If so, and if the (most, the ones that are running) endpoints show as Connected (the green icon) select them, right-click Comply with  → Group updating policy.

    Christian

  • Hi CHristian,

     

    All machines have a cross through them and have the Awaiting policy transfer  apart from the client software installed on the SEC server itself

     

    Kind Regards

    Stephen

  • Hello Stephen,

    you did reprotect them and they did connect after install, i.e. the down-arrow and the hourglass disappeared from the computer icon and there are no error messages?
    You can in addition check from the Computer Details view, column Last message time.

    Christian

  • Hi Christian,

    I reprotected them, got the hourglass, then they went back to a cross next to the machine

     

     

    Above is what I am currently seeing

     

    Kind Regards

    Stephen

  • Hello Stephen,

    guess the error reported are install errors, could you check the Alert and Error Details view, the Update errors column is on the far right. Or double-click a computer to view its details.

    Could it be that a firewall (network or server-local, unlikely on the endpoints) is blocking the connection? Simple test is to try to telnet to port 8192 on the management server from an endpoint.

    Christian

  • Hi Christian,

     

    I get the following on the install error section on most of the endpoints.

     

    Kind Regards

    Stephen

  • There's also nothing blocking ports as far as I can see