Quote:
Originally Posted by b52junebug
is anyone else being subjected to a Good Link and BES environment? What gives with Goodlink anyway.. and what are you feelings about the Good interface.
|
Yup - I administer both here. We have Good Mobile Messaging and Blackberry Enterprise Server.
The Goodlink was the first installation, since I was more of a mobile PC kind of guy, so I pushed for it. It works OK, but has some definite drawbacks. Still, for all those non-blackberry people it does the trick. I finally changed my own device over to a Blackberry 7130, and never wanted to mess with Palm or Windows Mobile again. Of course, now I have the 8100 Pearl, and love it even more.
I don't have any issues with the Goodlink Management Console. It works, but that's about it. I do have issues with the way the Good Client software actually installs and takes over devices. Most people who had Treo's previously got totally confused when they ended up with two contacts lists. Also, on Windows Mobile Phones, the Good software doesn't completely take over from the Pocket Outlook - things like alt-clicking to select SMS Contact didn't work from the Good Software. The one thing Good has over Blackberry is the Good Online Portal. I can go and check a devices network connectivity for the last 24 hours. I can't do that with Blackberry. So when the CFO calls and says "I didn't get an important email yesterday! We missed a deadline and now it is going to cost us $50,000 for failing! Why did your server screw up?" I can actually research and tell him that his phone lost network connectivity. It had nothing to do with the server. Instead of guessing....
The BES is a much more complicated beast, and because of that, I love it and hate it. For a new BES Admin, it can be rather daunting. I will pick Blackberry over Good any day though. Mainly because of the support issue. Right now, it is nice to tell everyone "buy a Blackberry, or you can't use the BES" We won't install Blackberry Connect devices here - they end up using the Good Mobile Messaging Server. That may change once this "virtual Blackberry software" is ready to ship.
Good works, and everyone has there Internet and applications on there handhelds working fine. One of the problems I have with BES is that I had to disable Internal Connections in the policy. That little piece, when enabled (which it is by default), gave every Blackberry the ability to connect to all internal network devices. I really don't want these handhelds to be able to connect to the payroll server, central router, etc... The only downfall to disabling the Internal Connections is that it breaks some applications on the Blackberry devices. I.E. Google maps, Telenav, Blackberry Messenger, etc... It's weird, some things work. Others don't.
To put a little perspective on it - I am the only admin for both the BES and the Good Mobile Messaging. We have 32 devices on the GMM, and 157 on the BES. I have people changing from the GMM over to the BES every other week....
Spydertech