Zimbra Forums

Thanks Eugene. Additional clarifications in the release notes will be very useful.

In the release notes for ZCB 5.0.19 you can find these recommendations: ---------------------------------------------- Hardware Recommendation Quad Core 16 GB RAM 500+ GB hard drive space ----------------------------------------------- My 3 ZCB 5.0.18 servers have only 4 GB RAM. Is it OK if I upgrad...

Thanks Eugene, No, I have NOT and the problem is I'm not confident this would work!? First of all you said that moving the zdbs MAY help and in the previous message Tony had said this was unsupported. Also, I originally had installed ZCB BETA 3 a year ago, then upgraded to BETA 4 then to ZCB GA. Whe...

I need to migrate around 5o BES/ZCB users with BB to a new hardware. I had received a migration SRP license from RIM and followed their migration procedure as it were BES for Exchange. I could see two servers listed in the BlackBerry manager and I could move users from my old server to the new one. ...

Thanks. Just installed ZCO 5.0.12 and was able to uncheck the Errors to Inbox.

I do have the HKEY_LOCAL_MACHINESOFTWAREimbra but not the turnOffInboxFailures key.
From time to time I would also receive the Server Failures notices but not as often as Bosco.
I think the ZCO 5.0.12 is not yet posted on the distribution site.
Rasim Duric

I think you should purchase a BES server for Exchange which comes with 20 client licences. The Zimbra Connector for BlackBerry works well when you don't have too many BB users (25 or less per ZCB server).

Look at this bug in the newest ZCS and ZCB versions:

Bug 33227 – Duplicate address book on BB handhelds.

I think I had seen once something like a NULL message on my BB and I just deleted it. Didn't have time to investigate. Never heard from my BB users with respect to these messages though.
Yeah, BETA 3 is working but not even close to be perfect!!!

Could you also restart the BB Dispatcher service? I would stop the BB Controller first and than stop the BB Dispatcher. A restart is just the opposite, first restart the Dispatcher and than the Controller.