Friday, October 9, 2009

How a Turkish mobile provider's BlackBerry firmware helped save my BlackBerry Bold.

Hello All,

I've been dealing with dropped calls and signal issues since I initially switched to AT&T in Dec 08. Surprisingly, the problem was the device (BlackBerry Bold) & 3G, and not AT&T. Now, I'm a big of BlackBerry technology, but it's to blame! The Bold is a great device except for one thing, 3G. It seems the 3G driver has a problem switching cell towers in heavily used areas and other random places. So, I would experience dropped calls (many places) and "lock" on EDGE or GSM (heavily used areas) which a quick reboot would fix. Thankfully the Bold reboots quickly (I use an app called QuickPull). The reason for the post was it looks like I finally found a more permanent "solution" to this issue, disabling 3G. I'll explain how later on.

Before I switched to AT&T I tested out the service with a BlackBerry 8820 running OS 4.2 during the end of 2008. It worked great. So, I bought a Bold and switched to AT&T and then the problems started. Initially I thought this was "normal" AT&T service people complained about. Then I noticed a pattern. Certain areas would cause the "problems" above. So, my resolution testing began.

- SIM swap did nothing (that was the 1st and last idea by AT&T support I listened to).
- borrowed another Bold, same issues.
- retested with the 8820 and loaded 4.5, no issues.
- ran a variety of cutting edge (unauthorized) BlackBerry OSes on my Bold in attempts to fix the dropped call problem. They varied from Singapore, Latin America, & UAE. All are developed by RIM, but released to different mobile phone providers for support. AT&T supports 1 version of the BlackBerry OS currently, and it has problem. So, I would load the latest BlackBerry OS I could find and see what would happen.

And then I finally had the idea, it could be the Bold & 3G. So, AT&T did release an OS with the ability to select "2G" or "2G/3G" networks, but due to a serious bug, it was pulled from the market days after release. I decided I didn't want to run that, but finally.... another OS ( with this capability was released by a Turkish mobile vendor, AVEA. So, I'm running it and so far it's been working as I hoped.

This is the URL that listed it.


Tuesday, October 6, 2009

Windows 2008 R2 and Exchange 2007? Microsoft says no.

Hello All,

Anyone who has not deployed Exchange Server 2007 and wants to do it on Windows 2008 R2 (it'll be launched this month), the answer is it is NOT supported. Not a big deal, since I would just wait a bit longer and have the benefits of I suspect to be the hands down best Exchange version yet, Exchange 2010. If you are wondering, 2003 is still the king. Some articles discussing this R2 rejection: Windows IT Pro and the Microsoft Exchange Team postings.

Server OS Support
Exchange Server 2003 supports Window Server 2000, Windows Server 2003, & Windows Server 2003 R2. (3 OSes supported)

Exchange Server 2007 supports Windows Server 2003, Windows Server 2003 R2, & Windows Server 2008. (3 OSes supported)

Exchange Server 2010 supports Windows Server 2008 & Windows Server 2008 R2. (2 OSes supported currently)

Microsoft decided against QA and supporting Exchange 2007 on Windows Server 2008, which is understandable since supporting 4 OSes is a time consuming process and 2010 is getting launch within the month. So, wait a little longer, and try and deploy Exchange Server 2010 once your eco-system is supported (e.g. BES, GFI, AppAssure, Backup Exec, etc).