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

Creating standalone installer for home users - confused

newco

Hello!

I followed the Best practice guide to create standalone installers for home users. Everything works, except one strange thing.

The guide tells to run setup.exe with the "-updp %SystemRoot%\Temp\savinst\SAVSCFXPXML\" parameter. So, when I installed the software on a Windows 7 x64, the primary update location in the program is this path, on the local computer. Not what is set in the updating policy in SEC. So it never will update, but if I run "Update now" it says OK. Is this folder updated by something? I don't think so... Or am I wrong? When I deleted the folder, Sophos couldn't update ("Could not contact server").

Question: shouldn't setup.exe called with -updp publishedupdatelocation.company.com?

I am confused...

Thanks,

newco

:33521


This thread was automatically locked due to age.
  • 0

    Hello newco,

    in step 11 of the guide you export the Sophos auto updater (SAU) and Sophos anti-virus (SAV) policies to the SAVSCFXPXML-directory.

    As far as I understand when you create the installer package, Sophos is installed with the update path %SystemRoot%\Temp\savinst\SAVSCFXPXML\ when it updates from that path the first time it pulls the SAU and SAV configuration from that path and configures itself to update from the source in that policy.

    Regards -sd

    :33523
  • 0

    Thank you for your reply, I sorted out the problem.

    I wrote a little tool to automate everything that can be automated to create the installers and the tool run the export config commands not properly and I didn't add an error check to this part of the code.:) So the configs were not exported-imported and that's why the standalone installer didn't change install location. After correcting the script it works.:)

    newco

    :33565
  • 0

    hey,

    cool ;-) i recently had the same problem i have a batch file that creates various standalone-installers with different policies.

    sophos should provide a gui tool for this.

    there is already the "Sophos Deployment Tool" but its automation options do not include policies.

    regards

    :33583