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

    I'm a bit lost and not quite sure what the current state is.  It sounds promising that the child SUMs directories are populated.

    I would check that looking in:

    \\childsum\sophosupdate\CIDs\S000\SAVSCFXP\savxp\

    that the last .ide file is recent.  If so, and this SUM is downloading exclusively from the parent SUM, the parent must be downloading and populating the warehouse directory:

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

    It might be worth checking the parent SUMs CIDs:

    \\parentsum\sophosupdate\CIDs\S000\SAVSCFXP\savxp\

    to check the most recent .ide file is also current.

    If both of these turn out to be ok, then there isn't much wrong with the updating setup.

    I see there is then the logs of AutoUpdate, these show a successful check to a distribution point, I'm not sure what that has to do with SUM other than proving the distribution point that SUM has created that client is pointing to is ok?

    The link to the other page on the forum should help you get past the registry check as the file mentioned will contain the key that the CRT component is finding.

    Jak

    :7729
Reply
  • 0

    HI,

    I'm a bit lost and not quite sure what the current state is.  It sounds promising that the child SUMs directories are populated.

    I would check that looking in:

    \\childsum\sophosupdate\CIDs\S000\SAVSCFXP\savxp\

    that the last .ide file is recent.  If so, and this SUM is downloading exclusively from the parent SUM, the parent must be downloading and populating the warehouse directory:

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

    It might be worth checking the parent SUMs CIDs:

    \\parentsum\sophosupdate\CIDs\S000\SAVSCFXP\savxp\

    to check the most recent .ide file is also current.

    If both of these turn out to be ok, then there isn't much wrong with the updating setup.

    I see there is then the logs of AutoUpdate, these show a successful check to a distribution point, I'm not sure what that has to do with SUM other than proving the distribution point that SUM has created that client is pointing to is ok?

    The link to the other page on the forum should help you get past the registry check as the file mentioned will contain the key that the CRT component is finding.

    Jak

    :7729
Children
No Data
Cookie Information Banner