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

Setting Sophos As Primary Update Location in Sophos Deployment Packager

Hello there,

I am trying to make an endpoint client install for offsite users that updates from Sophos and I am using the Sophos Deployment Packager. How do I point the package to update from Sophos? The location asks for a UNC and I have seen on the forums that it is not a good idea to put the full address to the sophos update server due to it changing from time to time.

What do I do?

Thanks

:44235


This thread was automatically locked due to age.
Parents
  • Hello Crayadder,

    that's to comply with the license agreement. If you do not want these computers to be managed (i.e. you do not include RMS) you can simply define the Secondary location as Sophos. The client will first try your regular Primary location and as this fails fall back to the Secondary. This introduces some latency and causes an error to be written to the updating logs but has otherwise no adverse effect.

    Feel free to ask if you have further questions.

    Christian

    :44239
Reply
  • Hello Crayadder,

    that's to comply with the license agreement. If you do not want these computers to be managed (i.e. you do not include RMS) you can simply define the Secondary location as Sophos. The client will first try your regular Primary location and as this fails fall back to the Secondary. This introduces some latency and causes an error to be written to the updating logs but has otherwise no adverse effect.

    Feel free to ask if you have further questions.

    Christian

    :44239
Children
No Data