Be aware that your license credentials travel in plain text see this thread. I'd use Sophos only as a last resort i. Typically I'd suggest that if you need clients to connect directly to Sophos, then simply provide them with the standalone installer and your EM credentials and they can install that - this will only connect to Sophos and have no interaction with your environment either updating or messaging.
However, if you need a managed package, you can configure the Primary to be an internal source and Sophos to be your Secondary source - remote clients will simply fail silently on the Primary, then update from the Secondary. If you checked your local autoupdate logs, you will find the full URL for "Sophos", and could hard code this into your Primary, but I'd recommend against it - while it doesn't change often, it does change, and remote machines are the hardest ones to get at when you need to make a change to them - they would be out of luck if we had to change the URL.
Second: Hardcoded isn't be the problem - unmanaged is, isn't it? Looking into iconn. If you have already installed an update manager on a different computer, the share where that update manager downloads software and updates will appear on the list of addresses. You can select it as a source for the update manager you are configuring. Then you can move the address that you want to be the primary one to the top of the list, using the Move up and Move down buttons to the right of the list.
All rights reserved. Site Search User. On-Premise Endpoint. Thread Info. RSS More Cancel. This discussion has been locked. Address Update server Sophos.
Hi, to avoid the use of a proxy we need the full address of the Sophos server which we're using as second update server. Jo The secondary update server location may alternatively be set to get updates directly from Sophos over the internet via HTTP. All rights reserved. Legal details.
0コメント