Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 1 subscriber
  • Views 1593 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.
Parents
  • 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
Reply
  • 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
Children
No Data