![]() ![]() When administrators specify a given policy on the server, mobile devices that fully support those feature options will stop working if the server-side policy settings raise the bar beyond the devices' capabilities. That detail didn't stop pundits from favorably comparing WiMo 5.x's ineffectual wipe with the lack of any remote wipe feature on the original iPhone up until the release of the 2.0 firmware.Īn Exchange server has no way to demand that clients obey all of its security policies it has to trust that client devices respect them. This effectively meant that Exchange admins simply could not really wipe a WiMo 5.0 phone, even though the devices were described as supporting a form of remote wipe. ![]() Since most WiMo phones shipped with very little included storage, any important data was most likely kept on this impossible to wipe Flash memory. Even Microsoft's own Windows Mobile 5.x implemented support for EAS differently than the current WiMo 6.x.įor example, under WiMo 5, EAS remote wipe couldn't also clear any data stored on an installed SD Flash card. For example, the Palm Pre's Exchange support currently doesn't support security policy involving PIN use or remote wipe at all. This makes it more likely that a thief could interrupt the wipe process, although once a phone is stolen, a savvy thief can disable its network connection and attempt to prevent any remote wipe from ever occurring.Ĭlient manufacturers who license EAS from Microsoft, including Apple, Palm and Sony Ericsson, can implement the EAS specification on their client devices however they like. Without device encryption, a remote wipe takes longer because the remote device must zero all of its files. With file level device encryption, administrators can rapidly remote wipe a lost or stolen device, minimizing the risk of its data falling in the wrong hands. For example, in Exchange 2007 Service Pack 1, Microsoft added a new security policy option to require device encryption on mobile devices in order to support a new feature of Windows Mobile 6.0. ![]() Microsoft has evolved EAS over time, adding new options that allow Exchange admins additional control over the devices they choose to support. Improved support for Microsoft's Exchange Server's security policy features, delivered in the iPhone 3.1 firmware update, has left some users angry after discovering that their mobile device is no longer compatible with the policy defined by their company.Īt issue is Apple's iPhone client implementation of Exchange ActiveSync, the Microsoft specification Apple licensed last year in order to provide official support for Exchange Server sync to the iPhone and iPod touch.ĮAS defines not only how Exchange server syncs data to mobile clients, but also involves remote management features like remote wipe and security policy such as mandating that all devices be set to use a PIN to lock the screen when not in use.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |