[ktd]

Pulling my hair out - I've spent probably 12-15 hours on the phone with RIM this week, everyday it's a different guy, telling me a different theory. I've run our BES for about 8 years, knock on wood, no real issues, this may be the first time i've had to work a significant case with them, and to say i'm not impressed is an understatement.

Current environment is:

BES 4.1.7 running on windows 2000
Exchange 2003 running on Win2003
150 handheld users

Moving my exchange to 2010, so i'm trying to move my BES users first, and then the exchange upgrade will follow.

Installed a new Win2008 R2 server with SQL 2008 R2 on it
Installed mapi and cdo 1.2.1
Installed BES 5.0.4
Installed the transporter tool
Using the same BESAdmin service account on both 4.1 and 5.0

All installed without issue.

Transported myself from 4.1.7 to 5.0.4 - no errors. On 5.0.4, my user is there, and all information is populated correctly, Mail flows, but delayed - anywhere from 2 minutes to 20...

Any help on my BES issue would be appreciated - or, any help on my RIM issue would be appreciated - how do i light a fire under these guys... Is their support group always this poor?

Thanks.

Danny

[Escorts]

How to Configure Perfmon to troubleshoot mail delays in an Exchange 2010 Environment.
KB Article : 25337

[ktd]

That's what they're having me do now - running perfmon. The exchange version is 2003, not 2010. But, exchange is running fine, and i think the perfmon will bear that out. The 4.1.7 box which is accessing the same exchange server will deliver the messages to it's users (149 users) within seconds, while the 5.0.4 box with 1 user (me) takes anywhere from 2 to 20 minutes.

Danny

[Escorts]

Check the Windows Event Log. A messaging server in the Microsoft Exchange environment may be experiencing an issue or event resulting in non-responsive threads.

[smoothadmin]

Originally Posted by ktd

Pulling my hair out - I've spent probably 12-15 hours on the phone with RIM this week, everyday it's a different guy, telling me a different theory. I've run our BES for about 8 years, knock on wood, no real issues, this may be the first time i've had to work a significant case with them, and to say i'm not impressed is an understatement.

Current environment is:

BES 4.1.7 running on windows 2000
Exchange 2003 running on Win2003
150 handheld users

Moving my exchange to 2010, so i'm trying to move my BES users first, and then the exchange upgrade will follow.

Installed a new Win2008 R2 server with SQL 2008 R2 on it
Installed mapi and cdo 1.2.1
Installed BES 5.0.4
Installed the transporter tool
Using the same BESAdmin service account on both 4.1 and 5.0

All installed without issue.

Transported myself from 4.1.7 to 5.0.4 - no errors. On 5.0.4, my user is there, and all information is populated correctly, Mail flows, but delayed - anywhere from 2 minutes to 20...

Any help on my BES issue would be appreciated - or, any help on my RIM issue would be appreciated - how do i light a fire under these guys... Is their support group always this poor?

Thanks.

Danny

You have the order of moving the users wrong. You need to first get your Exchange 2010 up and running and start the migration between Exchange 2003 and 2010, then you need to preferably setup a separate server for BES 5.0.4 and start the migration from 4.1.x to 5.0.x as you migrate the mailboxes over to Exchange 2010 SP3 RU1.