07-23-2009, 05:30 PM
Thumbs Must Hurt
Join Date: Nov 2006
Carrier: Rogers Wireless
Post Thanks: 0
Thanked 0 Times in 0 Posts
Getting fewer every day... personal experience.
1. BES talks to the POA (Post Office Agent) only. Sometimes, when the POA is restarted BES does not pickup. Make sure you do mail flow testing with a user in that POA.
2. BES acts like a GroupWise client and polls Groupwise for new mail
3. Again, just keep an eye on POA. If POA is down, no one gets into their mail including BES. Of course there are other problems that could bring Groupwise down, MTA (Message Transfer Agent), GWIA (Groupwise Internet Agent) etc. but then if those go down that is really a Groupwise issue. I suggest you call Novell or Novell newsgroups for support.
4. Unique to Groupwise BES is that BES can sync to a single Groupwise Address Book that the Admin chooses. I wish Exchange BES had that feature.
Blackberry Tasks and Notes dont exactly work the same way in Groupwise because the Groupwise UI is different.
Address book syncs are slow to come down to the device (random value up to 2 hours) but are quick to sync from device to Groupwise (5 mins.).
5. Groupwise and BES is pretty reliable. BES server uses native Groupwise client APIs to make the connection to the BES server. If you update your Groupwise client on a workstation, make sure the BES server has the same version Groupwise client.
6. Depends on the issue, but the same logs are there. Same troubleshooting rules apply.
7. Sometimes the Novell newsgroups are helpful. But really, you need to attend the BES for Groupwise training from RIM. RIM tech support is also helpful.