Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 35 replies
  • Subscribers 1 subscriber
  • Views 30449 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

Upgrading? Need advice? Let us know!

lilhavoc

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
  • 0

    You're welcome, Matt

    Didn't see the high CPU usage on my server. SophosUpdateMgr.exe maxes out one core (so it's 25% here) for about one minute but between those it's quiet. Ah - I see the discussion has resumed.

    Meanwhile some mulling over Remote CID vs. Child SUM. Maybe John could comment on this. Looks like initial deployment of a CID might "never" complete when there are frequent (i.e. the interval between errors is shorter than the time needed to deploy the whole subscription) errors in the connection. The distributing SUM seems to start all over again after an interruption. The child SUM resumed fetching data to the warehouse - at least my test suggests it.

    As for ADSL - isn't upstream even slower than downstream (guess that's why there's an A in ADSL)? And in distributing - what does SUM have to read from the CID when updating? Would this affect performance?

    Or course if the remote server's CPU is below spec you are caught between a rock and a hard place.

    Just wondering, Matt, (but perhaps you do not want to disclose this information) how the remote offices are managed over a link like this (I don't say it's slow, I remember when we celebrated the upgrade of our BITNET link from 4.800 to 9.600 baud)? How did you get Sophos on the machines in the first place? Guess Sophos wouldn't recommend synching the CID by some other less expensive means (are there even?).

    Christian     

    :1834
Reply
  • 0

    You're welcome, Matt

    Didn't see the high CPU usage on my server. SophosUpdateMgr.exe maxes out one core (so it's 25% here) for about one minute but between those it's quiet. Ah - I see the discussion has resumed.

    Meanwhile some mulling over Remote CID vs. Child SUM. Maybe John could comment on this. Looks like initial deployment of a CID might "never" complete when there are frequent (i.e. the interval between errors is shorter than the time needed to deploy the whole subscription) errors in the connection. The distributing SUM seems to start all over again after an interruption. The child SUM resumed fetching data to the warehouse - at least my test suggests it.

    As for ADSL - isn't upstream even slower than downstream (guess that's why there's an A in ADSL)? And in distributing - what does SUM have to read from the CID when updating? Would this affect performance?

    Or course if the remote server's CPU is below spec you are caught between a rock and a hard place.

    Just wondering, Matt, (but perhaps you do not want to disclose this information) how the remote offices are managed over a link like this (I don't say it's slow, I remember when we celebrated the upgrade of our BITNET link from 4.800 to 9.600 baud)? How did you get Sophos on the machines in the first place? Guess Sophos wouldn't recommend synching the CID by some other less expensive means (are there even?).

    Christian     

    :1834
Children
No Data
Unfiltered HTML