![]() ActiveSync PoliciesĪctiveSync Policies, such as enforcing a Device Unlock Password or Device Encryption are typically applied during the Provisioning phase of enrolling an ActiveSync client with an ActiveSync server.Īt a high level, the Provisioning process proceeds as follows – Version 1.0 of ActiveSync simply allowed a mobile device sync mail/contacts/calendar from a server, which was a significant improvement from POP3 which was more common at the time.ĪctiveSync 2.5 added Direct Push, the ability for the server to inform the client that new mail was available in the users’ mailbox so it should connect and sync this new mail.ĪctiveSync 2.5 also added the first policies/controls in the form of Remote Wipe (the ability for an administrator to set a flag that the ActiveSync client would read during the next sync and initiate a wipe of the device) and the enforcement of a Device Unlock Password/PIN along with some control over theįurther enhancements and controls were added to ActiveSync with enforcement of Device Encryption becoming an option with ActiveSync 12.1. The ActiveSync protocol has moved through a number of iterations with releases typically coinciding with new editions of Microsoft Exchange Server. Nokia Symbian, Windows Mobile, Blackberry BB10, Google Android, Windows Phone, Apple iOS, Windows 8 RT and Windows 8 Pro all include an ActiveSync PIM client. Microsoft Exchange ActiveSync is a collection of protocols that enables mobile devices to synchronize and exchange messaging objects such as email, contacts, or calendar items (often referred to as PIM data) with a server.ĪctiveSync was originally released in 1996 and has now become the de-facto standard for syncing corporate PIM data from various enterprise email solutions from Microsoft Exchange to Lotus Notes, Office365 and Google Apps to mobile devices.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |