HTC Sensation and Outlook Exchange Email

[lancer123]

Hello,
I was wondering if anybody knows why my HTC Sensation will not connect to our Exchange 2010 at my place of work? For some reason, the account will not fully setup because the error claims that encryption is not supported on my phone.

I thought that the Sensation does support encryption? I know in the past that I have had other HTC phones such as the EVO and the Exchange setup worked. Did something with Sense 3.0 break?

I know I can use Touchdown or Moxi Mail, etc. However, I would really like to use the native email client as it integrates nicely with the Calendar,etc.

Thanks for your time,
Lance

 

[bryancruise]

What specific error message are you getting? I have successfully set up TWO exchange accounts to sync with my phone (which is cool that Sense supports > 1 finally). One is at work, where we use SSL encryption, and the other is my home exchange account, where I don't use SSL.

Most commonly, the problem with configuring Exchange sync is on the server side. Have you spoken with your exchange admin? They have a slew of logs that will show your attempts to connect, and can either fix the server configuration, or tell you what the client is doing wrong.

 

[lancer123]

Thanks for helping me. The error I get is
"unable to sign in to your exchange account because your policy seetings are incompatible with those on the server. Please contact your IT Team for assistance."

If I click details, the error says "policy setting incompatible. Device encryption enabled. Required device encryption".

Thanks,
Lance

 

[idephili]

Hi,

not skilled in Exchange 2010, but sounds like a problem with these serversettings, taken from system-manger 2003:



Either last point or a choosen device password doesn´t fulfill the selected policy.

Greets
idephili

 

[damird]

You should check Exchange policy for mobile devices. In Exchange Server 2010 you can enforce several options on device side, including encryption of storage card. However, not all devices support this. Windows Mobile 6.5. was supporting all of them, but new platforms (iOS,WP7 and Android) support only a small subset of features configurable on Exchange side.
Sometime, unsupported feature will just be ignored, but if it is security related it will not let you sync.

Damir

 

[pantera_za]

Hey guys,

I am having the exact same problem. I am using an HTC Sensation running stock 2.3.4. recently, our IT (bank) decided that it would be a bright idea to implement a security policy that requires device encryption. Since then I have been unable to get things working again, and upon investigation, I was told that it was because the Sensation doesn't support device encryption.

Are there any work-arounds that I could try? I have tried to get IT to disable the encryption requirement, but they are refusing to budge. What can I try to do on the device side that will get things working again. I am desperate here.

Any advise will be appreciated.

Regards,
Michael

 

[Catnap]

I have tried to get IT to disable the encryption requirement, but they are refusing to budge.

And rightly so- device encryption is probably enforced so they comply with various industry regulations and don't end up as one of "those" companies that lost a load of customer data and get fined.

The trouble is, even if you were able to fool the server into thinking that the Sensation supports device encryption, were you to lose your phone and it had sensitive information on it, you'd be on the hook for bypassing IT security.

I'm afraid to say you're very unlikely to get this to work if your IT department have this turned on for a reason.

 

[pantera_za]

And rightly so- device encryption is probably enforced so they comply with various industry regulations and don't end up as one of "those" companies that lost a load of customer data and get fined.

The trouble is, even if you were able to fool the server into thinking that the Sensation supports device encryption, were you to lose your phone and it had sensitive information on it, you'd be on the hook for bypassing IT security.

I'm afraid to say you're very unlikely to get this to work if your IT department have this turned on for a reason.

firstly thanks for the reply (as much as it didn't make me feel any better)

I can understand enforcing a device password policy, but requiring a feature that is unsupported by a latest generation device is a bit ridiculous if you ask me, especially given that I have no access to any customer data at all.

The password protection can also be used to wipe the device in the event of theft, so I really don't see where the issue is (while I dislike having a password on the phone, I can at least understand the reasoning for having it), whereas requiring encryption seems a little bit over the top...

 

[Catnap]

firstly thanks for the reply (as much as it didn't make me feel any better)

I can understand enforcing a device password policy, but requiring a feature that is unsupported by a latest generation device is a bit ridiculous if you ask me, especially given that I have no access to any customer data at all.

The password protection can also be used to wipe the device in the event of theft, so I really don't see where the issue is (while I dislike having a password on the phone, I can at least understand the reasoning for having it), whereas requiring encryption seems a little bit over the top...

To be fair, Blackberries have always had robust encryption so I guess they either assumed that all new phones supported it too, or they went "encryption? Goooood. Mobile device encryption? Goooooooooood. <tick>". As much as it doesn't help you, I can understand them wanting to cover their asses.

 

[jelliottz]

Is have no trouble with my sensation on sense 3.0. It meets all of my work security requirements.

When I try sense 3.5, I get the doesn't support device encryption error. Not sure what the difference is, but il sticking with 3.0.

Good luck.

Sent from my HTC Sensation XE with Beats Audio using XDA App

 

[pantera_za]

Is have no trouble with my sensation on sense 3.0. It meets all of my work security requirements.

When I try sense 3.5, I get the doesn't support device encryption error. Not sure what the difference is, but il sticking with 3.0.

Good luck.

Sent from my HTC Sensation XE with Beats Audio using XDA App

thanks for the reply... As I said, the above only started giving problems when they changed the security policy, and started requiring passwords, and apparently encryption.

My other exchange account (which is linked to a consultancy) already required that the device be secured with a PIN. Once the policy changed, I was forced to now enter a password, which I did, with little help.

I am running a stock ROM (1.42) (which I assume uses Sense 3.0). Would moving to a custom ROM possibly help?

 

[bluther]

I have the same problem. Every custom ROM that has Sense 3.5 doesn't work with my exchange account saying that my device isn't encrypted. For now, I have to stay with Sense 3.0 ROM's.

 

[xaccers]

Had a quick look online and it seems encryption was added to honeycomb