Search results

From Open-Xchange
  • ...oke former given access, the data for objects will still be present in the database and on the filestore but is not visible to the customer any more. Please no
    35 KB (5,130 words) - 09:22, 10 January 2020
  • ...volumes on the shared storage are available: an EXT3 volume for the MySQL database, another EXT3 volume for the mail services (smtp, imap) and a store for the
    26 KB (3,410 words) - 09:34, 27 November 2015
  • ...lient. It contains settings for the world's largest ISPs. We hope that the database will soon have enough information to autoconfigure approximately 50% of our | <nowiki>username for the database user </nowiki>
    231 KB (31,760 words) - 11:29, 16 April 2013
  • ...lient. It contains settings for the world's largest ISPs. We hope that the database will soon have enough information to autoconfigure approximately 50% of our | <nowiki>username for the database user </nowiki>
    231 KB (31,767 words) - 10:27, 19 April 2013
  • ...lient. It contains settings for the world's largest ISPs. We hope that the database will soon have enough information to autoconfigure approximately 50% of our | com.openexchange.database.replicationMonitor
    247 KB (33,845 words) - 11:37, 16 August 2013
  • ...lient. It contains settings for the world's largest ISPs. We hope that the database will soon have enough information to autoconfigure approximately 50% of our | com.openexchange.database.replicationMonitor
    268 KB (37,155 words) - 12:16, 21 October 2015
  • ...ther OX authentication package installed like „open-xchange-authentication-database“. Additionally, don't install following packages, since they are not need ...min-plugin-contextrestore, open-xchange-log4j, open-xchange-passwordchange-database, open-xchange-passwordchange-servlet
    27 KB (3,970 words) - 06:25, 1 September 2016
  • ...t. It contains settings for the world&#39;s largest ISPs. We hope that the database will soon have enough information to autoconfigure approximately 50% of our | <nowiki>com.openexchange.database.replicationMonitor</nowiki>
    271 KB (37,062 words) - 13:43, 1 July 2015
  • ...t. It contains settings for the world&#39;s largest ISPs. We hope that the database will soon have enough information to autoconfigure approximately 50% of our | <nowiki>com.openexchange.database.replicationMonitor</nowiki>
    280 KB (38,131 words) - 21:26, 5 March 2014
  • ...t. It contains settings for the world&#39;s largest ISPs. We hope that the database will soon have enough information to autoconfigure approximately 50% of our | <nowiki>com.openexchange.database.replicationMonitor</nowiki>
    293 KB (39,973 words) - 13:36, 1 July 2015
  • ...t. It contains settings for the world&#39;s largest ISPs. We hope that the database will soon have enough information to autoconfigure approximately 50% of our | <nowiki>com.openexchange.database.replicationMonitor</nowiki>
    297 KB (40,685 words) - 10:14, 13 June 2017
  • ...t. It contains settings for the world&#39;s largest ISPs. We hope that the database will soon have enough information to autoconfigure approximately 50% of our | <nowiki>com.openexchange.database.replicationMonitor</nowiki>
    300 KB (41,181 words) - 07:10, 9 July 2015
  • ...t. It contains settings for the world&#39;s largest ISPs. We hope that the database will soon have enough information to autoconfigure approximately 50% of our | <nowiki>com.openexchange.database.replicationMonitor</nowiki>
    301 KB (41,323 words) - 19:56, 2 December 2015
  • ...t. It contains settings for the world&#39;s largest ISPs. We hope that the database will soon have enough information to autoconfigure approximately 50% of our ...to personal folders (personal in terms of non-global e.g. folders kept in database) are supposed to be propagated to remote nodes. This option is only useful
    321 KB (44,146 words) - 07:59, 2 December 2015
  • ...t. It contains settings for the world&#39;s largest ISPs. We hope that the database will soon have enough information to autoconfigure approximately 50% of our ...to personal folders (personal in terms of non-global e.g. folders kept in database) are supposed to be propagated to remote nodes. This option is only useful
    333 KB (45,761 words) - 15:55, 17 May 2016
  • ...t. It contains settings for the world&#39;s largest ISPs. We hope that the database will soon have enough information to autoconfigure approximately 50% of our ...to personal folders (personal in terms of non-global e.g. folders kept in database) are supposed to be propagated to remote nodes. This option is only useful
    347 KB (47,794 words) - 13:34, 31 January 2017
  • ...t. It contains settings for the world&#39;s largest ISPs. We hope that the database will soon have enough information to autoconfigure approximately 50% of our ...to personal folders (personal in terms of non-global e.g. folders kept in database) are supposed to be propagated to remote nodes. This option is only useful
    351 KB (48,276 words) - 15:48, 31 January 2017
  • ...t. It contains settings for the world&#39;s largest ISPs. We hope that the database will soon have enough information to autoconfigure approximately 50% of our ...to personal folders (personal in terms of non-global e.g. folders kept in database) are supposed to be propagated to remote nodes. This option is only useful
    366 KB (50,420 words) - 07:11, 29 September 2017
View ( | ) (20 | 50 | 100 | 250 | 500)