[nsmith_62]

This is probably a very dumb question but, am I right in assuming if I update the CDO.dll version on the BES (3.6), I will need to update it on the Exchange 2003 servers?
Desktop services are about to rollout Outlook 2003 to end users and I want to try and avoid these calendaring issues.
The RIM docs (that I have found) only talk about upgrading it on the BES....

[cames]

I think the main thing is to ensure the version of the CDO.dll file on the BES is the same (or newer than) the version on the exchange servers.

[greywolfe]

CDO versions depend on your exchange and outlook setup, not the BES version.

For Exchange 2k3 and Outlook 2k3, you will require version 6.5.6980.3 or above on both Exchange AND the BES server. Just make sure they are the same version.

[nsmith_62]

No I understand that CDO.dll is determined by exchnage and Outlook client versions, juts wasn't sure if Exchange and BES needed to 'hotfixed' together - but I guess from your reply that they do.

thanks Greywolfe

Neil

[greywolfe]

Rule of thumb for Exchange hotfixes in a BES environment is to always apply them to both. In the case of cdo hotfixes, apply to Exchange first, reboot it, then copy the new cdo file over to the bes server and register it.

[jibi]

...however, if you just want to install ESM 2003 SP1 on the BES and be done with it until you upgrade your Exchange environment, there would be no issues there either, as CDO is supposed to be backwards compatible... in this case, the OS of the BES would determine your ESM installation. if you had Windows Server 2003 for the BES, then you'd install ESM 2003. if you were on Windows 2000 Server for the BES, then you'd install either ESM 2000 or ESM 2003 - your choice.

[greywolfe]

Well having the cdo in the exch/bin dir on Win2k3 apparently only works with BES 4.0 sp2? You can have it in both directories but I believe it only becomes mandatory in sp2?

[jibi]

correctomundo. i've just added the extra little step in my installation documentation to put it in /bin and /system32 - but i register it in the latter locale only. i sure wish they'd make up their mind. in related hesaid/shesaid news, i was told that updating JRE was supported and just fine to do, however, any of the BES installations or SP updates or HF patches always report post-install that it could not detect a supported Java Runtime Environment - go figure.

[nsmith_62]

Ok, so just to be clear
everything is running on win2003
our exchange environment is ex2003 (no SP)
we have BES 3.6 and BES 4 (BES 3.6 users will be migarted to BES4 over the next few months),both BES platforms have ESM2003 installed (no SP)
users are currently on Outlook 2000 but again will be migrated to Outlook2003 over the next few months.

So, will it be ok to just upgrade the cdo.dll to 6.5.6980.3 on the BES 3.6 and BES 4 servers for now (in both /bin and /system32 and only register it in the latter),with a view to updating Exchange servers in the near future?

thanks for your help guys, much appreciated