Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 1 subscriber
  • Views 1553 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

Update Sources; Update Failed Error Messages

Prejay

Hi Guys,

I'm sure some of you have encountered this before.

The primary update source is set to the local update server, with Sophos being a secondary source.

A laptop gets taken offsite, and can't reach the local source, so the user gets an update failed popup message.

It then updates from Sophos and everything is fine.

Is there no way to stop the misleading popup message? 

It seems like the type of false positive error message that shouldn't be around after 10 versions. 

:24229


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

    Hello Prejay,

    guess the AutoUpdate log shows that the download of RMS failed. As this is the correct behaviour you could argue that the error shouldn't appear. OTOH by the lincense agreement the client should always update from your site under normal conditions (i.e. if your clients are regularly used off site you should provide access either through VPN or a WebCID). Thus updating from Sophos is correctly identified as a problem - although the failed is admittedly misleading.

    Christian

    :24235
Reply
  • 0

    Hello Prejay,

    guess the AutoUpdate log shows that the download of RMS failed. As this is the correct behaviour you could argue that the error shouldn't appear. OTOH by the lincense agreement the client should always update from your site under normal conditions (i.e. if your clients are regularly used off site you should provide access either through VPN or a WebCID). Thus updating from Sophos is correctly identified as a problem - although the failed is admittedly misleading.

    Christian

    :24235
Children
No Data
Cookie Information Banner