[commits] [Wiki] changed: ActiveSync

[Michael Rubinsky]

mrubinsk  Mon, 27 Jul 2015 15:42:11 +0000

Modified page: http://wiki.horde.org/ActiveSync
New Revision:  280
Change log:  Update this section a bit since support in clients has  
improved over time.

@@ -138,18 +138,19 @@
  No additional steps are normally necessary for synchronization of  
the supported applications. However, each application that supports  
synchronization also has user preferences to determine which shares  
will be synchronized. For example, in Kronolith the user's default  
calendar is *always* synchronized, but the user can choose to add any  
additional calendars he/she owns.

  +++ Multiple sources in the same collection

-Prior to Horde 5.2, all non-email sources would be "multiplexed"  
together so they appear as a single source on the client. For example,  
all user calendars would appear as a single, combined calendar on the  
client and any new events would always be added to the user's default  
calendar. Starting with Horde 5.2, applications can be configured to  
provide all user sources as discrete sources on the client. Since very  
few EAS clients actually support this, there are a number of ways to  
control this:
-* By enabling/disabling the discrete sources preference per  
application. This, of course, affects all of a user's devices, so must  
be set to the lowest common denominator. If it is desired to always  
force the multiplexed collections, you can lock the preference.
-* By implementing the activesync_device_modify hook (see  
//horde/config/hooks.php.dist//). There is a sample hook already  
defined that performs some basic device sniffing to determine which  
collections do not support discrete sources. For example, Android  
devices typically do not support ANY discrete non-email sources, so we  
disable this for any Android device, while iOS supports discrete  
sources for everything exempt Memos.
+Prior to Horde 5.2, all non-email sources would be "multiplexed"  
together so they appear as a single source on the client. For example,  
all user calendars would appear as a single, combined calendar on the  
client and any new events would always be added to the user's default  
calendar. Starting with Horde 5.2, applications can be configured to  
provide all user sources as discrete sources on the client. Since not  
all EAS clients support this, there are a number of ways to control  
this.
+* By enabling/disabling the discrete sources preference per  
application. This, of course, affects all of a user's devices, so must  
be set to the lowest common denominator. If it is desired to always  
force the multiplexed collections, you can lock the preference. When  
this pref is activated, the ActiveSync library a tries to sniff out  
the client's capability and disables this if the client is unable to  
honor it.
+* By implementing the activesync_device_modify hook (see  
//horde/config/hooks.php.dist//). There is a sample hook already  
defined that performs some basic device sniffing to determine which  
collections do not support discrete sources.

  The following chart is meant to provide a general idea of what  
device class supports this, not a listing of all devices and  
capabilities:
  ||~ Device ||~ Calendars ||~ Contacts ||~ Tasks ||~ Memos ||~  
Creating new sources ||~ Notes ||
  || Android || || || || || || ||
+|| Blackberry || Yes || Yes || Yes || Yes || Yes, for Tasks and Notes  
|| Creating a new Notes source from 10.3.x only||
  || iOS || Yes || Yes || Yes || || Yes, for Calendars and Tasks || ||
+|| Outlook || Yes || No || Yes || n/a || || ||
  || Windows Phone || || || Yes || || || ||
-|| Blackberry || Yes || Yes || Yes || Yes || Yes, for Tasks and Notes  
|| Creating a new Notes source from 10.3.x only||

  Users can also view all their paired !ActiveSync devices by visiting  
their //!ActiveSync Devices// preferences. This is located within  
Horde's //Global Preferences//. From here, it is possible to force a  
complete re-sync, or to request a remote wipe of a provisioned device  
(see below).

  ++ Email Support