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 to SUM

Hello all,

I'm a bit confused on the upgrading to SUM. I am currently running Enterprise Console Ver. 4.0 with EM Library Ver. 1.3.3 (im assuming that my EM Library is the one that is expiring in March). If so, do I just need to upgrade to Console 4.5 and this will be taking care of? Any help will be greatly appreciated. 

:8877


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

    Section 6 in:

    http://www.sophos.com/sophos/docs/eng/sesc_95_augeng.pdf

    should help you.

    If you aleady running SEC 4 you will have SUM installed at least on the Sophos mangement server it just may not be configured yet but if you switch to the SUM list in Enterprise Console you should see it and can start.

    You don't mention if you have multiple EMLibrary installs to upgrade to SUM installs or if you just have the one on the management server but if you do have more than 1 EMlibrary, to upgrade, on the EMlibrary machine you can just run the setup.exe from the SUM installer share on the management server as mentioned in chapter 6.3 of the above PDF.  Once the machine reports back in as a SUM you will see it in the update managers list in SEC.

    If you need to automate the install of many SUMS:

    http://www.sophos.com/support/knowledgebase/article/61474.html

    might be worth a look also.

    Either way the prinical of SUM is the same as EMLibrary it's just more intergrated into SEC.  The communcaiton with SUM uses RMS and you don't need a separate mangament console.  You set up a source, e.g. Sophos, define what subscriptions you want (a subscription can be thought of as a collection of versions of the various AV products for the different platforms).

    You then assign this subscription to the SUMs that need to maintain it.  The term CID or Central Installation Directory has been changed to Distribution Point but essentially they are the same collection of files.

    In the new updating polcies you only have to specify the root of the share (should be pre-populated in the drop down), and then you chose the subscription (verison of the software) the share has to offer in the subscription tab of the policy, the new updating policy then essentially adds the share path to the subscription to form the full updating path.  That's about it.  

    Regards,

    Jak

    :8883
Reply
  • HI,

    Section 6 in:

    http://www.sophos.com/sophos/docs/eng/sesc_95_augeng.pdf

    should help you.

    If you aleady running SEC 4 you will have SUM installed at least on the Sophos mangement server it just may not be configured yet but if you switch to the SUM list in Enterprise Console you should see it and can start.

    You don't mention if you have multiple EMLibrary installs to upgrade to SUM installs or if you just have the one on the management server but if you do have more than 1 EMlibrary, to upgrade, on the EMlibrary machine you can just run the setup.exe from the SUM installer share on the management server as mentioned in chapter 6.3 of the above PDF.  Once the machine reports back in as a SUM you will see it in the update managers list in SEC.

    If you need to automate the install of many SUMS:

    http://www.sophos.com/support/knowledgebase/article/61474.html

    might be worth a look also.

    Either way the prinical of SUM is the same as EMLibrary it's just more intergrated into SEC.  The communcaiton with SUM uses RMS and you don't need a separate mangament console.  You set up a source, e.g. Sophos, define what subscriptions you want (a subscription can be thought of as a collection of versions of the various AV products for the different platforms).

    You then assign this subscription to the SUMs that need to maintain it.  The term CID or Central Installation Directory has been changed to Distribution Point but essentially they are the same collection of files.

    In the new updating polcies you only have to specify the root of the share (should be pre-populated in the drop down), and then you chose the subscription (verison of the software) the share has to offer in the subscription tab of the policy, the new updating policy then essentially adds the share path to the subscription to form the full updating path.  That's about it.  

    Regards,

    Jak

    :8883
Children
No Data