Sophos Central Endpoint and SEC: Computers fail/hang on boot after the Microsoft Windows April 9, 2019 update. Please follow knowledge base article 133945
Learn about the Benefits of Multi-Factor Authentication (MFA). Turn your MFA on now!
We'd love to hear about it! Click here to go to the product suggestion community
we have to prepare a Computer that is not in our Company-Network. Which means the Computer has access to the Primary Update Address (Sophos) but not to the secondary Update Address
(our Sophos Update Server in our Company-Network).
Is there a possibility that the Sophos Endpoint Computer will lose the license or will stop working since he can not connect to the Sophos Enterprise Console anymore?
Even though he will get his updates directly from Sophos with the correct username and password.
are you indeed talking about the SEC-managed SESC and a managed endpoint? SESC does not permit Sophos as Primary update location (endpoints are supposed to update primarily from an on-site location, Sophos is just a fallback). If SEC then it could work in principle in two ways:
In both cases your updating credentials identify your license and could be transferred to additional endpoints outside your "jurisdiction".