![]() This distinction is an important one, as users sometimes forgo using ActiveSync in fear of losing personal data (photos of your dog or kids doing cute stuff) when a Remote Wipe is instigated for instance due to too many faulty password logon attempts or an admin clicking on the wrong button.Īnother difference is that security policies like screen lock timeout and PIN requirements are also in-app only, which some users might find too restrictive. Where EAS would in most cases (Mail app in Windows 8 and 10 is an exception as seen here) wipe the whole device and revert it to factory defaults, OWA for Devices only wipes the data within the app. Heck, it's not even an implementation that has all possible capabilities, for instance SMS-sync is an option and was last seen in a Microsoft product with Windows Mobile 6.x (!).īut besides that, what features do I mean? Well, one important distinction is data isolation. ![]() I've heard this argument before, that the Exchange ActiveSync (EAS) implementation in Windows Phone doesn't require an OWA for Devices app (or MOWA as is the official acronym) like iOS has (for iPad and iPhone) and what is currently in preview for Android.Īlthough the Windows Phone 8 ActiveSync implementation doesn't have the issues both other mobile OS's have, it's certainly not on par with OWA for Devices. Native app handles all of that functionality. ![]() Recently I came across this Twitter You don't need it for WP. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |