5 ms·
Every Exchange install comes with a default ActiveSync policy and Android (along with iPhone, Windows Phone, and any other ActiveSync-capable client) will alert
by techsupporter 15y ago
Every Exchange install comes with a default ActiveSync policy and Android (along with iPhone, Windows Phone, and any other ActiveSync-capable client) will alert you to its existence and prompt you to accept that fact. This is a feature, not a bug. Your employer or Exchange provider can configure these however they like. Your IT admins may have the security policies locked down because of a requirement from "on high." The default policy is wide open and doesn't require a PIN or password lock nor does it wipe your device if you do set a security lock and get it incorrect.
Both you, as the Exchange user, and the Exchange administrator can perform a remote wipe on your device. If you don't like this level of access, as you said, you can simply not sync your personal device. At my employer, huge swaths of people don't sync work mail with personal devices for this and other reasons.
- barrkel 15y agoI think it's a bug that Android's integration requires you to accept a complete remote wipe, rather than just Exchange data. "Simply" not syncing has only one downside in my practical experience: no calendar integration. The "security" doesn't protect much when there's also IMAP access.
- techsupporter 15y agoEvery non-app ActiveSync implementation I'm aware of requires a full device wipe. iPhone goes one further and busts you down to boot loader (or did when I had an iPhone 3G and tried it out) so that it requires assistance from iTunes to get moving again. Windows Phone and Android will just reboot to stock. Having IMAP access enabled means that your IT department didn't think ahead, they got overruled on having IMAP shut off, since it comes disabled by default, or they are using the default ActiveSync policy which will generate the security prompts as well.
- barrkel 15y agoThe topic is BYOD. "Requiring" a full device wipe is a problem here then, I hope you can see - the remote server has no authority to require such a thing. That's a bug, whether it's a bug with institutions and software licensing, or with implementations, it's still a bug for proper BYOD support.