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

CID Server support different OS's

maeglin
I would like to create a CID server on Linux that provides updates to Linux, Unix and Windows clients. The clients do not have access to the Internet. The CID server shares a directory with the clients and can retrieve its own updates. The "mkinstpkg" tool creates an OS-specific installer which will not work on the other systems. Are the alternate OS files even on the CID server? If this will not work, are there instructions for downloading the update data directly so the CID server can store the update files for the other operating systems? Sincerely
:56421


This thread was automatically locked due to age.
Parents
  • 0

    Hello maeglin,

    any issues with haveing the SUM talk through a proxy

    so you intend to let one computer connect to the "outside"? Please note that there is not standalone SUM, you'd need to install the management server (please see here for the supported platforms).

    WPAD

    Should have told you what applies to Endpoint (as opposed to Cloud) and what does not. In Endpoint you can configure a proxy (individually for the Primary and Secondary  location) in the updating policy (similarly for a SUM's Source). Guess the Endpoint product (at least its AutoUpdate component) doesn't use WinHTTP.

    mkinstpkg ... proxy server

    Sorry, no experience, can't say if mkinstpkg will ask for an optional proxy (guess it does and it's easy to find out). Anyway to clarify, the PrimaryUpdateSourcePath (or whatever mkinstpkg calls it) must point to a valid CID (either deployed by SEC or a Linux host) or Sophos. You should be able to specify a proxy (if not with mkinstpkg) with savconfig (or perhaps savsetup). Please note that updates from Sophos have a format and structure which are different from those in a CID.

    Christian

    :56462
Reply
  • 0

    Hello maeglin,

    any issues with haveing the SUM talk through a proxy

    so you intend to let one computer connect to the "outside"? Please note that there is not standalone SUM, you'd need to install the management server (please see here for the supported platforms).

    WPAD

    Should have told you what applies to Endpoint (as opposed to Cloud) and what does not. In Endpoint you can configure a proxy (individually for the Primary and Secondary  location) in the updating policy (similarly for a SUM's Source). Guess the Endpoint product (at least its AutoUpdate component) doesn't use WinHTTP.

    mkinstpkg ... proxy server

    Sorry, no experience, can't say if mkinstpkg will ask for an optional proxy (guess it does and it's easy to find out). Anyway to clarify, the PrimaryUpdateSourcePath (or whatever mkinstpkg calls it) must point to a valid CID (either deployed by SEC or a Linux host) or Sophos. You should be able to specify a proxy (if not with mkinstpkg) with savconfig (or perhaps savsetup). Please note that updates from Sophos have a format and structure which are different from those in a CID.

    Christian

    :56462
Children
No Data