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

Upgrading? Need advice? Let us know!

I want to ask you, our esteemed customers, what information Sophos could provide to make upgrading easier. This applies to upgrades from any version, but I'd love to be able to address people's concerns about the upgrade from Enterprise Console version 3 to version 4 especially.

We've got a great couple of upgrade guides, but what else can we do? What would you like to know more about?

Want to tell us how to do our jobs?? :smileyvery-happy: We'd love to hear to your suggestions, so let's talk!!

Thanks,

Lil

:1039


This thread was automatically locked due to age.
Parents
  • Hi Matt,

    What a great word -- cludgy!!

    Seriously though, our developers would love to get more info from you about your environment -- both to understand why the migration failed and also to understand why SUM's choking the server during an update -- this is not behaviour that we've seen in our tests and we're taking it very seriously.

    Obviously, you may be wary of publishing some of the details of your installation to the forums, so if you could switch on private messaging and mail me the following info, we can get someone from the SUM team to look at this:

    • Support ticket number for your failed migration, so we can check the details and try to improve the migration process.
    • How the SUM updating hierarchy is organised, e.g. one SUM or many SUMs in a hierarchy or many SUMs connecting to Sophos.
    • Which products are subscribed
    • How many CIDs are being distributed and to where (local machine or remote machine)
    • What was included in the quoted figure of 250Mb, e.g. only the CIDs (all of them? Which products?)
    • What is included in the quoted figure of 4.3Gb, e.g. only the SUM share, the remotely deployed CIDs, or the Sophos product set as a whole?
    • What’’’’s the machine spec? (This would be useful to know for performance reasons, as the post says it’’’’s at 100% CPU for 20 minutes, so we could combine that with info on the number of CIDs being pushed)

    If you need help switching on private messaging, please let me know!

    Best regards,

    Lil

    :1735
Reply
  • Hi Matt,

    What a great word -- cludgy!!

    Seriously though, our developers would love to get more info from you about your environment -- both to understand why the migration failed and also to understand why SUM's choking the server during an update -- this is not behaviour that we've seen in our tests and we're taking it very seriously.

    Obviously, you may be wary of publishing some of the details of your installation to the forums, so if you could switch on private messaging and mail me the following info, we can get someone from the SUM team to look at this:

    • Support ticket number for your failed migration, so we can check the details and try to improve the migration process.
    • How the SUM updating hierarchy is organised, e.g. one SUM or many SUMs in a hierarchy or many SUMs connecting to Sophos.
    • Which products are subscribed
    • How many CIDs are being distributed and to where (local machine or remote machine)
    • What was included in the quoted figure of 250Mb, e.g. only the CIDs (all of them? Which products?)
    • What is included in the quoted figure of 4.3Gb, e.g. only the SUM share, the remotely deployed CIDs, or the Sophos product set as a whole?
    • What’’’’s the machine spec? (This would be useful to know for performance reasons, as the post says it’’’’s at 100% CPU for 20 minutes, so we could combine that with info on the number of CIDs being pushed)

    If you need help switching on private messaging, please let me know!

    Best regards,

    Lil

    :1735
Children
No Data