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

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
  • hi forum

    german support gave me the following information regarding this topic.

    migrating macosx client from one sec to another is not possible with mrinit.custom as in windows.

    (with mrinit.conf)

    the only options you have is either edit the local router.config or uninstall / reinstall with the right mrinit.conf.

    kind regards

    remo

    :3608
Reply
  • hi forum

    german support gave me the following information regarding this topic.

    migrating macosx client from one sec to another is not possible with mrinit.custom as in windows.

    (with mrinit.conf)

    the only options you have is either edit the local router.config or uninstall / reinstall with the right mrinit.conf.

    kind regards

    remo

    :3608
Children
No Data