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

Package for standalone AV

Jvuz

Hello,

we have some machines that are not connected to our network. For those pc's, notebooks I can install the standalone version, but you need to give in username and password. Is there a way to create a package where you can set the username and password to dowload the updates from the sophos site, so that when you want to install it on a machine, you just need to run that package and it will be installed without giving in the username and password.

Jo

:15873


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

    HI,

    There are a couple of options:

    http://www.sophos.com/support/knowledgebase/article/67504.html
    which essentially uses sauconfi.xml but you have to use ExportPrivateStore.exe to create the XML and then edit it.

    Another approach which you might find easier is to bundle up a distribution location/CID.  You would call the install using the switches to setup.exe:
    http://www.sophos.com/support/knowledgebase/article/12570.html

    From a working "template" machine, that is configured correctly, take a copy of the iconn.cfg file from the machine as this essentially defines the update policy.  You could then overwrite the "un-configured" file.

    To wrap it all up, you could create an SFX from the CID + the configured iconn.cfg file.  Then the SFX would run a script, e.g. a batch file to call setup.exe with the necessary switches and finally copy over the configured iconn.cfg.

    As a slight change to the second option, rather than just copying over the file, it's possible to use the SAU API to change the config, so if the script run by the SFX was something like VBScript you could do it from that:

    http://www.sophos.com/support/knowledgebase/article/36262.html
    has a few ideas.  

    That last link also gives an example of how to call an update at the end of the install.  Otherwise, if you go for a more simple approach using a batch, file, restarting the AutoUpdate Service will kill off an update within 5 mins. 

    Hope it helps and gives you some ideas of potential routes to take,

    Regards,

    Jak
     

    :15875
Reply
  • 0

    HI,

    There are a couple of options:

    http://www.sophos.com/support/knowledgebase/article/67504.html
    which essentially uses sauconfi.xml but you have to use ExportPrivateStore.exe to create the XML and then edit it.

    Another approach which you might find easier is to bundle up a distribution location/CID.  You would call the install using the switches to setup.exe:
    http://www.sophos.com/support/knowledgebase/article/12570.html

    From a working "template" machine, that is configured correctly, take a copy of the iconn.cfg file from the machine as this essentially defines the update policy.  You could then overwrite the "un-configured" file.

    To wrap it all up, you could create an SFX from the CID + the configured iconn.cfg file.  Then the SFX would run a script, e.g. a batch file to call setup.exe with the necessary switches and finally copy over the configured iconn.cfg.

    As a slight change to the second option, rather than just copying over the file, it's possible to use the SAU API to change the config, so if the script run by the SFX was something like VBScript you could do it from that:

    http://www.sophos.com/support/knowledgebase/article/36262.html
    has a few ideas.  

    That last link also gives an example of how to call an update at the end of the install.  Otherwise, if you go for a more simple approach using a batch, file, restarting the AutoUpdate Service will kill off an update within 5 mins. 

    Hope it helps and gives you some ideas of potential routes to take,

    Regards,

    Jak
     

    :15875
Children
No Data