[cvs] [Wiki] changed: ActiveSync

[Michael Rubinsky]

mrubinsk  Thu, 10 Jun 2010 19:06:03 -0400

Modified page: http://wiki.horde.org/ActiveSync
New Revision:  1.68
Change log:  some tweaks

@@ -15,9 +15,9 @@
  ++ Description

  The Horde !ActiveSync implementation provides over the air  
synchronization of email, contacts, and calendar data to devices such  
as the iPhone/iPod Touch, Android and any other system supporting  
!ActiveSync. This implementation supports Microsoft !ActiveSync  
protocol versions up to 2.5 - the version implemented by Microsoft  
Exchange 2003.

-++ Configuration
+++ Setup

  !ActiveSync support is not active by default, and should still be  
considered experimental. The code base is fairly stable, but there are  
still devices on which it has not been tested yet. It may work, it  
might not, or it might make your iPod grow legs and run for higher  
ground. You have been warned.  If you have used a device with Horde's  
!ActiveSync support that is not listed below, please feel free to let  
us know how it went.

  To activate the server, you need to enable it in Horde's  
configuration, on the !ActiveSync tab.  You will also need to create  
the SQL tables that horde uses using the  
//horde/scripts/sql/horde_activesync.sql// creation script.
@@ -69,13 +69,9 @@
  Users can initiate a remote wipe, as well as view/manage their  
partnered devices in the !ActiveSync user preference.

  Clicking //Wipe// flags the server to send the wipe command to the  
device the next time it synchronizes. The next time the device  
attempts to request a command other then PING or OPTIONS, it will be  
wiped. The !ActiveSync preference page shows the status of all the  
user's devices. If the status is listed as //Pending//, and you wish  
to cancel the wipe request, you may do this by clicking the //Cancel  
Wipe// button. You should see the status be reset to //Provisioned//.  
After it is wiped, the status will be shown as //Wiped//, if you wish  
to allow the device to connect to your server again, you need to  
explicitly remove the device as a sync partner by clicking the  
//Remove// button. If you do not remove this entry, the device will  
continue to be wiped each time it reconnects to the server.

-++ Rough list of issues/todos/development notes in no particular order
-
-* Implement more recent protocol version support - version 12 or  
maybe 12.1 (Exchange 2007??) should be fairly non-disruptive. Version  
12 would get us more atomic policy settings, local wipe rules, as well  
as the ability to send the policy settings to the client as the more  
compact wbxml. 14 (Exchange 2010?) would probably be lots more work as  
it does away with PING, using SYNC for waiting for changes instead.
-
-++ What to do if you have problems (or How to help us debug your issue)
+++ What to do if you have problems (or How to help us help you)

  **If you are not even able to get past the initial setup page on  
your phone**: you should first check to be sure you do not have SSL  
enabled on the phone when you're server is not serving SSL. The  
iPhone/iPod will not let you turn this off until after you save the  
configuration, so you must continue through all the errors and go back  
into the settings to disable SSL. You should also make sure that you  
have not enabled Provisioning support if your phone does not support it.

  **If the configuration went well, but you are not seeing any  
contacts/calendar items appear on the device:** Some clients require a  
manual refresh or folder selection after setup when not using the  
"Automatic Discovery" facility of Exchange. With !TouchDown, for  
example, after setup you must select the folders you want sync'd under  
the Advanced settings tab.
@@ -85,8 +81,12 @@
  * Check the web server error logs and see if there are any PHP  
errors being logged.
  * Configure Horde to send !ActiveSync log messages to a separate  
logfile. This is configured on the !ActiveSync tab of Horde's  
configuration screen.
  * If you are able to, it would also be useful to run a wireshark  
session to capture the network communication.
  * In some cases, it might be useful for us to see the affected  
device's state records in the database.
+
+++ Todo
+
+* Implement more recent protocol version support - version 12 or  
maybe 12.1 (Exchange 2007??) should be fairly non-disruptive. Version  
12 would get us more atomic policy settings, local wipe rules, as well  
as the ability to send the policy settings to the client as the more  
compact wbxml. 14 (Exchange 2010?) would probably be lots more work as  
it does away with PING, using SYNC for waiting for changes instead.

  ++ Resources

  http://z-push.sourceforge.net