So far everything is great, I’ve seen some great sessions and met up with some great people.

I finally met jsanders, knottyrope (who’s a lunatic) and a bunch of great 3101 people. Got some great business cards, and look forward to getting some more tomorrow.

I’ll be Tangoe’s booth , I will be posting booth number soon. Come over and lets talk BlackBerry.

Looks pretty solid, I just downloaded the beta test and look forward to messing around with it. I hear release date this year end time?

So generally when you have an agent that wont restart 10 times, there is no way to get the agent to restart. Reboots, restarting to dispatcher etc: The only way to get it to restart is to go into the bes logs, and rename the bes logs, like OLD_BES_LOG. The way we were able to figure this out by looking at the BES log and seeing at the end of the log it would actually say END OF LOG.

So looks like I’m going to be meeting up with some port3101 peeps at WES, look forward to meeting some people and seeing how they run their environments.

Taken from

http://na.blackberry.com/eng/deliverables/7335/New_BES_features_50_656131_11.jsp

Support for Microsoft SQL Server 2005 Express Edition

BlackBerry Enterprise Server version 5.0 supports Microsoft SQL Server 2005 Express Edition. The setup application can install Microsoft SQL Server 2005 Express Edition if your organization’s environment does not already include a database server.

Support for Windows Server® 2008

BlackBerry Enterprise Server version 5.0 supports Windows Server 2008.

Hell fucking yes!

So RIM came in today and talked to us about bes 5.0 for about three hours. I am going to say, it is getting really exciting, the current package is looking like it is the gold package they are going to go with.

More to come

Love this guy

http://unified-communications.blogspot.com/2008/08/how-to-configure-your-bes-server-to.html?showComment=1233953220000#c4217927056315361416

Going through plenty of BES logs lately, I have noticed a pattern that I am going to try to explain briefly. It seems that people don’t understand why it is a bad idea that a large percentage of your messages are being delivered via rescan, and not by notification. I am going to try to explain this in more detail.

• Notification– This is when the BES See’s that a new message has gone into your mailbox, it then sends the message to your handheld through the rim infrastructure and you get it on your handheld.
• ReScan– This is when BES does a rescan of the users mailbox every 15 minutes or so, and then notices that a message has not been marked sent to the handheld, and then is sent to the handheld.

Now obviously, the notification should be the one that always happens, but with the exchange environment getting overloaded, sometimes things need to get picked up with the rescan. Now the problem we get into, is when companies start to depend on the rescan. Then you start seeing things like mail clumping and latency issues. There is a BRK that you can run that can assist you with this information is messageflow. The general accepted rule is that your rescan % should not be more then, at the very worst of 20%, I would even say 15%. So no more then 20% of the total messages sent to your BlackBerry should be delivered via rescan

I’m so happy that in BES 5.0 they are totally changing how they do software config’s. I have such a huge problem with how confusing and inconsistent software config’s are. Let me give you an example. Earlier, in one of the test enviroments we have at my office, one of the developers created a software config. Now he assumed that all you have to do is add the files to the directory and then load that directory through the BES.

How silly of him…

First you have to index the files, then you have to make sure you don’t have duplicate names of the directory’s. And then finally you have to make sure that none of the files in the directorys have the same name, or the new software config will not show up.

BES 5.0 april 1st?