autoupdate.rst 4.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125
  1. =====================
  2. The Automatic Updater
  3. =====================
  4. The Automatic Updater ensures that you always have the
  5. latest features and bug fixes for your ownCloud synchronization client.
  6. The Automatic Updater updates only on Mac OS X and Windows computers; Linux
  7. users only need to use their normal package managers. However, on Linux systems
  8. the Updater will check for updates and notify you when a new version is
  9. available.
  10. .. note:: Because of various technical issues, desktop sync clients older than
  11. 1.7 will not be allowed to connect and sync with the ownCloud 8.1+ server. It
  12. is highly recommended to keep your client updated.
  13. Basic Workflow
  14. --------------
  15. The following sections describe how to use the Automatic Updater on different
  16. operating systems.
  17. Windows
  18. ^^^^^^^
  19. The ownCloud client checks for updates and downloads them when available. You
  20. can view the update status under ``Settings -> General -> Updates`` in the
  21. ownCloud client.
  22. If an update is available, and has been successfully downloaded, the ownCloud
  23. client starts a silent update prior to its next launch and then restarts
  24. itself. Should the silent update fail, the client offers a manual download.
  25. .. note:: Administrative privileges are required to perform the update.
  26. Mac OS X
  27. ^^^^^^^^
  28. If a new update is available, the ownCloud client initializes a pop-up dialog
  29. to alert you of the update and requesting that you update to the latest
  30. version. Due to their use of the Sparkle frameworks, this is the default
  31. process for Mac OS X applications.
  32. Linux
  33. ^^^^^
  34. Linux distributions provide their own update tools, so ownCloud clients that use
  35. the Linux operating system do not perform any updates on their own. The client
  36. will inform you (``Settings -> General -> Updates``) when an update is
  37. available.
  38. Preventing Automatic Updates
  39. ----------------------------
  40. In controlled environments, such as companies or universities, you might not
  41. want to enable the auto-update mechanism, as it interferes with controlled
  42. deployment tools and policies. To address this case, it is possible to disable
  43. the auto-updater entirely. The following sections describe how to disable the
  44. auto-update mechanism for different operating systems.
  45. Preventing Automatic Updates in Windows Environments
  46. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  47. Users may disable automatic updates by adding this line to the [General]
  48. section of their ``owncloud.cfg`` files::
  49. skipUpdateCheck=true
  50. Windows administrators have more options for preventing automatic updates in
  51. Windows environments by using one of two methods. The first method allows users
  52. to override the automatic update check mechanism, whereas the second method
  53. prevents any manual overrides.
  54. To prevent automatic updates, but allow manual overrides:
  55. 1. Edit these Registry keys:
  56. a. (32-bit-Windows) ``HKEY_LOCAL_MACHINE\Software\ownCloud\ownCloud``
  57. b. (64-bit-Windows) ``HKEY_LOCAL_MACHINE\Software\Wow6432Node\ownCloud\ownCloud``
  58. 2. Add the key ``skipUpdateCheck`` (of type DWORD).
  59. 3. Specify a value of ``1`` to the machine.
  60. To manually override this key, use the same value in ``HKEY_CURRENT_USER``.
  61. To prevent automatic updates and disallow manual overrides:
  62. .. note:: This is the preferred method of controlling the updater behavior using
  63. Group Policies.
  64. 1. Edit this Registry key:
  65. ``HKEY_LOCAL_MACHINE\Software\Policies\ownCloud\ownCloud``
  66. 2. Add the key ``skipUpdateCheck`` (of type DWORD).
  67. 3. Specify a value of ``1`` to the machine.
  68. .. note:: Enterprise branded clients
  69. (see `Building Branded ownCloud Clients
  70. <https://doc.owncloud.org/branded_clients/>`_) have different key names,
  71. which are set in ownBrander using the Application Vendor and Application
  72. Name fields. Your key names look like this::
  73. ``HKEY_LOCAL_MACHINE\Software\Policies\myCompanyName\myAppName``
  74. Preventing Automatic Updates in Mac OS X Environments
  75. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  76. You can disable the automatic update mechanism, in the Mac OS X operating system,
  77. by copying the file
  78. ``owncloud.app/Contents/Resources/deny_autoupdate_com.owncloud.desktopclient.plist``
  79. to ``/Library/Preferences/com.owncloud.desktopclient.plist``.
  80. Preventing Automatic Updates in Linux Environments
  81. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  82. Because the Linux client does not provide automatic updating functionality, there is no
  83. need to remove the automatic-update check. However, if you want to disable it edit your desktop
  84. client configuration file, ``$HOME/.local/share/data/ownCloud/owncloud.cfg``.
  85. Add this line to the [General] section::
  86. skipUpdateCheck=true