Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 1 subscriber
  • Views 3430 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 Support for non Windows CIDs

eniac

dear community

we are migrating our existing SEC installation to a new Server with a clean database.

(new hostname, new ip / merging two enterprise console installations to one)

with the information on how to create message relay computers and a good forum

(thanks QC) the first test clients successfully replaced the local mrinit.conf and

reported to the new database.

the question is, can this be done for the ESCOSX CID too?

if i run configcid.exe with the path to ESCOSX i just get:

root=[PATH]\CIDs\S000\ESCOSX
dir =
prod={8baa10c1-3844-465e-919c-d778a5407708}
elem:     135, 0xB2C93604, \root.upd
Read catalog file cidsync.upd
Failed to open catalog [PATH]\CIDs\S000\ESCOSX\Sophos Anti-Virus.mpkg\cidsync.upd

or is there any other way to update the local mrinit.conf for macos x?

kind regards

remo

:3408


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

    hi RL

    thanks a lot for your reply - very "in detail" description :)

    the problem i would like to circumvent is to automate the changes to mrinit.conf

    only with the sophos autoupdate feature. here is the process that works for windows:

    normally mrinit.conf is created on install and is never changed.

    to distribute a modification you can:

    1.) put mrinit.conf in rms subdirectory

    2.) run configcid.exe to include the file in the autoupdate process

    3.) on next update the new mrinit.conf is downloaded and installed on every client

    4.) client contacts new sec and is "migrated" to the new database

    is something similiar also possible with macos x? (without the need of running

    a script or install on every client by hand)

    kind regards

    remo

    :3423
Reply
  • 0

    hi RL

    thanks a lot for your reply - very "in detail" description :)

    the problem i would like to circumvent is to automate the changes to mrinit.conf

    only with the sophos autoupdate feature. here is the process that works for windows:

    normally mrinit.conf is created on install and is never changed.

    to distribute a modification you can:

    1.) put mrinit.conf in rms subdirectory

    2.) run configcid.exe to include the file in the autoupdate process

    3.) on next update the new mrinit.conf is downloaded and installed on every client

    4.) client contacts new sec and is "migrated" to the new database

    is something similiar also possible with macos x? (without the need of running

    a script or install on every client by hand)

    kind regards

    remo

    :3423
Children
No Data