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 over 14 years ago

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

post (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

This thread was automatically locked due to age.

Parents

0 RL over 14 years ago

Hi Christian and Remo
Yes that is basically the same thing i am doing except i think my way is easier in regards to create the package and push out to the client machine and there is no need to go to each machine and copy the com.sophos.sau.plist to it.
My instructions are in detail because following the instructions any one can create this now and there was no point me providing half or incomplete steps because that doesn't help anyone.
Composer can be used for many packaging need in MAC OSX and is a must for any Mac administrator.
As you can see in my steps when you copy the com.sophos.sau.plist and along with the com.sophos.sav.plist file to the relevant resource locations with in the mpkg through composer stated in my steps, when the final package is built and gets installed on the Mac osx clients the com.sophos.sau.plist and com.sophos.sav.plist settings get installed on the client and you don't have to manually go to each machine and copy these manually stated in the other thread.
This is also good because this allows you to make the mpkg a full offline installer and doesn't need to wait to contact the server to get the update details.
Remo there isn't a simple command you can do like in windows OS and this is because of the way pkgs and mpkgs are handled by the OS.
There are other ways but they are much more complicated, longer and i will just end up confusing you.
TK
:3461
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 RL over 14 years ago

Hi Christian and Remo
Yes that is basically the same thing i am doing except i think my way is easier in regards to create the package and push out to the client machine and there is no need to go to each machine and copy the com.sophos.sau.plist to it.
My instructions are in detail because following the instructions any one can create this now and there was no point me providing half or incomplete steps because that doesn't help anyone.
Composer can be used for many packaging need in MAC OSX and is a must for any Mac administrator.
As you can see in my steps when you copy the com.sophos.sau.plist and along with the com.sophos.sav.plist file to the relevant resource locations with in the mpkg through composer stated in my steps, when the final package is built and gets installed on the Mac osx clients the com.sophos.sau.plist and com.sophos.sav.plist settings get installed on the client and you don't have to manually go to each machine and copy these manually stated in the other thread.
This is also good because this allows you to make the mpkg a full offline installer and doesn't need to wait to contact the server to get the update details.
Remo there isn't a simple command you can do like in windows OS and this is because of the way pkgs and mpkgs are handled by the OS.
There are other ways but they are much more complicated, longer and i will just end up confusing you.
TK
:3461
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data