client update

[Blisk]

Server configuration

I'm running the desktop client on Centos 6.5 x64. The ownCloud sync client version is 1.6.3 Owncloud version 7.0.2

I hope clien soon will be changed to make a unattended or silent installation. Or, to update it withouth entering administrator credentials when update. I have 15 users and when client update I need to go to each one and put in the admin username and password to update. That is really annoying. And it can be solved by unattended installation/update from server.

[danimo]

And it can be solved by unattended installation/update from server.

How? What do you mean?

[Blisk]

almost all software have unattended or silent installation, when in cmd you can run it and software is installed with no intervention at all. I can force with GPO on windows 2008 server that some software is installed on client on windows 7. And almost all software which have possibility to install silently have also possibility when you install new version over old version doesn't ask anything but uninstall previous version and install new one and keep settings. That will help big time. Because with 3 clients that is not a problem with updating but what about 100 clients?

[enoch85]

Agree on this. :+1:

[danimo]

@Blisk and how does that software do that without either being user-only or shipping its own updater service?

[Blisk]

Don't know. But flash player works that way, mozilla firefox also, java, etc. It will be enough if owncloud can be installed silently, so it doesn't ask nothing when you use a swithch /S or /Q like with other programs so I can install it in cmd like this. c:\ownCloud-1.6.2.3463-setup.exe /S with higher privileges and after that it won't ask anything but install or update to the end with default settings. That would solve almost all.

[danimo]

@Blisk They all provide a background service that supervises the update. So far I've tried to avoid that because it adds an extra level of complexity. I'd rather look for existing frameworks in that area, but everyone just seems to roll their own.

As for /S. we already use that (i.e.: it works). You can disable the auto-updater, wrap the .exe into an MSI and you should be able to roll it out enterprise-wide.

[Blisk]

thanks I will try, if msi works with no intervention than I don't need more. you should make exe also to work with /S, so people don't need to convert it into msi.

Wil switch "/S" work with update too?

[danimo]

it's been made work for the automatic updater, so yes.

[Blisk]

thank you, that's all what I need

[danimo]

This now is dupe of #2231.