Would like to bring to your attention a known issue with the ActiveSync on the current build of the Verizon Thunderbolt. There is a bug not allowing the Calendar to sync properly with an Exchange 2010 server. There is already a current google support thread.
http://www.google.com/support/forum/p/Google+Mobile/thread?fid=7dfa7586687b22d400049ebbd4e05e0a&hl=en
Please provide a fix to allow me to fully use the device..
Well HTC's official response is that they don't support ex2010 or they are stating its an issue with Android. Not sure where the issue is, other HTC phones work without an issue with our Exchange 2010 Server. Incredible and HTCEvo all work no problems.
That is one of the worst stances I have ever seen. Exchange 2010 has been out for a while now, and my EVO works just fine with our Exchange 2010 server so why shouldn't my Thunderbolt? Let's hope there are enough support calls that the next OTA will have some form of a fix for this, because it is really, REALLY annoying.
BTW in that same thread, a Google employee states that email on a HTC phone is done via a HTC email client and NOT androids vanilla client. So any issue would be on HTC's software. I know my EVO and Incredible worked just fine on the same server, so they can't give us a line about them not supporting it because every other HTC phone i've owned does.
I have to say that I expect more from a company that touts itself as having above average products. This stance is a complete cop-out, my Incredible worked with exchange 2010 SP1 just fine, we have EVO's that work just fine as well so this stance of not supporting exchange 2010 is complete crap - get to work and fix my issue so that I have a fully functioning phone! I paid good money for this phone and I expect a fix
Well said. If they even tested this they would see its a issue and work to resolve it. Its easy to replicate. I think we all know they are aware of the issue and *fingers crossed* lets see what happens in the upcoming OTA. I for one am using the Google gmail calender sync and using that for the interm. Works ok but I prefer having my exchange calender directly.
HTC when are going to address this issue and tell your loyal customers you are at least "Working" on a fix, this would make me feel better than staring at a wall waiting for a response. This is a huge issue and I can not recommend a phone to the 100 people that I work with and support that is not 100%. I can look past under powered batteries for the phones, but this issues is unacceptable.
I have had the same issue. I removed the account and added it again and it is now working. But for how long. I do have the full version of Touchdown and it works fine. At least for the last week, it has been working. I use google sync anyway to keep my google calendar and my OWA calendar sync'd. I prefer using the exchange calendar as the primary (until I retire soon) to keep the updates on the phone, my blackberry and my office exchange account up to date. The google sync only works when the computer is on and outlook is running on my office desktop.
I tried that, I also tried a factory reset a few times an came up snake eyes. I still await their resolution of something other than "We don't support Exchange 2010"
I found a solution to this that worked for me. Go into Outlook and view your calendar items in list view, highlight them all and add a category. Then remove the category from all items. After doing this my calendar syncronized on the first try. Whoooo Hoooo!
Just gave this a try does not seem to sync any of my events. My sync error went away for the first sync, but no events ever were downloaded from exchange.
*UPDATE* it actually did sync 1 all day event I created today. I created this event in Outlook after the Category suggestion.
It seems to sync new events no problem, its mainly older ones from what I am seeing that don't sync.
This seems to have fixed the issue (for now) on my calendar! Good show! I was able to sync my old events as well as new events. I have tested and it is pushing both ways from the phone to exchange and vice versa.
Thanks again for sharing this fix!
~Jake