Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 12805 views
  • Users 0 members are here
Options
Suggested
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 as primary update location

biosmatrix

Hello,

I'd like our laptops to always update from 'Sophos' with the primary location being direct, secondary through our proxy.

Now 'Sophos' is only a selectable option in secondary server, what do I need to put as the URL in the Primary to get this to update from 'Sophos' ?

:413


This thread was automatically locked due to age.
Parents
  • 0

    Biosmatrix:

    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.

    Hope this helps,

    :445
Reply
  • 0

    Biosmatrix:

    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.

    Hope this helps,

    :445
Children
No Data
Unfiltered HTML