[cvs] [Wiki] changed: Project/ActiveSync
Michael Rubinsky
mrubinsk at horde.org
Sat May 1 22:40:19 UTC 2010
mrubinsk Sat, 01 May 2010 18:40:19 -0400
Modified page: http://wiki.horde.org/Project/ActiveSync
New Revision: 1.57
Change log: Instructions on requesting/cancelling a remote wipe
@@ -63,9 +63,9 @@
Provisioning allows devices to be more tightly registered with a
particular server. It enables the server to be able to send policy
settings to the device. These policy settings include things like
requiring a PIN to unlock the device, the complexity of the PIN
required, the number of failed login attempts allowed etc...
Additionally, it enables devices to be remotely wiped so that if a
device is lost or stolen, the user or administrator can request the
device to be wiped.
Users can initiate a remote wipe, as well as view/manage their
partnered devices in the !ActiveSync user preference.
-The next time the device attempts to request a command other then
PING or OPTIONS, it will be wiped. **DO THIS AT YOUR OWN RISK!!!**
After it is wiped, if you wish to allow the device to connect to your
server again, you should remove the entry in the device table for the
device so it can be rebuilt. If you do not remove this entry, or at
least set the value of rwstatus back to 0, the device will continue to
be wiped each time it reconnects to the server.
+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.
More information about the cvs
mailing list