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

Setting up Enterprise Console that pulls updates from another Enterprise Console server

bmoorman

I'm trying to determine if it is possible to setup an "isolated" Enterprise Console for an environment that has limited Internet access to pull updates from a second Enterprise Console server across a Firewall.  If it is possible, what steps do I need to do on the "isolated" Enterprise Console so it looks to the other server for updates from it's update manager?

:52803


This thread was automatically locked due to age.
  • 0

    Hello bmoorman,

    do I understand correctly that you want a full management server which manages its own endpoints and you don't want it to download from the Sophos CDN either directly or via a proxy but rather from another SEC? 

    You can use another SEC or SUM as source provided that

    • the SEC versions are the same
    • the source SEC/SUM has subscribed to the packages the isolated SEC needs
    • the source's SophosUpdate share is accessible via HTTP (i.e. published by a web server) 

    UNC would also be possible but given the setup probably not the first choice anyway. Publishing is simple with IIS, you'd just have to make sure that IIS serves the .xml extension as text and .dat as binary (I've added an application/sophos-x MIME type for it).

    On the isolated server you configure http://mainserver[/path] as source, where mainserver can be a simple name, FQDN or IP; the optional /path is the path to SophosUpdate - SUM expects to find the Warehouse folder (not its contents) there.

    Christian 

    :52815