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

steps for setup child server

yh

Hi,

We just setup Sophos Enterprise Console 4.5(replace symantec) The structure==> one primary server as parent server  updated from Sophos website. 4 Site servers as child server updated from parent server.

Anyone knows the detail steps to setup child server? Because after copy SUMInstallSet folder from parent server to child server, run setup.exe, configure this child server (source from parent, subscriptions as recommended, distribution as update to share \\child server\Sophosupdate). Got the error  'threat detection data update failed" and last updaed "never". What's wrong? Can anyone provide the detail steps with screen shot.

Thanks

:7641


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

    Hi,

    It sounds like most of the setup is working: If you ran setup to install the child SUM, shortly after it appeared in SEC, you configured it and the machine is compliant with the SUM policy (Configuration column shows as matches in SEC), all of the messaging system is functioning which is a large part of the system.

    I assume the configuration of the child is with regards to the "Sources" tab is:

    "\\ServerName\SophosUpdate"

    and at the child SUM machine, this same address resolves ok?  It doesn't need to be full qualified for example?

    On the child, is there anything in?

    \Documents and Settings\All Users\Application Data\Sophos\Update Manager\working\?

    or:

    \Programdata\Sophos\Update Manager\working\?

    I assume "Working" exists on the machine?

    Also does:

    \Documents and Settings\All Users\Application Data\Sophos\Update Manager\Update Manager\

    or:

    \Programdata\Sophos\Update Manager\Update Manager\

    Contain a CIDs and Warehouse directory and are they populated?

    Other than that to get a feel for what has happened, looking in the log files is worth a glance.There are 2 types of logs:

    1. SUMLog[timestamp].log
    2. SUMTrace[timestamp].log

    as found in:

    \Documents and Settings\All Users\Application Data\Sophos\Update Manager\Logs\

    or

    \ProgramData\Sophos\Update Manager\Logs\

    In the SUM Program Files directory there is a logviewer.exe, this essentially reads in the "SUMLog" files and can apply a few filters on it and for more indepth analysis the "Trace" file can be looked at.

    As a third way of seeing what SUM is doing you can also connect to the SUM to see what's going on in real-time as per this post:

    This logs a similar amount as the trace log.

    Regards,

    Jak

    :7645
Reply
  • 0

    Hi,

    It sounds like most of the setup is working: If you ran setup to install the child SUM, shortly after it appeared in SEC, you configured it and the machine is compliant with the SUM policy (Configuration column shows as matches in SEC), all of the messaging system is functioning which is a large part of the system.

    I assume the configuration of the child is with regards to the "Sources" tab is:

    "\\ServerName\SophosUpdate"

    and at the child SUM machine, this same address resolves ok?  It doesn't need to be full qualified for example?

    On the child, is there anything in?

    \Documents and Settings\All Users\Application Data\Sophos\Update Manager\working\?

    or:

    \Programdata\Sophos\Update Manager\working\?

    I assume "Working" exists on the machine?

    Also does:

    \Documents and Settings\All Users\Application Data\Sophos\Update Manager\Update Manager\

    or:

    \Programdata\Sophos\Update Manager\Update Manager\

    Contain a CIDs and Warehouse directory and are they populated?

    Other than that to get a feel for what has happened, looking in the log files is worth a glance.There are 2 types of logs:

    1. SUMLog[timestamp].log
    2. SUMTrace[timestamp].log

    as found in:

    \Documents and Settings\All Users\Application Data\Sophos\Update Manager\Logs\

    or

    \ProgramData\Sophos\Update Manager\Logs\

    In the SUM Program Files directory there is a logviewer.exe, this essentially reads in the "SUMLog" files and can apply a few filters on it and for more indepth analysis the "Trace" file can be looked at.

    As a third way of seeing what SUM is doing you can also connect to the SUM to see what's going on in real-time as per this post:

    This logs a similar amount as the trace log.

    Regards,

    Jak

    :7645
Children
No Data