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

Pushing Libraries to Linux

imc

Hello,

I'm working on a replacement server for EM.  I've got it all configured.  I still have my old server with Enterprise Console 3.x chugging along.  In that version, I was able to create a CID to push the updates towards a linux server which I then configured my clients to update against, allowing mobile users to be able to get updates when not on site.  Is this still possible with the updated version?

:2027


This thread was automatically locked due to age.
  • 0

    I figured out that it's a distribution source that needs to be set up.

    Now I'm stuck on the update policy piece because if I install from a remote location, the default updating policy gets completely ignored. 

    George is getting mad!

    :2031
  • 0

    Hi,

    I have a similar setup here with users that have no access to the sophos RMS and therefore I can't get a remote policy update. I tackle this by creating a dummy updating group in my policy specifically for this type of user, setting up my updaing locations e.g. a webcid and then I integrate the SAUCONF.XML into the install package which you install from.

    Must admit that I haven't done this for v.9 EPS but use it all the time on v.7 I'm fairly sure it'll be exactly the same though. There's a tool to extrat SAUConf.XML from a group and another to integrate it into a CID (which you can then rar up and create a self-extracting file that kicks off setup so making it easy to deploy), the names of the two programs escape me at the moment but sure one of the Sophos staff can jump in.

    The advantage of this method is that you can then block anyone modifying the update sources themselves as the update locations get greyed out and non editable (unless you know the files to tweak).

    Matt

    :2033
  • 0

    No Sophos staff needed: Export with exportconfig.exe (in the Enterprise Console folder) and configure the CID with - you guess already - configcid.exe (in the Update Manager folder).  Up to 3.1 you entered the path to the specific CID (e.g. \\server\InterChk\SAVSCFXP) in the updating policy while from 4.0 on you only select a "base path" (\\server\SophosUpdate) and SEC appends the path for the subscription and product   (e.g. \CIDs\S000\SAVSCFXP). SUM creates this path when it distributes to a share. 

    But some additional steps are probably required and it'd be best if you'd tell us the details of your current setup.

    Christian

    :2036
Unfiltered HTML