According to this post and comments made in it, these rollouts should be complete and devices should be updated fully to the new architecture, however my entire fleet still hasn't updated. The new agent seems to be rolled out but devices still have the Sophos Anti-Virus component. Can we get a status update on this or a method to force it. I get tired of having to continually monitor if these changes have rolled out for months on end.
It looks like it's finally done it. Not sure of why there was a delay but all good now.
Ah, OK, I know that the client needs a couple of "Update now" after the reboot to switch from SDDS2 to using SDDS3 and remove the orphaned components, in this case SAV.
It also can take a long time to download if under global settings in Central you have the default bandwidth set.
I suspect if you open C:\programdata\sophos\autoupdate\logs\sophsupdate.log.
2022-03-25T14:59:16.484Z [24064:17692] I Performing standard update using SDDS32022-03-25T14:59:16.485Z [24064:17692] I Limiting bandwidth to 256 Kbps
Did it take a long time to download all the files over SDDS3? The timestamps of the lines should give it away.
Yes, it looks like it took a good while to download and we are set to the default bandwidth usage.
Thanks for all the help and insight.
Great. Might be worth increasing the default :) Thanks.
We are using Controlled Updates for endpoints and servers and this update is still not showing up on our Test Computers approved for the last version released 6/16/2022.Is there anything we can do to make this available to our test computers without adding them to the EAP?
I suggest checking the following release notes page to verify what version your OS' should have installed. You can find the correct information by using the following options through the drop-down menus on the release notes page.- Endpoint > Sophos Core Agent > All versions
The 2022.1.0.78 release was put on hold, so your devices should be on 2.20.13 for now. The 2022.1.1.3 release, which replaces 2022.1.0.78, will begin on the 21st and will finish over the course of a few weeks. I suggest checking back in periodically after the 21st.
Thanks for the info, I will look out for the 2022.1.1.3 update.Our Win10 x64 Test computers are still running 2.20.11 which was released in Feb. 2022:
Note, the only mention of SDDS3 in the AU/MCS logs is from McsClient.log: "sdds3.ready":false
Qoosh What is the status of this rollout? We were investigating an InterceptX resource issue and on further investigation, we have found that over half of our MSP sites have still not had the new architecture rolled out! I'm referring to workstations not servers (which from another post, https://community.sophos.com/intercept-x-endpoint/f/discussions/135365/how-to-get-the-latest-intercept-x-version-for-servers-manually, appears to be put on hold).
What is the delay with this? Is it an issue with the new architecture so you have delayed deployment, or is the deployment rollout just taking a very long time?
Due to the following issue, the release of Core Agent 2022.1.1.3 was put on hold. - Sophos Endpoint: Unable to connect to Wi-Fi networks after Core Agent 2022.1.1.3 update
This release will be superceded by Core Agent 2022.2.1. We do not yet have definitive release dates for the new version, though we expect the rollout to begin on the 20th of July barring any delays or issues encountered.
We finally got the Next Gen agent available through Controlled Updates, with 2022.2.1.9 rolling out to our test systems now.