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

WebCID using Enterprise Console 4.

KSO

I'm trying to create a WebCID to allow standalone machines to access the Sophos Updates on an Internal Webserver.

Before the upgrade to Enterprise Console 4, http://192.168.11.30/sophos works.

With the new version, what do I make available to the IIS?

The "Sophos Update Manager Warehouse Share" is at: C:\Documents and Settings\All Users\Application Data\Sophos\Update manager\Update Manager" (default location)

Do I publish that location to /sophos on IIS, or to Warehouse or CIDs directory?

Thanks

:292


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

    Before SUM you had \\server\InterChk which contained the individual CIDs - was http://192.168.11.30/sophos your update location or was something appended (eg SAVSCFXP)? You will now find SAVSCFXP under ,,,\Update Manager\Update\CIDs\Snnn.

    If you configure updates manually on the machines you can publish \Snnn. If you are using policies from SEC you have to publish \Update - SEC appends the path to the subscription.

    Christian

    :300
Reply
  • 0

    Before SUM you had \\server\InterChk which contained the individual CIDs - was http://192.168.11.30/sophos your update location or was something appended (eg SAVSCFXP)? You will now find SAVSCFXP under ,,,\Update Manager\Update\CIDs\Snnn.

    If you configure updates manually on the machines you can publish \Snnn. If you are using policies from SEC you have to publish \Update - SEC appends the path to the subscription.

    Christian

    :300
Children
No Data
Unfiltered HTML