Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 2 subscribers
  • Views 3490 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

Error reporting SUM

freebird317

I currently have a SUM server setup and in the process of getting things configured. My problem is the SUM server has an update policy with a UNC path for primary and Sophos for secondary.  When a client is outside the LAN and they try to update from the UNC path, they error and is error recorded to the console.  The client then updates fine from Sophos. If I have lots of devices off prem updating this way I will see lots of updating errors for the UNC yet the clients are updating from sophos fine.  How can I avoid this?

 

 



This thread was automatically locked due to age.
Parents
  • +1

    Hello JasonLehman,

    perhaps I'm nit-picky but SUM is the Sophos Update Manager component which just makes the updates available for the endpoints. The thingy which does the policies and collects alerts and errors is the Management Server which often goes by the name of SEC (Sophos Enterprise Console) or Console for short. This in turn is not quite correct as console is the UI to the management server.  There's always a SUM and a Console on the management server (guess you could in theory remove the latter), there can be additional SUMs and Remote Consoles. Thus in conjunction with endpoint management it's better not to refer to SUM. Excuse the rant.

    Incidentally there's a recent related post to which has replied. Specifically in your case (as Sophos is Secondary) an update error is expected. To be exact there are two kinds of errors. 1 - failures on the Primary are always reported (even if the update is successful from the Secondary) to inform you of potential problems. 2 - when Sophos is Secondary the RMS component is not updated, RMS is only updated from a site/installation-specif CID.
    Thus with your configuration you can't avoid these errors.  I'm somewhat surprised though that you see lots of updating errors. Normally sites which don't have an an off-LAN update location (WebCID) also have no RMS connectivity for off-site endpoints. As long as an endpoint is off-site it can't report its errors - it will do so once it's on the LAN again but these errors are cleared with the next update and won't persist. But even when using a WebCID as Secondary you'll see the errors for the UNC Primary.

    The only way to avoid these (reputed) errors is a public WebCID as Primary.

    Christian 

Reply
  • +1

    Hello JasonLehman,

    perhaps I'm nit-picky but SUM is the Sophos Update Manager component which just makes the updates available for the endpoints. The thingy which does the policies and collects alerts and errors is the Management Server which often goes by the name of SEC (Sophos Enterprise Console) or Console for short. This in turn is not quite correct as console is the UI to the management server.  There's always a SUM and a Console on the management server (guess you could in theory remove the latter), there can be additional SUMs and Remote Consoles. Thus in conjunction with endpoint management it's better not to refer to SUM. Excuse the rant.

    Incidentally there's a recent related post to which has replied. Specifically in your case (as Sophos is Secondary) an update error is expected. To be exact there are two kinds of errors. 1 - failures on the Primary are always reported (even if the update is successful from the Secondary) to inform you of potential problems. 2 - when Sophos is Secondary the RMS component is not updated, RMS is only updated from a site/installation-specif CID.
    Thus with your configuration you can't avoid these errors.  I'm somewhat surprised though that you see lots of updating errors. Normally sites which don't have an an off-LAN update location (WebCID) also have no RMS connectivity for off-site endpoints. As long as an endpoint is off-site it can't report its errors - it will do so once it's on the LAN again but these errors are cleared with the next update and won't persist. But even when using a WebCID as Secondary you'll see the errors for the UNC Primary.

    The only way to avoid these (reputed) errors is a public WebCID as Primary.

    Christian 

Children
Unfiltered HTML