Internet Related/Filtering/Firewall Thread, BES Express 5.0.2 with Exchange 2010 Rant - First Edition in Technical; BES Express is frankly shocking, I thought RIM may have improved after the travisty that was BPS but I think ...
BES Express 5.0.2 with Exchange 2010 Rant - First Edition
BES Express is frankly shocking, I thought RIM may have improved after the travisty that was BPS but I think that they are even worse.
Does RIM employ only cyfilidic howler monkeys as programers or must they all undergo a full labotomy to get their jobs.
First off registering to get BES Express in New Zealand is impossible, I'm not exagerating, it actually is. Initially attempting to register with the companies address resulted in being told that the road did not exist. It has only been there for the last 60 years so I guess its a bit recent for them. Issue two was encountered when using a road that was accepted (100+ years old) and this is where the imposibility comes in. When you click submit it wipes the city field then returns an error that you must include a city. Firefox, Chrome, IE, it made no difference, neither did attempting different cities.
Solution: register using an Australian address copied off their contact page, they at least know that their own address exists.
Issue two, not really a fault but rather an annoyance is their rubbish slow servers, 100k a second turns a 560MB download into a long wait.
Now to the install and after installing the many prerequsites manually and doing loads of configuration manually (have they heard of an installer wizard?) you finally get to the install.
Suprisingly it installed without error, I'm not saying that there were not problems or that it worked but it did not make any error messages. After the install finished I got a lovely page telling me that I now just needed to go to this web page to continue configuring it. Problem, the webpage does not work, no helpful error, nothing, just a timeout.
Re-reading through the common issues it turns out that BES in its infinite incompetence does not handle multiple network cards well. It is supposed to be put on a server and it has problems with multiple NICs, who are these people. So solution found, push the right interface up to the top of the bindings list in networking advanced properties and it should work... Should, as it fails in the exact same way.
More internet searching and attempts to find solutions eventually reveil that BES fails when either of two Windows hotfixes are installed. This is a known issue with no fix timeline but thats fine the workaround is just to remove them. They are unimportant only patching kernel escilation issues, its not like you would want your server to be pretected from complete compromise anyway. Remove these two and restart the server, is the problem solved? No. Same issue.
At this point I'm looking to the free support incident as the only way to even get this mad bit of overhyped java running and log into the support portal, go to make a support incident and the button is greyed out. Really, how do I raise an incident about not being able to raise an incident. It makes my head spin.
Religated to the fact that I would have to make this steaming pile of filth run all by myself I continued the fight. Eventually comming to the realisation, after reading through 100 or so pages of error logs that BAS (the blackberry administration service) can't connect to the SQL server.
The installer defaults to using dynamic ports and to strive for a problem free install I had left the defaults. My mistake, turns out that that does not work if there are any other instances of SQL on the box at all. First I needed to make sure the SQL Browser service was running then after configuring the SQL instance to use the default port on the all ips instance and removing the setting for dynamic it finally kicked into life.
The above does not even include the need to manually setup firewall rules for it or the hunt for the right CDO with MAPI compnents to install.
So after wasteing only five hours of my time it was installed, I have still to find out if it even works with the Blackberries.
I just want to know how they get away with releasing such junk, the coding level would even make an educational software developer blush in embaresment. How have the developers not been hunted down and delt with by angry IT workers from their local area.
The mind boggels and I can only look foward to the day when all of their Blackberries are replaced with something that uses Activesync, at this point I would even settle for iPhones.
Has BES made anyone else criminally angry lately or is it just me?
Last edited by SYNACK; 18th November 2010 at 09:42 AM.
Nah, it's not just you, I had a similar experience last year installing the 'free, single-licence' version of BES 4 (or whatever). The first bit that confused me was, having read on their Marketing blurb that it doesn't need a server of it's own and can sit on your messaging server, and having done that, then being told by their support people that it can't sit on the messaging server but has to have its own server. So I had to turn round and build a whole new server (lucky we had one spare, huh?) just for one person. Admittedly, that person was the Head, but even so.....
It just got worse from there on. I found the support were great at the big stuff, but not so hot on the little details, like setting the handset to 'Enterprise' mail and so on.
The easiest part was getting my GFL to open up the port on our router, and that's what I was expecting most trouble with.
I've downloaded BES Express and I was meaning to get round to installing it sometime........probably when someone on the SLT p*ss*d me off enough to tell the Head that all the SLT can now be Blackberried, too.
But, having read your post, I think I'll forgo that momentary, fleeting pleasure...........it don't seem worth it.
Not so much expertise to add this, as just joining in on the rant. I've got a couple friends who have invented new words to describe that software. Thankfully those phones are in short supply where I work. For the few people that have them, there only option is to sync calender and contacts from their computer. The standard work phone here in the office are Droids.
I still can't figure out why Black Berry phones need this horrible front end to interface with Exchange when Apple iOS, Droid, and Windows Mobile do it right out of the box.
"Hate" is not too strong a word for my feelings after having to set up a Blackberry server recently - what a horrible product it is! After reading the OP I definitely will not be looking at this upgrade in the near future...