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

ConfigCID.exe changes

QC

Hello all

Last week I stumbled over the recent changes in ConfigCID.exe - got a "Failed to read signing key" error (meanwhile the article on ConfigCID.exe has been amended with information on this). This will affect you if

  • you have to configure a CID on a child SUM and
  • you can't access the share from the management server

There are perhaps more changes (to expect)

Just to let you know

Christian

:36855


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

    Hello JFC,

    this is - I assume - an endpoint attempting to update, isn't it? Is the WebCID configured as Primary or Secondary? You've probably noticed this because updating failed on the endpoint. Now I think the the actual failure - if updating indeed failed - is somewhere else. The SDDS mechanism (which searches for the catalogue) is for updating from a Sophos Warehouse and tried first (regardless of the path configured) if the Last Update Mechanism for the location is SDDS or Unknown. It is expected to fail when not updating from Sophos (or a Sophos Warehouse) where it indeed would find the catalogue. AU the tries the CID mechanism which is the appropriate method for a WebCID (which contains neither the catalogue nor a catalogue folder). Looks like this failed as well - there should be another error in the log.

    Christian

    :39519
Reply
  • 0

    Hello JFC,

    this is - I assume - an endpoint attempting to update, isn't it? Is the WebCID configured as Primary or Secondary? You've probably noticed this because updating failed on the endpoint. Now I think the the actual failure - if updating indeed failed - is somewhere else. The SDDS mechanism (which searches for the catalogue) is for updating from a Sophos Warehouse and tried first (regardless of the path configured) if the Last Update Mechanism for the location is SDDS or Unknown. It is expected to fail when not updating from Sophos (or a Sophos Warehouse) where it indeed would find the catalogue. AU the tries the CID mechanism which is the appropriate method for a WebCID (which contains neither the catalogue nor a catalogue folder). Looks like this failed as well - there should be another error in the log.

    Christian

    :39519
Children
No Data