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

Standalone installation confusion in EC4

Hi,

We already have a standalone installation program, that was created with EC3, but it is require a bit to update after installation, so would like to do one for EC4.  I've been following the updated KB article (http://www.sophos.com/support/knowledgebase/article/67372.html), but I'm lost on step #2!

"In Sophos Update Manager, create a new Software Distribution to create an additional share ..."

I can't find anywhere that mentions creating a "Software Distribution" in the Update Manager.  Am I missing something??  I can create a subscription, but that doesn't appear to be what I'm after..

Can anyone shed some light on the issue?

Thanks in advance,

Ryan G

:1770


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

    "In Sophos Update Manager, create a new Software Distribution to create an additional share ..."

    The wording is somewhat unfortunate. You have to create a new share on the server (or somewhere else), then you select this share in Configure update manager -> Distribution tab. It is then populated with the selected subscription.

    So what's the difference between this approach and kevgo's?

    Disadvantage:

    * an additional distribution adds load to the server during updates (see the current discussions)

    Advantage:

    * you don't need the copy steps

    * you have to customize it only once. After you have added the the xml-files and run configcid.exe the changes are honoured by SUM and whenever you need to create a new package you just run the build process

    But whatever worked with SEC3/SESC8/SAV7 should also work with the newer versions (except for the changed CID locations).

    Christian

    :1777
Reply
  • Hello Ryan,

    "In Sophos Update Manager, create a new Software Distribution to create an additional share ..."

    The wording is somewhat unfortunate. You have to create a new share on the server (or somewhere else), then you select this share in Configure update manager -> Distribution tab. It is then populated with the selected subscription.

    So what's the difference between this approach and kevgo's?

    Disadvantage:

    * an additional distribution adds load to the server during updates (see the current discussions)

    Advantage:

    * you don't need the copy steps

    * you have to customize it only once. After you have added the the xml-files and run configcid.exe the changes are honoured by SUM and whenever you need to create a new package you just run the build process

    But whatever worked with SEC3/SESC8/SAV7 should also work with the newer versions (except for the changed CID locations).

    Christian

    :1777
Children
No Data