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

Next Gen Architecture Rollout

NetGuy

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.



This thread was automatically locked due to age.
Parents
  • 0

    The next-gen endpoint architecture has been rolled out to 10% of customers and will gradually be released to larger groups. If you're looking to test out the new features sooner, it's possible to enroll a few devices in the EAP Program for Endpoints, likewise for Server OS'. 

    If you have customers using MSP Flex licensing, the EAP Programs may not be available. In this situation, you can open a case with our support team to request that the customer/you be moved into the appropriate release group to receive the updates right away. 

    Kushal Lakhan
    Team Lead, Global Community Support
    Connect with Sophos Support, get alerted, and be informed.
    If a post solves your question, please use the "Verify Answer" button.
    The New Home of Sophos Support Videos!  - Visit Sophos Techvids
  • 0 in reply to Qoosh

    I'm note seeing the next gen architecture on any of our devices either yet.  I've added my own device to the EAP but that doesn't seem to force the update either.

  • 0 in reply to colly72

    Have you rebooted since the client was added to the EAP?

    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Sophos\AutoUpdate\UpdateStatus

    sddsVersion should be 3

    and

    sdds3Synced should be 1.

    Is the SAVService.exe process still exists, which is part of the SAV component, then it hasn't migrated as the SAV component should be removed as an orphaned product. I believe this happens after reboot on the next update once the client is using SDDS3 rather than SDDS2.

Reply
  • 0 in reply to colly72

    Have you rebooted since the client was added to the EAP?

    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Sophos\AutoUpdate\UpdateStatus

    sddsVersion should be 3

    and

    sdds3Synced should be 1.

    Is the SAVService.exe process still exists, which is part of the SAV component, then it hasn't migrated as the SAV component should be removed as an orphaned product. I believe this happens after reboot on the next update once the client is using SDDS3 rather than SDDS2.

Children
Unfiltered HTML