The Following 3 Users Say Thank You to tomster For This Useful Post: | ||
|
2010-02-03
, 13:59
|
Posts: 101 |
Thanked: 18 times |
Joined on Dec 2009
@ Sweden
|
#1062
|
|
2010-02-03
, 14:21
|
Posts: 71 |
Thanked: 33 times |
Joined on Dec 2009
@ Munich, Germany
|
#1063
|
|
2010-02-03
, 14:50
|
Posts: 277 |
Thanked: 46 times |
Joined on Jan 2010
|
#1064
|
|
2010-02-03
, 15:05
|
Posts: 277 |
Thanked: 46 times |
Joined on Jan 2010
|
#1065
|
|
2010-02-03
, 19:41
|
Banned |
Posts: 291 |
Thanked: 60 times |
Joined on Dec 2009
|
#1066
|
|
2010-02-03
, 19:47
|
|
Posts: 11,700 |
Thanked: 10,045 times |
Joined on Jun 2006
@ North Texas, USA
|
#1067
|
If you spent 600 plus on a device that does not perform as advertised.......would you give it a rest? I have a simple question: will provisioning appear for this device?
|
2010-02-03
, 19:52
|
Posts: 2,829 |
Thanked: 1,459 times |
Joined on Dec 2009
@ Finland
|
#1068
|
One thing I would not do is continue parroting the same thing over and over and over again in the same place.
I would escalate.
“The definition of insanity is doing the same thing over and over again and expecting different results.”
-Albert Einstein
|
2010-02-03
, 19:55
|
|
Posts: 11,700 |
Thanked: 10,045 times |
Joined on Jun 2006
@ North Texas, USA
|
#1069
|
The Following User Says Thank You to Texrat For This Useful Post: | ||
Tags |
activesync, certificate, email, exchange, fremantle, ignore tex14, maemo 5, mail for exchange, mfe, n900, provisioning, sync, thanks vitaly! |
|
Have you tried to set the EAS protocol permanent to version 2.5 (or maybe 12.0 or 12.1) as described in the Heartbeat-Wiki under troubleshooting?
My guess would be: The older the Exchange server, the less policies IT can enable. Setting N900's protocol to the oldest -> lowest standard (2.5) therefore might help. Again, I don't run either Exchange nor Google Sync!
Though not being related to Nokia or Vitaly's dev team I'd like to take up the cudgels for them - at least to some content ;-)
As much as I know there are a rough 30 different security policies IT can enable on Exchange's 2009 configuration. I doubt that any device (except maybe WinMo 6.1 devices) supports all of them.
The iPhone for example used to forge device encryption on OS3.0 to get Exchange sync up and running. As soon as OS3.1 came out this "feature" was dropped leaving the iPhone disciples syncless again...
If you have the time go read this essay on Exchange's policies. This quite clearly explains why Vitaly would mostly suggest to enable the "Allow non-provisionable devices" tab on Exchange as it eventually eliminates possible sync errors/ communication errors with a hand-strike.
Vitaly & his buddies will for sure come up with extended EAS support- no doubt. But you now might understand why this could take a while.
And besides, the other devices aren't much better here - it all depends on your IT's policy settings. If you're lucky, other devices might pass your specific environment's settings just because they respond to a policy by forged output. Nokia can't. They officially licensed EAS and therefore have to stick to the rules...
Just my 2 cents.
Last edited by tomster; 2010-02-03 at 10:42.