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

Offline updates - isched.cfg being overwritten? Setup complete indicator?

Elbow

Apologies for all the questions - having a few issues.  Process I've been following to update machines that aren't currently fully networked:

- copy SAVSCFXP folder to the target server

- stop Sophos AV service

- run setup.exe from the SAVSCFXP folder

Bit of time passes then:

- Sophos AV service seems to start up itself

- isched.cfg file gets overwritten with settings from unknown source

Can anyone tell me where the settings that end up in isched.cfg are found?  Also, if I use the "mng no" command line switch with setup, isched.cfg gets overwritten with entirely other settings.  Where do they come from? 

Also - how do I tell when the setup installation has completed?  Is there something I can look out for?

Hopefully that all makes sense,

Thanks in advance.

:35709


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

    Hello Elbow,

    my bad, may bad. In retrospect I've blundered in my last reply: AutoUpdate does of course not call setup.exe but the Installer - AutoUpdate and setup.exe have different intents.  While AutoUpdate tries to keep settings setup.exe (re-)initializes them. I'll try to do better this time.

    isched.cfg

    Is it really isched.cfg? It controls whether the automatic updating can be configured using the GUI, updating is enabled, the frequency and if it should run if dial-up is detected. Can't see why -mng no should result in entirely other settings (well, AllowLocalConfig is expected to be 1 instead of 0 if the computer is not managed) but I've never checked. The "templates" are in SAVSCFXP\sau\CommonAppData\Sophos\AutoUpdate\DefaultConfig and customized according to the parameters specified (and the environment found), for example -updp and credentials modify iconn.cfg.

    how do I tell when the setup installation has completed?

    AFAIK, on an unmanaged computer the Sophos System Tray icon notifies you with Sophos Protection or something like that when it's up and running (not only after install but whenever Almon has initialized I think). Open the SESC GUI - if all items are active (colored) the install has completed. Also there are the logs in the %TEMP% directory. Guess the exact point in time is not critical though.

    Christian

    :35711
Reply
  • 0

    Hello Elbow,

    my bad, may bad. In retrospect I've blundered in my last reply: AutoUpdate does of course not call setup.exe but the Installer - AutoUpdate and setup.exe have different intents.  While AutoUpdate tries to keep settings setup.exe (re-)initializes them. I'll try to do better this time.

    isched.cfg

    Is it really isched.cfg? It controls whether the automatic updating can be configured using the GUI, updating is enabled, the frequency and if it should run if dial-up is detected. Can't see why -mng no should result in entirely other settings (well, AllowLocalConfig is expected to be 1 instead of 0 if the computer is not managed) but I've never checked. The "templates" are in SAVSCFXP\sau\CommonAppData\Sophos\AutoUpdate\DefaultConfig and customized according to the parameters specified (and the environment found), for example -updp and credentials modify iconn.cfg.

    how do I tell when the setup installation has completed?

    AFAIK, on an unmanaged computer the Sophos System Tray icon notifies you with Sophos Protection or something like that when it's up and running (not only after install but whenever Almon has initialized I think). Open the SESC GUI - if all items are active (colored) the install has completed. Also there are the logs in the %TEMP% directory. Guess the exact point in time is not critical though.

    Christian

    :35711
Children
No Data