Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 5 replies
  • Subscribers 1 subscriber
  • Views 14337 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

Endpoints not getting correct version from SEC, or updating

along2285

Let me first thank you for your help ahead of time. I have just taken over the task of making changes to our AV. This is where I stand and I can provide any information necessary to further assist. We had a previous version of enterprise console(5.0 I think) running that managed Sophos on 20+ servers. The orginization decided to move all endpoint to a Sophos solution(350+). The console was updated to 5.3 and the Download Security Software Wizard has been run since it is missing from my menu. 

My issues are that version 10.0 is being pushed to the endpoints if I install it through the SEC, and once I do it will not update. The subscription was still set to the previous version we used on the server, so I made a subscription change so that it should be getting the new version. I also input the new password associated with the license and username. 

The following is information that I feel might be of help, if you need anything more specific let me know and I will post back ASAP;

Primary update server showing on endpoint ~ \\windowsmedia\sophosupdate\CIDs\s002\SAVSCFXP\
primary server configured in update policy ~ \\windowsmedia\sophosupdate\

updating policy username ~ corsp\SophosUpdateMgr ~ which is not in my active directory users
Same username set on the endpoint

update manager install location \\WindowsMedia\SUMInstallSet

Cheers

Andy

:57169


This thread was automatically locked due to age.
  • 0

    Hello Andy,

    you're not really familiar with SEC, are you?

    CIDs\s002

    this suggests that you have more than one subscription. Let's start with the Update managers view. To the left is the Software Subscriptions pane. There's at least one subscription in addition to Recommended. Check the subscribed versions (View/Edit Subscription -> select the applicable row -> check the Version column or click Details...).

    Primary update server [...] update policy

    The Primary/Secondary Address contains the path to the share (or its equivalent for HTTP). For the actual path on the endpoint \CIDs\Snnn\productfolder is appended. CIDs is a constant, productfolder is SAVSCFXP for Windows, ESCOSX for Mac OS X. Snnn corresponds to a specific subscription (e.g. S000 to Recommended). You can see the correlation by selecting View (in the menubar at the top) -> Bootstrap locations.... In the Updating Policy there's a (surprise!) Subscription tab - there you select the subscription (and implicitly the Snnn folder).

    So - does S002 (according to View Bootstrap) indeed contain the desired version?

    version 10.0 is being pushed

    Nothing is pushed, the endpoints connect to the update location and download whatever version SEC (SUM) has put there. The question is whether the endpoints can update (i.e. successfully connect to and download from the CID, regardless of the version) or not - in the latter case the icon and the log would show that updating failed. 

    updating policy username

    can be a domain or a server-local account - are the names WindowsMedia (for the server hosting the share) and corsp (the host/domain for the updating account) pseudonyms?

    Christian

    :57173
  • 0

    You would be correct, I am not familiar with this console. It was managed by someone who is no longer with the organization. I had created a new subscription prior to posting. The subscription was poingting to the correct location for version 10.3, but the update policy turned out to be my issue. I input the full path to the install location and everything seems to be working as it should now. All test endpoints are running the correct version and updating.

    Thank you very much for your assistance QC, the problem was right in front of me and I simply overlooked it. 

    Cheers

    Andy

    :57187
  • 0

    I have another issue now and I cannot find anything on this. The actual location my files reside is

    \\windowsmedia\sophosupdate\CIDs\s002\SAVSCFXP\

    My machines are now looking to install/update from the following path;

    \\windowsmedia\sophosupdate\CIDs\s002\SAVSCFXP\CIDs\s002\SAVSCFXP\

    Somehow it is adding a second string of CIDs\s002\SAVSCFXP\ to the path where the install files are located. My bootstrap location is correct, as is the path in my updating policy. The only place that I can find that the path does not show 

    \\windowsmedia\sophosupdate\CIDs\s002\SAVSCFXP\  is the "Update to" portion of the distribution tab in confugureing the update manager. The path specified there is \\windowsmedia\sophosupdate. 

    Thanks again for your assistance.

    Cheers

    Andy

    :57202
  • 0

    In the updating policy, you only specify the share in the Primary update path tab (this should be in the drop down list), e.g.

    \\windowsmedia\sophosupdate\

    The subscrition part, i.e. CIDs\s002\SAVSCFXP\ is appended.  You can check the subscription tab in the updating policy to ensure that is correct.

    Regards,

    Jak

    :57205
  • 0

    Thank you very much jak. 

    Cheers

    Andy

    :57216
Cookie Information Banner