Another hot tidbit is that GMM is officially in the roadmap for Good Mobile Messaging support.  The enterprise class messaging platform is initially going to use the push notifications currently in use by select iPhone applications.  One amazing feature of this will be the ability to have two… count ‘em 1+1… enterprise based messaging suites.  One will utilize Good and the other will use Exchange ActiveSync.  Who should this be huge news for?  IT admins who need to monitor a test environment as well as their production environment, sniveling assistants who manage their master’s contacts, calendar, and mailbox size, and plain old people who might be running a home/personal exchange server but also need access to their corporate mailbox.

Now for a feature request if I may… How about Good Messaging integrating a client which has the ability to sync only one aspect of the mailbox, ie, calendar only…  This way, the super busy executive won’t have to compromise their mail to have some one wirelessly manage their calendar.

Ok, so patching any server is never just a walk in the park… but it’s not supposed to be the sort of thing which has to be attempted more than once.  Each failed attempt makes “higher ups” more and more wary of the competency of the IT staff.  So what types of concerns are there with the BES patch process?Well it’s not so much the process… actually, it’s not the post-patch issues.  Once patching has occurred, the BES needs to make connection with each and every device to push out new service books and “re-scan” the users’ mailboxes.  While this process really isn’t all that complicated, the time it takes to re-connect with each device is significant.  This time is increased exponentially when there’s a hefty amount of users.

Let’s just say an organization has about 2000 users on a single BES which they’d like to patch to say 4.1.6 or 5.0.  As it stands, post-patching connectivity would probably take in the neighborhood of about a day or two.  What self-respecting business has that much time to have users without connectivity?  So as a word of advice… When implimenting a new BES environment, go with the highest possible version to delay having to patch.

Incident for BlackBerry PIN to PIN service for subscribers of “The Americas

Network”

Impact: BlackBerry subscribers may experience delays in receiving PIN

messages and may receive an “x” when sending PIN messages.

Incident Window Start Date and Time: 23 July 2009 14:46:00 (EDT).

Duration: Ongoing

Seems like BlackBerry’s PIN messaging went down for a short while last night.  This would affect all those users wishing to send super-secrect messages…  Sorry guys, but it looks like you’ll have to learn how to use good ol email to communicate.  RIM still seems to be ironing out some kinks with their Network Operations.  Several system wide outages over the past few months could mean nothing or everything depending on how your organization uses their services.  It can be easy to get lured into the ease of deployment, the all-in-one solution, the ease of troubleshooting ect… But when you throw an outage here, an outage there… it quickly becomes an IT nightmare.  One unexpected outage can easily become 50-100 phone calls and emails.  As for other enterprise class wireless messaging solutions, I have yet to see the same sort of security issues.