Blackberry Enterprise Server 5.0

Here is most of the documentation you need to install and administer the BB 5.0 server:

Server 5.0 Upgrade Paths:

http://na.blackberry.com/eng/services/server/upgradepath.jsp

Server 5.0 Intsallation Support:

http://na.blackberry.com/eng/support/software/serverinstall.jsp

  

Server 5.0 Upgarde guide:

http://docs.blackberry.com/en/admin/deliverables/7315/index.jsp?name=BlackBerry%20Enterprise%20Serve...=

BlackBerry Enterprise Server Resource Kit Docs and Files

https://www.blackberry.com/Downloads/entry.do?code=D736BB10D83A904AEFC1D6CE93DC54B8

http://docs.blackberry.com/en/admin/subcategories/?userType=2&category=BlackBerry%20Enterprise%20Ser...

Server 5.0 Admin Tutorial:

http://docs.blackberry.com/en/admin/deliverables/7466/flash_start.html

All Server guides:

http://docs.blackberry.com/en/admin/?userType=2

Exchange 2013 CONF

Exchange CON Keynote Session: Key Issues in Managing Exchange
http://www.onlinemeetingnow.com/seminar/?id=bcbe605f0e

Exchange CON 2013 Breakout Session 1: MS Exchange Storage Managment Strategies
http://www.onlinemeetingnow.com/seminar/?id=dcbef9578a

Exchange CON 2013 Breakout Session 2: Making Highly Available Exchange Deployments Highly Available
http://www.onlinemeetingnow.com/seminar/?id=082a345494

Exchange CON 2013  Breakout Session 3: Backup & Security Strategies for MS Exchange in 2013 and Beyond
http://www.onlinemeetingnow.com/seminar/?id=60f79933b7

Exchange CON 2013 Breakout Session 4: Best Practices for Keeping Exchange Healthy
http://www.onlinemeetingnow.com/seminar/?id=fefb258c4e

Blackberry Collaboration Service does not stay started

In this post i will discuss about an issue which i have faced today and how i have fixed it.

I have installed a windows media package and restarted the blackberry enterprise server. After the server restart in the blackberry stand by server, the blackberry collaboration service does not stay started. Even though manually i have started the collaboration service, it stops again.

I have checked the BBIM logs on server and found 

<DEBUG>:<LAYER = BBIM, [BBCS] Invoking remote OCSC method, configureConnectorProperties, by sending request:>

From BAS Console, i have changed the listening port for the server instance BBIM from 65061 to 65063

Blackberry Solution Topology > Blackberry Domain > Component view > Collaboration > Edit (BESServer_BBIM_InstanceNumber)

But it didn't work, then i have reverted the changes back. (Changed the port to 65061)

From command prompt i ran netstat -abn which showed me the list of listening connections with the services in which OCSConnector.exe is not listening to 65061.

I have restarted the Blackberry Controller Service, again i ran the netstat command and found the below info

  TCP    0.0.0.0:65061          0.0.0.0:0              LISTENING

 [OCSConnector.exe]

I have determined that the BlackBerry Collaboration Service could not start due to a port conflict.  By running the netstat command i am able to determine that port 65061 was currently bound to the BlackBerry Controller.  To resolve this issue i have restarted the BlackBerry Controller service first.  I have verified that the controller was using a different port this time and i was then able to successfully start the BlackBerry Collaboration Services.

Therefore I conclude that when the server was restarted after applying the windows patches the Controller service happened to grab the port that the collaboration service needed causing the conflict.  Restarting the controller caused it to use a different port allowing the collaboration service to use the port it required.

Reference Article: KB32042

Blackberry Enterprise Server Resources

Here in this post, you will find various blackberry resources which will help you in your administration.

Blackberry Enterprise Server 5 Administration

BES10 Tutorials

Blackberry Web Based Training

Introducing the Blackberry Business Cloud Services

Blackberry Cloud Service Overview Pages

Tutorial - Migrating from Hosted BlackBerry Services for Microsoft Exchange Online to BlackBerry Business Cloud Services 

Tutorial - Administering BlackBerry Business Cloud Services

Blackberry Cloud Admin Guide

Lot of Information on Blackberry Cloud Services

Blackberry Resource Kit

Blackberry Calendar is not in Sync with Outlook Calendar

Problem Description: 

Blackberry user is facing the issue where his blackberry device calendar information is not synchronizing with Outlook calendar.

Resolution:

 

Check the below settings

• Go to Calendar folder
• Click Options
• Click Calendar Options
• Calendars: Desktop
• Click on Desktop -> Appt Color -> Wireless Sync -> Yes
• If the option is already Yes

Run the RSET command

Go to Calendar (don't highlight anything) options -> General Options -> then type RSET and it will pop up with a box then click YES then it will delete the calendar folder and download a new one from server and it is populated in 20 minutes.

Send Option is missing when Blackberry device is connected to Desktop Manager

Problem Description: 

Send option is missing when user tries to reply or create new messages from Blackberry device, when the device is synced through Desktop Manager.

However able to perform the forward operation on Blackberry device.

Resolution:

• Delete the service book Desktop [CMIME] on Blackberry device and resend the service book from BAS Console.
• User will be able to see the send option when the device is not connected to desktop manager. Again when Blackberry gets connected to Desktop Manager, Send Option goes missing.
• Run a repair of the Desktop Manager, perform a clean Un-installation of Desktop Manager, Restart the desktop and Re-install.
• Connect the Blackberry device to Device Manager and generate new encryption key under E-mail settings.

Exchange 2010 SP3 Rollup 2 & SP2 RU7

Yesterday the Exchange Team released Rollup 2 for Exchange Server 2010 Service Pack 3 (KB2866475). This update raises Exchange 2010 version number to 14.3.158.1.

Here’s a list of fixes contained in this Rollup:

• • 2837926 Error message when you try to activate a passive copy of an Exchange Server 2010 SP3 database: “File check failed”
  • 2841150 Cannot change a distribution group that contains more than 1,800 members by using ECP in OWA in an Exchange Server 2010 environment
  • 2851419 Slow performance in some databases after Exchange Server 2010 is running continuously for at least 23 days
  • 2853899 Only the first page of an S/MIME signed or encrypted message is printed by using OWA in an Exchange Server 2010 environment
  • 2854564 Messaging Records Management 2.0 policy can’t be applied in an Exchange Server 2010 environment
  • 2855083 Public Folder contents are not replicated successfully from Exchange Server 2003 or Exchange Server 2007 to Exchange Server 2010
  • 2859596 Event ID 4999 when you use a disclaimer transport rule in an environment that has Update Rollup 1 for Exchange Server 2010 SP3 installed
  • 2860037 iOS devices cannot synchronize mailboxes in an Exchange Server 2010 environment
  • 2861118 W3wp.exe process for the MSExchangeSyncAppPool application pool crashes in an Exchange Server 2010 SP2 or SP3 environment
  • 2863310 You cannot send an RTF email message that contains an embedded picture to an external recipient in an Exchange Server 2010 SP3 environment
  • 2863473 Users cannot access Outlook mailboxes that connect to a Client Access server array in an Exchange Server 2010 environment
  • 2866913 Outlook prompts to send a response to an additional update even though the response request is disabled in an Exchange Server 2010 environment
  • 2870028 EdgeTransport.exe crashes when an email message without a sender address is sent to an Exchange Server 2010 Hub Transport server
  • 2871758 EdgeTransport.exe process consumes excessive CPU resources on an Exchange Server 2010 Edge Transport server
  • 2873477 All messages are stamped by MRM if a deletion tag in a retention policy is configured in an Exchange Server 2010 environment

In addition to these fixes, this Rollup also includes a fix for the security issue described in Microsoft Security Bulletin MS13-061.
Notes:

• As of Service Pack 2 Rollup 4, its no longer required to disable/re-enable ForeFront Protection for Exchange using the fscutility to be able to install the Rollup properly. However, if you want to remain in control, you can disable ForeFront before installing the Rollup using fscutility /disable and re-enable it afterwards using fscutility /enable;
• If you want to speed up the update process for systems without internet access, you can follow the procedure described here to disable publisher’s certificate revocation checking;
• If you got a DAG and want to properly update the DAG members, check the instructions here;
• Rollups are cumulative, i.e. they contain fixes released in earlier update Rollups for the same product level (RTM, SP). This means you don’t need to install previous Rollups during a fresh installation but can start with the latest Rollup package.

As with any Hotfix, Rollup or Service Pack, I’d recommend to thoroughly test this rollup in a test and acceptance environment first, prior to implementing it in production.
You can download Exchange 2010 SP3 Rollup 2 here.

Exchange 2010 SP2
For those still on Exchange 2010 SP2, Microsoft released Exchange 2010 SP2 Rollup 7. This Rollup only includes the MS13-061 security fix and raises Exchange 2010 SP2′s version number to 14.2.375.0, can be downloaded here; the related KB article is KB2874216.