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

    Hello remo,

    I had no troubles "preconfiguring" the ESCOSX CIDs for an initial install using a rather simple approach outlined in the thread - no special tools required and it works for us.

    And while I have been able to run configcid.exe on a Mac CID (simply copying the "missing" cidsync.upd from the root directory, it then says there's nothing to do for mrinit.custom which one can create and then it says Adding entry) it doesn't re-initialize the RMS component as on Windows.

    On the other hand some mechanism for updating the RMS component between releases obviously exists. In the light of  I think it's be a good idea to improve the manageability of Macs (and probably Linux as well) - especially the ability of "moving around" the clients (or replacing/"splitting"/"merging" the servers).

    Oh, and thanks for the feedback

    Christian

    :3424
Reply
  • 0

    Hello remo,

    I had no troubles "preconfiguring" the ESCOSX CIDs for an initial install using a rather simple approach outlined in the thread - no special tools required and it works for us.

    And while I have been able to run configcid.exe on a Mac CID (simply copying the "missing" cidsync.upd from the root directory, it then says there's nothing to do for mrinit.custom which one can create and then it says Adding entry) it doesn't re-initialize the RMS component as on Windows.

    On the other hand some mechanism for updating the RMS component between releases obviously exists. In the light of  I think it's be a good idea to improve the manageability of Macs (and probably Linux as well) - especially the ability of "moving around" the clients (or replacing/"splitting"/"merging" the servers).

    Oh, and thanks for the feedback

    Christian

    :3424
Children
No Data
Unfiltered HTML