We are doing a HUGE migration and upgrade at work right now. Everything is moving from Server 2003, Exchange 2003, and SQL 2005 to Server 2008R2, Exchange 2010, and SQL 2008 R2. So far everything has been going well, then I started to play with blackberries. We only have a few so buying the full out BES wasn't worth the money so instead we went with a software called "Notify Link." Basically BES but 3rd party. Long story short, it sucks and we wanted to switch. Since BESX is free we are using that.
Now I recently did a install of BESX on a client who was doing a similar migration (though they were already on Exchange 2010) and it went fine. On ours we are having MAPI issues during the install process. I called RIM about the problem and they stated that the Microsoft Messaging API and CDO download v1.2.1 was too new for Exchange 2003, and suggested that I find my Exchange 2003 disks and just install the Exchange management console for the correct MAPI version. Well I did this, BUT, Exchange 2003 is not supported at all in the 2008 R2 environment (Windows doesn't even let you install it). I also tried copying the mapi32.dll and cdo.dll from the exchange server to the system32 folder of the BES server, registering them, and still no dice. So I am kinda stuck here. I want to upgrade our exchange first (because it would make the BES part easier) but this is getting shot down because there are some squeaky wheels that want their blackberries working now instead of the email update.
Suggestions?
Now I recently did a install of BESX on a client who was doing a similar migration (though they were already on Exchange 2010) and it went fine. On ours we are having MAPI issues during the install process. I called RIM about the problem and they stated that the Microsoft Messaging API and CDO download v1.2.1 was too new for Exchange 2003, and suggested that I find my Exchange 2003 disks and just install the Exchange management console for the correct MAPI version. Well I did this, BUT, Exchange 2003 is not supported at all in the 2008 R2 environment (Windows doesn't even let you install it). I also tried copying the mapi32.dll and cdo.dll from the exchange server to the system32 folder of the BES server, registering them, and still no dice. So I am kinda stuck here. I want to upgrade our exchange first (because it would make the BES part easier) but this is getting shot down because there are some squeaky wheels that want their blackberries working now instead of the email update.
Suggestions?