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 errors after subscription change

Prior to Sophos Anti-virus 10.3 I had four software subscriptions.  Subscriptions and bootstraps were as follows:

Recommended  -  S000 (v9.7)

Endpoint v10 - S002 (v10.0)

Endpoint v10.2 - S003 (v10.2)

The automatic update from 10.2 to 10.3 display "Software not available" on the parent SUM as well as three child SUMs.  Sophos support told me to acknowledge alerts and run an update on parent SUM.

Next I was adivsed to create a new subscription,  Recommended1 - S005 (v10.3), and remove the older subscriptions.  I made all of the necessary changes under the update managers and to the updating policies.  Things seemed to be ok at this point.

A few days later I decided to put the software subsciption back to only one which was Recommended.  So I changed the version on Recommended subscription to Recommended (10.3) from 9.7 Extended Maintenance Recommended and I deleted the Recommended1 subscription.  I made all of the necessary changes to the parent SUM, child SUMs, and updating policies.

Once I did that almost 70% of our endpoints were displaying update errors mainly RMSNT and the bootstrap location pointed back to S000 (v9.7).  I assume all of the updates/binaries for 10.3 replaced all of the old stuff.

Sent SDU logs from parent SUM and some endpoints to Sophos support.  Support has been great up to this particular incident.

I took it upon myself to add the Recommended1 software subscription which created S008 (v10.3) bootstrap location, made necessary changes to parent and child SUMs and watched the error count decline.

I'm still seeing the following errors on clients.

ERROR: Could not find a source for updated packages (00000071)

Failed to install RMSNT: Package authentication failed (00000067)

Failed to install SAVXP: A previous version could not be uninstalled (00000067)

Failed to install Sophos AutoUpdate: The MSI has failed (00000067)

Updating failed because no update source has been specified (0000006e)

Download of Sophos AutoUpdate failed from server sophosupdates/CIDs/S008/SAVSCFXP/ (0000006b)

Download of SAVXP failed from server sophosupdates/CIDs/S003/SAVSCFXP/ (0000006b)

Download of RMSNT failed from server /CIDs/S008/SAVSCFXP/ (0000006b)

Download of SAVXP failed from server Sophos (0000006b)

Failed to install Sophos AutoUpdate: Error code 80070001

:44833


This thread was automatically locked due to age.
Parents
  • Thank you for the reply and explanation. I checked the mrinit.conf on all SUMs.  Location roaming is not enabled.

    Any additional SUM will use the same mrinit.conf

    ParentSUM

    MRParentAddress"="x.x.x.96

    ParentRouterAddress"="x.x.x.96

    ChildSUM1 (for academic endpoints)

    MRParentAddress"="x.x.x.96

    ParentRouterAddress"="x.x.x.116

    ChildSUM2 (for staff endpoints)

    MRParentAddress"="x.x.x.96

    ParentRouterAddress"="x.x.x.117

    WebSUM (for home use clients - not managed)

    Uses sameas parentSUM

    ParentSUM Distribution details

    Update to: \\ParentSUM\SophosUpdate

    ChildSUM1 Distribution details

    Update to: \\ChildSUM1\SophosUpdate

    ChildSUM2 Distribution details

    Update to: \\ChildSUM2\SophosUpdate

    WebSUM Distribution details

    Update to: \\WebSUM\SophosUpdate

    So if I am understanding all of this correctly, a custom mrinit.conf was setup, on our childSUMs, from initial deployment.

    I have never checked the mrinit.conf on any workstation until now so I'm not sure what the correct address should be for ParentRouterAddress.  All of the client installer packages I have created, that are used have originated from the ParentSUM\CID\SXXX.  Each package has

    setup.exe -crt R -mng yes -updp childsum1/.../SAVSCFXP  -s -ni (installed on academic pcs)

    setup.exe -crt R -mng yes -updp childsum2/.../SAVSCFXP  -s -ni (installed on staff pcs)

    setup.exe -crt R -mng no -updp websum/.../SAVSCFXP  -s -ni (installed on home pcs)

    :44913
Reply
  • Thank you for the reply and explanation. I checked the mrinit.conf on all SUMs.  Location roaming is not enabled.

    Any additional SUM will use the same mrinit.conf

    ParentSUM

    MRParentAddress"="x.x.x.96

    ParentRouterAddress"="x.x.x.96

    ChildSUM1 (for academic endpoints)

    MRParentAddress"="x.x.x.96

    ParentRouterAddress"="x.x.x.116

    ChildSUM2 (for staff endpoints)

    MRParentAddress"="x.x.x.96

    ParentRouterAddress"="x.x.x.117

    WebSUM (for home use clients - not managed)

    Uses sameas parentSUM

    ParentSUM Distribution details

    Update to: \\ParentSUM\SophosUpdate

    ChildSUM1 Distribution details

    Update to: \\ChildSUM1\SophosUpdate

    ChildSUM2 Distribution details

    Update to: \\ChildSUM2\SophosUpdate

    WebSUM Distribution details

    Update to: \\WebSUM\SophosUpdate

    So if I am understanding all of this correctly, a custom mrinit.conf was setup, on our childSUMs, from initial deployment.

    I have never checked the mrinit.conf on any workstation until now so I'm not sure what the correct address should be for ParentRouterAddress.  All of the client installer packages I have created, that are used have originated from the ParentSUM\CID\SXXX.  Each package has

    setup.exe -crt R -mng yes -updp childsum1/.../SAVSCFXP  -s -ni (installed on academic pcs)

    setup.exe -crt R -mng yes -updp childsum2/.../SAVSCFXP  -s -ni (installed on staff pcs)

    setup.exe -crt R -mng no -updp websum/.../SAVSCFXP  -s -ni (installed on home pcs)

    :44913
Children
No Data