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

Download of Sophos AutoUpdate failed from server... incorrect CID location

Zatol

Quick question... maybe. I've recently taking over administering Sophos Anti-Virus on our network. I've read through a lot of the forums here and it seems most people are managing very few computers. I'm managing 20,000+, so I'm looking to see if there's a different response than "re-install the Endpoint client."

Basically, we have our main SophosAV box and somewhere around 20 relays (I have not counted them). I am seeing a lot of updating errors that deals with computers clients pointing to the wrong CID files. So where as the actual CID folder on the relay is S033, the update is pointing to S038 and failing every single time. This is leaving me with a ton of errors (3,400 errors) thus far, and a ton of them are related to failing to download the updates.

Is there a location to easily change where the Endpoint client looks for update? If the bootstrap location of the update is in S038, and the updating policies for the relays are correct, then why is my client still looking toward S033 for the update? I'm really looking for a solution other than re-install the Endpoint client because pushing it to all of my clients is no small task, especially in this environment.

Appreciate any help. 

:17893


This thread was automatically locked due to age.
Parents
  • 0
    Seems a strange setup and might take some time to sort out as it looks like there was some misconception.
    Now you should have quite a lot of updating policies in SEC. And from what you said they all (or many of them) point to the same location. What makes them update from different CIDs is the so-called Subscription (you'll find a tab for it in the policy). These in turn are managed in the Update Mangers view.
    It seems that
    1) clients update from a central web server (assuming the name does not resolve to different servers at the sites)
    2) the different CIDs are used to configure message relays
    The combination is not ideal, or better far from ideal.

    There's more than one way to skin a cat. For now, please take a look at the subscriptions and if the relays are in the correct SEC groups.

    Christian
    :17907
Reply
  • 0
    Seems a strange setup and might take some time to sort out as it looks like there was some misconception.
    Now you should have quite a lot of updating policies in SEC. And from what you said they all (or many of them) point to the same location. What makes them update from different CIDs is the so-called Subscription (you'll find a tab for it in the policy). These in turn are managed in the Update Mangers view.
    It seems that
    1) clients update from a central web server (assuming the name does not resolve to different servers at the sites)
    2) the different CIDs are used to configure message relays
    The combination is not ideal, or better far from ideal.

    There's more than one way to skin a cat. For now, please take a look at the subscriptions and if the relays are in the correct SEC groups.

    Christian
    :17907
Children
No Data