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

SEC. Secondary Server - Can it be Sophos direct?

I'm running the latest version of SEC within our organisation. All is now well after a bit of a disaster where the machine running the server spectacularly fell-over.

We have a single instance of the server and this appears to work fine for our use. I do however have some laptop users who might be away from the office for an extended amount of time and may not "check in" via our VPN.

So of course there is the chance I've got out of date machines that are at risk until they come back onto the main network and get updated.

So, to me couple of options.

1. Is it possible to set the secondary server configuration so that clients, on the event that they cannot contact my main internal server instead attempt to update dirtectly from Sophos?

If this isn't an options, we have:

2. I have a "public" facing server that can be accessed. I say public facing, what I mean is a machine on the internal network with port forwarding in place at our router.

If this is the only viable option, does anyone know what ports and or range of ports would need to be forwarded?

Thanks.

This thread was automatically locked due to age.

Parents

0 QC over 12 years ago

Hello Aminocom,
if you edit an updating policy, Secondary Server tab, you'll see that Sophos appears in the Address drop down - the corresponding article is How to configure managed computers to update from the Sophos website when necessary. The legal stuff is - I'd say deliberately - vague about the exact meaning of inaccessible (it has come up several times in this forum whether this applies to emergencies only or also to routine operation). Rather clear is that it is not meant as regular updating source for Home Use.
if you have a significant number of "off-site" clients you should consider providing an updating location. You could make your server "public" but usually one creates a WebCID for this purpose (instead of forwarding NetBIOS) please see Configuring Microsoft Internet Information Services for endpoint updating for details. You might also want to read Summary of port configurations in Sophos applications if you'd like to be able to manage these clients.
HTH
Christian
:35623
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 QC over 12 years ago

Hello Aminocom,
if you edit an updating policy, Secondary Server tab, you'll see that Sophos appears in the Address drop down - the corresponding article is How to configure managed computers to update from the Sophos website when necessary. The legal stuff is - I'd say deliberately - vague about the exact meaning of inaccessible (it has come up several times in this forum whether this applies to emergencies only or also to routine operation). Rather clear is that it is not meant as regular updating source for Home Use.
if you have a significant number of "off-site" clients you should consider providing an updating location. You could make your server "public" but usually one creates a WebCID for this purpose (instead of forwarding NetBIOS) please see Configuring Microsoft Internet Information Services for endpoint updating for details. You might also want to read Summary of port configurations in Sophos applications if you'd like to be able to manage these clients.
HTH
Christian
:35623
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data