Replies

None of those three links even mention Exchange. Do you even know what that is?

Oh, I definitely do! Apparently you're a bit lacking in knowledge. Android has supported Microsoft Exchange since 2008. What's your problem? Are you just being obtuse on purpose?

I am, however, here to inform you that device-level (that is, hardware) encryption is commonly necessary for remote connections in corporate Exchange server setups. Blackberry devices do hardware encryption; so does iPhone 3GS and 4. As far as I can tell, no Android device meets this standard. As far as I can tell, no Android device meets this standard.

Device level means "hardware based"? Yet another term you're redefining or making up? Businesses allow laptops WITHOUT hardware encryption to connect to Exchange all the time; you need to implement an SSH tunnel, provide for local encryption as needed (hardware or software) and you can do that with Android. And many times you need to support remote wipe and password security policies - which those apps I linked supplied.

Here's another app that works.

So yes, Android works fine with corporate situations. But don't just take my word for it (you won't); Motorola can set you straight.

"Android has supported Microsoft Exchange since 2008. What's your problem? Are you just being obtuse on purpose?"

I wish you'd learn to provide a link or two to at least attempt to support your bogus claims. The Exchange "support" you mention was very limited in 2008 and still, near as I can tell, doesn't include encryption baked into the mix. I rely on published accounts such as this one from CNet from late last year:

"[Android's] lack of real encryption is a serious concern. The security measures that are built into Android 2.0 are limited at best. Yes, end users can set up finger-swipe passwords for when their screens time out or after the handset reboots. And yes, Droid lets you secure your information with an alphanumeric password.

"Unfortunately, that's about it. IT professionals can't define security policies, perform a remote wipe, or remotely provision handsets, which means that your IT manager would essentially have to physically touch every device to set it up. And if you lose your handset, your data might be as good as compromised."

Perhaps the situation has improved with post-2.0 versions of Android, but from your links it seems not, and costly and confusing arrays of third-party software are needed to implement even rudimentary software encryption. Because that's all you'll get, and as I've been saying, that's usually not enough. For example there's things like this: "Android hardware also lacks support for hardware encryption, making the devices ineligible for support by the default security policy of Exchange Server."

Which is what I've been trying to inform you. See, we latte-sipping and probably gay Macbots have been there before. Apple introduced a perfectly operable software-encryption-based Exchange capability in iPhone OS 3, then had to disable it for the older iPhone 3G, which lacked the necessary hardware encryption to meet default Exchange security policies as commonly configured.

Now it might be that one of the very latest Android phones running the very latest Android OS is finally equipped to perform hardware encryption, bringing it up to the level of capability of the last-generation iPhone 3GS. But if so, that doesn't exactly leap from the pages of those links you provided. Which is another problem with Android: it's freaking chaos out there.

Your apologies are accepted.

Oh, and by the way, I'd hope Motorola might set you straight too. Referring to your link and noting a little click-thingie for what to do if your Droid doesn't work with the Exchange Server, I dug a little deeper. Sure enough, if your Exchange Server device policies require encryption (and, dear me, isn't that what I've been talking about all along?), there are instructions to... get ready... just turn it off! How about that.

Have a cigar. [>boom<]

----

DROID - Exchange Email Troubleshooting

If you are able to successfully connect an Exchange account on your phone, but your email and contacts are not syncing with your device, your company may have a security policy that prevents syncing.

At launch, Motorola DROID's native exchange solution doesn't support password security policy or remote wipe.

If your company's exchange server has been setup to ONLY allow devices that support password security policy, your IT administrator will need to customize some of the settings on the Exchange server for your Motorola DROID to successfully sync.

What options do I have if my company has password security policy on their exchange server?

Option 1 - Instructions for configuring your Exchange Settings

The following solution describes the options that your IT admin can take to adjust the password security policies on your Exchange server to allow DROID connectivity. The available options depend on whether you have Microsoft® Exchange 2003 Server or Microsoft® Exchange 2007 Server. Mobile Email Sync can not be set-up on a Microsoft® Exchange 2000 Server.

Remember that you can protect the data on your device by enabling "gesture" lock in Settings => Location & security menu.

Option 2 - While we do not endorse or guarantee these solutions, or provide support for them, some owners have reported success using a 3rd party Android Application like "Touchdown Exchange". You can search the Android Market for 3rd party applications that are available that will enable you to provision Exchange email with force password security policies.

Exchange 2003 SP2 Instructions

1.     Launch Microsoft Exchange System Manager:

2.     Change Mobile Service Properties:

3.     Select device security

4.     Enable "Allow access to devices that do not fully support password settings." Turning on this setting will allow devices like the Motorola DROID to connect to your Exchange server. This will not change any requirements for devices that do fully support Exchange security policy - they will continue to require password access. [snip]