order to use when stopping and restarting BES services

When stopping and restarting BES services in the course of troubleshooting, I found this KB on the correct order to stop services and the correct order to start the services after they have been stopped. From the KB:

The correct order to start the BlackBerry Enterprise Server services is detailed below:

1. BlackBerry Router
2. BlackBerry Dispatcher
3. BlackBerry Controller
4. All remaining BlackBerry Enterprise Server services

The following is the order in which to stop the BlackBerry Enterprise Server services:

1. BlackBerry Controller
2. BlackBerry Dispatcher
3. BlackBerry Router
4. All remaining BlackBerry Enterprise Server services

BES Express installation thoughts

RIM released a new version of their free server side enterprise software in early 2010. There are some big benefits of the new version (Blackberry Enterprise Server Express 5.0 over Blackberry Professional Server Express). Three huge advantages to the new version - 1) you can install it on 64 bit systems, 2) you no longer need the BB Enterprise plan on your devices to use Blackberry Enterprise (though you need BB Enterprise plan to do wireless activation - without it, you need to do wired activation through the desktop software), and 3) the server license is free and so are all device licenses.

You can get the software here:
http://na.blackberry.com/eng/services/business/server/express/?iid=BESX_Software_landing

The install wasn't too different from the previous version of the server software, but what's great is that RIM made a great installation guide and one that included a great screen shot walk-through.

Here's the text guide:
http://docs.blackberry.com/en/admin/deliverables/14335/BlackBerry_Enterprise_Server_Express_for_Microsoft_Exchange-Installation_and_Configuration_Guide--984521-0120054149-001-5.0.1-US.pdf

Here's the screen shot walk-throug:
https://www.blackberry.com/blackberrytraining/web/_content/indexExternal.html?cc=3731382d30323036335f42455358496e7374616c6c&cx=3230393930313031&cl=656e&cg=636f6e6669675f6c6f76655f707572706c652e786d6c

I was setting up BES Express on a Windows 2008 R2 machine with Exchange 2010 on it. The truth is that I had some trouble with the instructions. There were several things that the guide told me to do that I couldn't. I had trouble setting send as permissions to besadmin. I had trouble granting log on locally as a permission to besadmin (option was greyed out). I also couldn't get this command to work (I edited it as appopriate for my domain):
Add-ADPermission -InheritedObjectType User -InheritanceType Descendents -ExtendedRights Send-As -User "BESAdmin" -Identity "DC=,DC=,DC="

So in my case, luckily, I had already created another bedadmin account when my domain was a 2003 domain - but overall, minus the issues on this Exchange 2010 install, which I was luckily able to work around, the new version is a welcome change.

configuring pre-4.0 Blackberries to BES

Yesterday, I was setting up a Blackberry 7290 to use the BES box I had created.  The BB was running version 3.8 of the device software so it couldn't use over the air enterprise activation.  After searching, it was just as simple as reinstalling the the BB desktop software and when prompted during the install - tell it to use a BES/corporate server.  I had already created a user on BES for the user who was on this BB - but I don't know how necessary that was.  It seemed pretty easy upon that install, which was nice.

BES install guide for SBS 2003 or Domain Controller

This content is reproduced for future reference from:
http://www.blackberryforums.com.au/forums/microsoft-exchange/281-bes-sbs-2003-a.html

Gary's BES install guide for SBS 2003 or Domain Controller

1. Ensure the port 3101 TCP is open on the firewall (Outbound ONLY).

2. Create a new user called BESadmin and ensure you create a mailbox. Ensure this user is ONLY a member of "Domain users"

3. Make BESadmin a local Administrator of the server. This is done in AD via the "Built-in" Administrators group

4. Go to Admin Tools on open "Domain Controller Security Policy" and expand the "Local Policies" and "User Right Assignment". You need to add BESadmin to "Allow Log on Locally" and "log on as Service".

5. Open Exchange System Manager and right mouse click on "DOMIANNAME (Exchange)" and select Delegate Control. Follow the steps and add BESadmin as an Exchange View Only Administrator.

6. In Exchange manager expand the servers folder and right mouse click on your server and select properties. On the properties windows select BESadmin and add the permissions "Administer Mailbox Store, Receive As, Send As"

7. Open Active Directory and from the View menu select "Advanced Features". Then go to each user that will be added to the BES and open their properties, go to the security tab and add the user BESadmin and add the security permission "Send As". (This will overcome some MS patches that prevent BES sending emails)

8. Log on as BESadmin and install the BES software, normally you just install "BlackBerry Enterprise Server" as most sites don't use the MDS services (MDS is a much heavier install). Follow the prompts of the install and the server will be required to restart half way through the install. Restart the server and log back on as BESadmin and the install will continue. (Make sure the Connect Test works and the SRP ID etc is validated during the install)

9. After the install is finished open BlackBerry Manager, an error will appear about MAPI client which you can just hit OK. The MAPI setting windows will appear so just add the server name back in and select "Check Name", if it resolves just hit OK and the manager will start.

10. Within Blackberry Manager click on Blackberry Domain in the left column and then the users SERVERS tab in the center section, select your server within this tab and view the properties below. Ensure that "SRP Status:" is Connected (This can take a few minutes the first time so refresh the screen a few times). Once your status is connected you can start adding users.

11. Within Blackberry Manager click on you server name in the left column and then the users TAB in the centre section, just add a user and the click on that user. You will see all the users’ properties and a drop down menu called "Service Access” and select “Set Activation Password” and set a password of “a” for example.

12. Turn on you BlackBerry device and ensure Wireless is enabled. Go into “Options/Settings” and “Time & Date” and set the correct zone and time etc. Then from the home screen go to enterprise activation and enter the users email address and enter the password that was set in step 11. Press the track wheel and select Activate. Within a minute you should get data returned which indicates the process is functioning correct.

Extra

Note: Sites running SBS 2003 premium will need to change the BES "Web Server Listen Port" from 8080 to another available port (e.g. 8090 or 9090) as soon as it is installed. This port needs to be changed as the BES Web Server will be listening on the same port as ISA. To change this setting open Blackberry Manager, select MDS and then "edit Properties" and change the "Web Server Listen Port" to the desired port number.

a. Also ensure you review the IT Policy in BlackBerry Manager. This can be found in BlackBerry Domain > Global TAB > Edit properties. It is recommended that in the IT Policy you go into “Device Only Items” and set “Enable WAP config” to FALSE, this will force user to use the free browser (It uses the internet connection of your BES server). It is also highly recommended that you configure a password policy prior to rolling out any handhelds.

b. If you are unable to activate devices wirelessly you can test your connectivity to Blackberry buy running the following app from the command prompt:
C:\Program Files\Research In Motion BlackBerry Enterprise Server\Utility\BBSrpTest.exe
This will send a signal to BB and wait for a response, it this fails check your firewall settings (open and/or direct port 3101 TCP to you BES server)

c. If you have Domain Admins using BlackBerry devices you may have to run the following script if you are unable to send email for those users devices:
dsacls "cn=adminsdholder,cn=system,dc=domainname,dc=c om " /G "DOMAINNAME\BESadmin:CA;Send As"

making BlackBerry show contents of subfolders

On your BB . . .

From messages, Options, Email Settings, Menu -> Folder redirection.
Make sure whatever folders they want the BES checking have a check mark.

run the setup wizard on Blackberries

I'm still not a Blackberry guy, but . . .

In this particular case, I'm setting up a T-Mobile BB Curve (BB 8300). There is no Enterprise Activation icon. So I troubleshoot and find this:

The tips listed below are items that will help you if you have received an error message while attempting an Enterprise Activation or if you are unable to find the Enterprise Activation option.

• If this device is a "re-activated" device, check the software version. You can do this by going to Options (the wrench), then choosing About. The software version must be at least v4.0 or 2.7 (Java & C++ devices respectively). If your software does not meet this standard, you must upgrade it. The software is device specific and is generally provided by the wireless carriers support pages.
• New devices and re-activated devices all need data service, this data service generally accompanies a phone service (even if the phone portion isn't going to be used). You must always be sure to activate your phone with your wireless carrier. Most carriers have some type of activation process you will need to follow. An example would be Verizon, who requires that you dial *228 and follow the prompts to program your new phone.
• Registering on the data network is the next step. You can do this by going to Options > Host Routing Tables, then clicking in on the scroll to receive a side menu that will give you the option of "Register Now". Choose this option by clicking on the scroll, and when the registration is complete you will receive a message in your Messages folder that will indicate that it is finished.
• Check with your wireless carrier to ensure that you have applied the correct data package to your device. A good example of this type of situation is T-Mobile, who requires a special Enterprise Package which enables you to use a Blackberry Enterprise Server.

In addition, as per some other troubleshooting I did on a BB 8800, you really should run the setup wizard on on your BB's home screen. Most of it is meaningless, but the last step asks if you are going to run enterprise activation. For this 8300, I told it I wanted to use Ent. Act. and it gave me the appropriate screen. However, it didn't work. Perhaps that's becuase right before that, I followed a step from the list above and called T-Mobile to request the Enterprise package for this device, and they said it would be active 10 minutes to 48 hours from that point.