Does anyone know which BES version will support Exchange 2010?

__________________

I'm guessing 4.1.8 (or whatever SP is current at that time for 4.1.x) and 5.x will be supported with it.

That said, as of now, 2010 should act the same as 2007 does with BES.

__________________
http://blog.port3101.org/hdawg/

The views expressed by me on Port3101 and its affiliated sites are my own and do not necessarily reflect the views of my employer.

any word on this? i'm inclined to believe that it wont work at all currently because doesnt 2010 drop cdo/mapi completely in favor of web services (so bb will act more like active sync then).

__________________
Two months ago, I saw a provocative movie on cable TV. It was called The Net, with that girl from the bus.

I'm not sure if anyone else has tested, but from reading other forums a few weeks ago, it had not been done successfully... although it was expected the RTM version of E14 would work. Nevertheless, official support won't be until next year (most likely 5.0 SP2 and 4.1 SP8). Keep in mind that its not even released yet, so I don't think it's reasonable to expect support until the WES timeframe (Feb-May, give or take).

__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.

RIM stated on a call with us that 5.0 SP1 would work with 2010 CAS.

I tried using BES 5 with the latest Exchange 2010 build a few weeks ago in a test environment where I test email routing using serial bypass, and I had a ton of problems - notification from Exchange 2010 to BES was flakey (even after upgrading to the latest MAPI subsystem on BES) and I had a ton of Delayed States of Notification. Also, when I tried to create a new calendar appointment with a resource mailbox attached or with multiple recipients, it never got recorded in the Exchange mailbox but there was no error in the BES logs or eventvwr on BES that I could see related to it. This leads me to believe that MS has changed some of the underlying API interfaces and that BES 5 will need to be updated to match.

__________________
Jason W. Eckert

They stated v5.0 SP1 again on a call today. So will will see hopefully soon enough.