Ajcody-Mobile-Topics: Difference between revisions
Line 63: | Line 63: | ||
* Cross link supported mobile device page with wiki page setup how-to for that model | * Cross link supported mobile device page with wiki page setup how-to for that model | ||
** http://bugzilla.zimbra.com/show_bug.cgi?id=43995 | ** http://bugzilla.zimbra.com/show_bug.cgi?id=43995 | ||
*** Internal work about updating http://www.zimbra.com/ | *** Internal work about updating http://www.zimbra.com/products/zimbra_mobile_device_list.html and creating how-to's for models. | ||
====Special Note About Nokia's==== | ====Special Note About Nokia's==== |
Revision as of 12:23, 18 March 2010
- This article is NOT official Zimbra documentation. It is a user contribution and may include unsupported customizations, references, suggestions, or information. |
Mobile & Phone Issues
Actual Mobile & Phone Topics Homepage
Please see Ajcody-Mobile-Topics
Help Me Understand the Mobility Options
Let's break it down to three forms of access for mobile devices.
Mobile Web Client - http://www.zimbra.com/products/mobile_web_browser.html
A. Setups the web access to the Zimbra server to be viewable from a mobile device. This is accessing mail over the "web browser" on the mobile phone.
A1. http://servername.com/zimbra/m/
B. Built in - no license or additional software needed.
Zimbra Mobile - http://www.zimbra.com/products/mobile_smartphone.html
A. This allows two-way, over-the-air synchronization between the mobile device and Zimbra server.
A1. Think of this as "fat client" mail sync'ing on a mobile device
B. This page will describe that process in better detail - http://wiki.zimbra.com/index.php?title=Mobile_Device_Setup
C. License required
Blackberry - http://www.zimbra.com/products/mobile_blackberry.html
A. Blackberry "two-way, over-the-air synchronization" requires the use of a Blackberry server. We use a "connector" on the Blackberry server that allows BES device to use their "fat client" for mail sync'ing.
B. This option requires a separate server, a Windows box that will run the Blackberry server software.
C. Zimbra Mobile license required. Windows Blackberry server require with appropriate Blackberry licenses. Installation of Zimbra BlackberryConnector on the Blackberry server.
Zimbra Mobile/Blackberry requires the license file to enable it. This cost can be discussed with your sales contact. It's only the Blackberry configuration that requires a "software" installation - so to speak. Enabling "Zimbra Mobility/option 2 above" is a license requirement - not a software installation one - and then configuration for the user. "You enable Zimbra Mobile in the ZCS COS or for individual Accounts."
Forum Support For Mobile Options
The Mobility Forum has three sections.
General Mobile Issues
What Devices Are Supported And How-To
I've made the following RFE's recently. I'm hoping we continue doing this going forward as well.
- Official Support for Google Android Phone
- http://bugzilla.zimbra.com/show_bug.cgi?id=43988
- Support has been trying to add specific how-to details for the various email software packages that Android phones can come with as we get availability to them. Please feel free to do likewise if you find your software isn't listed and your comfortable with describing how to set it up for others.
- http://bugzilla.zimbra.com/show_bug.cgi?id=43988
- Official Support for Palm Pre Phone
- Cross link supported mobile device page with wiki page setup how-to for that model
- http://bugzilla.zimbra.com/show_bug.cgi?id=43995
- Internal work about updating http://www.zimbra.com/products/zimbra_mobile_device_list.html and creating how-to's for models.
- http://bugzilla.zimbra.com/show_bug.cgi?id=43995
Special Note About Nokia's
- Official Support for Nokia N97 Phone
- Official Support for Nokia E52 Phone
- Official Support for Nokia E75 Phone
From Nokia's Website :
- Supported devices:
- Nokia devices with ActiveSync built into the email client:
- Nokia E75, Nokia E72, Nokia E55, Nokia E52, Nokia N86 8MP, Nokia 6710 Navigator and Nokia 6730 classic
- Nokia devices with ActiveSync built into the email client:
- Nokia devices with Mail for Exchange email client:
- Certified devices:
- Nokia Eseries: Nokia E51, Nokia E63, Nokia E66, Nokia E71, Nokia E90
- Nokia Nseries: Nokia N76, Nokia N81, Nokia N81 8GB, Nokia N82, Nokia N95, Nokia N95 8GB
- Other Nokia S60 3rd Edition devices: Nokia 6120
- Enabled devices:
- Nokia 5700 Xpress Music, Nokia 6110 Navigator, Nokia 6121, Nokia 6210 Classic, Nokia 6290
- Certified devices are devices on which the functionality of the Mail for Exchange software client has been validated.
- Enabled devices are devices on which the functionality of the Mail for Exchange software client has not been validated individually, but where the functionality of the Mail for Exchange software client on a certified device has been validated in the same software branch.
- Certified devices:
Some Issues Addressed On Nokia'S Support Forum:
- Nokia's : * Discussions Main Page * Tips and Troubleshooting * Messaging
- "MAILFOREXCHANGE where is the outbox?"
Mobiles And GAL Searches
Some RFE's to watch:
- "RFE: Doc from test/qa what mobiles & their software can search against in GAL"
- "zimbraAccount missing useful attributes"
Bugs To Be Aware Of
- "Sync tasks for ZimbraMobile"
- "MobileSync Multiple Calendars and Addressbooks"
Zimbra Mobile And ActiveSync Technology
Zimbra Mobile on Windows Mobile Smartphones, Nokia Business Series Smartphones, Apple iPhones, Palm Treo or any other Smartphones that natively uses the ActiveSync Technology
Understanding how Direct Push works:
Understanding Direct Push, From MS Exchange Server 2010 Help
Make sure you review the other pages for this subject that will show on the left hand side.
Windows Mobile Emulator For Testing
You can use the following to setup a Window Mobile emulator for testing.
- Virtual PC 2007
- Microsoft Device Emulator 2.0 -- Standalone Release
- Windows Mobile 5.0 Image
- Windows Mobile 6.0 Standard Image
- Windows Mobile 6.0 Professional Image
iPhone General Topics
iPhone And Caldav
See Ajcody-Apple-Mac-Issues#iTunes_.26_iPhone_configuration_for_CALDAV
iPhone And SSL Certs
Send CRT File To iPhone By Email
For a self-signed certificate file on the ZCS server, path is /opt/zimbra/ssl/zimbra/server/server.crt
If you email yourself the crt file and read the message from the iTouch/iPhone device, you'll get a "install" button to push.
Setup Webserver To Server Out CRT
For a self-signed certificate file on the ZCS server, path is /opt/zimbra/ssl/zimbra/server/server.crt
Please see the following:
- http://io.yort.com/self-signed-imap-ssl-certs-on-iphone
- http://download.gna.org/savane-doc/savane-install-guide-HTML/x562.html
iPhone 2 Topics
iPhone 2 Support & Features With Zimbra
Here's three nice references to review:
- http://www.zimbra.com/forums/announcements/19110-iphone-2-zimbra.html
- http://www.zimbrablog.com/blog/archives/2008/07/zimbra-mobile-for-iphone.html
- http://www.zimbrablog.com/blog/archives/2007/07/izimbra.html
iPhone 2 Bugs
- "iphone: sync with shared contacts and calendars"
- http://bugzilla.zimbra.com/show_bug.cgi?id=30950
- For search, shared calendar - shared calendars
- http://bugzilla.zimbra.com/show_bug.cgi?id=30950
- Bug 29749 "iPhone 2.0 should be able to sync multiple calendars"
- Bug 29899 "iPhone 2.0 + Zimbra Mobile Sync can cause high CPU usage for large mailboxes"
- Bug 29902 "Address book photo doesn't sync via iPhone 2 ActiveSync"
- Bug 29903 "iPhone 2.0 Zimbra <-> ActiveSync Push Mail Does Not Put Phone into Standby Mode, Consuming Battery Quickly"
- Bug 29909 "iPhone 2.0: mailbox folders missing on device"
- Bug 30008 "some appointments missing on iPhone2.0 with zimbra mobile"
- http://bugzilla.zimbra.com/show_bug.cgi?id=30008
- This is a duplicate bug for 30304 "VersaMail 3.5 does not sync calendar appointments"
- Bug 30501 "Reply doesn't show in iPhone 2.0"
BES Connector Issues
Bugs & RFE's
Import Ones To Note First
- "ZCB PDF needs to include information on server sizing and ZDBs"
- "BB: ZCB/BES Sizing Data Needed"
- http://bugzilla.zimbra.com/show_bug.cgi?id=22415
- Recommended Maximum Number Of Users Per BES Server - 50
- The recommended max is 50 users. After recommended max. is reached you may receive error message in BES MAGT log file indicating that user was not added successfully.
- Recommended Maximum Number Of Users Per BES Server - 50
- http://bugzilla.zimbra.com/show_bug.cgi?id=22415
- "BES/ZCB doc's for restore and server move's"
- "BB: multi-tenancy"
- http://bugzilla.zimbra.com/show_bug.cgi?id=17026
- "support multi-domains in blackberry connector" - was marked as "Duplicate" of 27986 above.
- http://bugzilla.zimbra.com/show_bug.cgi?id=17026
- "BES and Proxy" [GunsNRoses]
- http://bugzilla.zimbra.com/show_bug.cgi?id=33179
- Description: Per the ZCB documentation, the BES server needs to talk to a single Zimbra mailbox server over 443 and 7071. The problem is that the mailbox servers are behind the Zimbra Proxy and are running in reverse-proxy mode - meaning, they only serve over basic http (port 80) and NOT over 443. The proxy servers serve over 443 - but do not do the 7071. So, we can't point the BES server at a Zimbra mailbox server because the Zimbra mailbox server is not listening over 443 due to being accessed through the proxy. We can't point the BES at a Zimbra proxy server because they do not handle 7071.
- Another related bug, as it will pertain to the 6.0 release:
- "ZCB fails if zimbraMailSSLPort is changed"
- Another related bug, as it will pertain to the 6.0 release:
- Description: Per the ZCB documentation, the BES server needs to talk to a single Zimbra mailbox server over 443 and 7071. The problem is that the mailbox servers are behind the Zimbra Proxy and are running in reverse-proxy mode - meaning, they only serve over basic http (port 80) and NOT over 443. The proxy servers serve over 443 - but do not do the 7071. So, we can't point the BES server at a Zimbra mailbox server because the Zimbra mailbox server is not listening over 443 due to being accessed through the proxy. We can't point the BES at a Zimbra proxy server because they do not handle 7071.
- http://bugzilla.zimbra.com/show_bug.cgi?id=33179
Status Of Unconfirmed, New, Assigned, Reopened As Of April 27, 2009
Release Target Version Was Based Upon April 27, 2009. Please goto bug/rfe link for status changes.
- "BB: Support for cradle provisioning" [Helix]
- "BB: Folder redirection for non top-level folders may stop working"
- http://bugzilla.zimbra.com/show_bug.cgi?id=17035 [GunsNRoses]* "
- "BB: need to set full display name when sending mail" [Helix]
- "duplicate appointment created" [GunsNRoses]
- "BB: Support access to email removed from local cache" [GunsNRoses]
- "BB: should reuse zdb on delete/add user" [Helix]
- "BB: new message timestamp is ambiguous" [GunsNRoses]
- "UI for ZCB related settings" [GunsNRoses]
- "BB: Enterprise Activation may not work on the first try" [GunsNRoses]
- "BB: unable to sync contacts database error" [GunsNRoses]
- "BB: no status for the initial sync of users" [Helix]
- "BB: Installer fails with no error msg if mapi32.dll is in use" [GunsNRoses]
- "BB: Can the MAPI/CDO PST provider replace Outlook's PST provider?" [GunsNRoses]
- "BB: BES Manager may be limited by ZCB"
- http://bugzilla.zimbra.com/show_bug.cgi?id=22864
- Related to the following bug:
- http://bugzilla.zimbra.com/show_bug.cgi?id=22864
- "BB: local/server failures need more information" [GunsNRoses]
- "BB: Outlook CDO.DLL being registered instead of Exchange's Version" [GunsNRoses]
- "BB: ZDB should detect and perform mailbox rebuilding/reindexing" [Helix]
- "BB Admin Integration w/Zimbra admin console" [Helix]
- "ZCB: Calendar issue when moving recurring appointments" [GunsNRoses]
- "BB: USB activation needs verification" [Helix]
- "Gal Lookups don't return all fields" [GunsNRoses]
- "BB: GetContentsTable() failed with 0x80040119 HRESULT" [GunsNRoses]
- "emails sent from a BlackBerry have incorrect headers" [IronMaiden]
- "Latency of new message arrival to device is too high for large BES deployments" [Helix]
- "BB: user config tool to assign users to static agents" [GunsNRoses]
- "BB: support in process calhelper" [Helix]
- "BB: ID Mapper state seems invalid on BES frequently" [GunsNRoses]
- "BB: Revisit Store Advise Sink implementation" [GunsNRoses]
- "BB: Only BB sent mail can be viewed in the Sent Items folder on the device." [GunsNRoses]
- "BB: Slow sync for a user will delay syncs for other users on the same server" [GunsNRoses]
- "Add a connector for a shared/global contact list on all Blackberry's" [Not Committed]
- "BB: Divide InitialAge for eMail and Calendar" [GunsNRoses]
- "BES log says: Error creating OOF Rule in CreateOOFRule" [Helix]
- "WaitSet APIs don't properly handle mailbox moves" [GunsNRoses]
- "BB: Enhancement. Only sync Inbox and Sent Items mail folders" [GunsNRoses]
- "Verifying MAPI/CDO version before upgrading." [Helix]
- "ZCB should resync BES admin after it's locked" [GunsNRoses]
- "setup test case simulating running out of space while while zdb file size is growing" [Helix]
- "Implement proper re-authentication logic for zcb" [Helix]
- "Cal replies from BB rejected - appointments deleted randomly" [GunsNRoses] [locked]
- "Hard shutdown of BES machine may lead to failures on restart" [Helix]
- "BB: Changes to single instance of recurring event not changing recurring event display" [Not Committed]
- "admin account is included in each waitset and the bes connector also create an extra waitset for the admin account" [GunsNRoses]
- "bes manager crash upon shutdown" [GunsNRoses]
- "BES: bes agent randomly fails to mount the mailbox in the first attempt. retries succeeds." [GunsNRoses]
- "BES: 1. bes agent occasionally hit segfault in initialization stage. 2. some agent failed to track the accounts assigned to them." [GunsNRoses]
- "Ability to Sync BB memopad" [Helix]
- "Reconciliation Wizard enhencement: set threshold for the value of delta" [Not Committed]
- "Resync items that have failed" [GunsNRoses]
- "Windows Update or Outlook repair can break BES functionality" [Not Committed] [Blocker]
- "Tool to validate ZCB Configuration" [Helix]
- "Support for Free/Busy lookup" [Helix]
- "BES : (main branch) 1.agent crash under load test, 2. data missing for some of the users in waitset" [Not Committed]
- "BES: BB manager fails to get started if the ZCS server was stopped and no error messages given." [GunsNRoses]
- "BES 5.0" [support with ZCB] [GunsNRoses]
- "Inner provider reports out of memory at 300MB reserverd memory" [GunsNRoses]
- "7 out of 50 tasks aren't showing in BB" [Not Committed]
- "BES: appointment data failed to get synced in multi-agent scenario" [Not Committed]
- "Filter out delegate-calendar forwarded invite emails when syncing to BB device" [GunsNRoses]
- "Profile not getting mounted even after installing BES Connector." [Not Committed]
- "BES:bes agent memory dump during the load test." [Not Committed]
- "Documentation of dependencies for the Blackberry Connector is insufficient" [Not Committed]
- "Bes: BES Manager queries only internal gal" [Not Committed]
- "Password change for windows and bb services breaks ZCB/Bes Sync" [GunsNRoses]
- "Avoid reprovisioning and reactivating users after re-creating BBServer and BBManager profiles" [GunsNRoses]
- "ZCB Contact Item fields do not have a one - to - one correspondence with ZWC." [GunsNRoses]
- "ZCB cannot get Zimbra GAL" [GunsNRoses]
- "waitset dead after traffic started for 10minutes under 100users 2agents" [Franklin - keyword 5.0.17]
- "Test and Certify MS Outlook 2k7 SP2 with ZCB 6.0 SMB" [Not Committed]
- "Update GAL sync logic" [Not Committed]
- "At times email items deleted using the ZWC does not get deleted from ZCB" [Not Committed]
- "EULA for ZCB still mentions 'BETA'" [Franklin - keyword 5.0.17]
BES Wiki Pages
See Wiki Category ZCB.
Split-DNS Issue
If your running split-dns for zimbra, make sure your BES box is configured to use the right DNS servers because it will pull the zmhostname variable and you don't want it resolving to the external ip address.
Duplicate Calendars
One customer reported that "updating the firmware to 4.5.0.37 (as I'm at now) fixed the issue with the duplicate calendar".
Upgrade Steps For ZCB
The Bascis
The normal upgrade process is to
- Shutdown BES [ see Correct_order_to_stop_and_start_BES_services ]
- Make sure outlook.exe isn't running
- Run the msi
- Restart/Start BES [ see Correct_order_to_stop_and_start_BES_services ]
From Beta2 To BES SMB - Outlook 2003 To Outlook 2007 Requirement
Here is the list of steps on how to upgrade from BETA2 to BES SMB:
- Stop BB controller [ see Correct_order_to_stop_and_start_BES_services ]
- Completely remove Outlook 2003
- (First, go to Add/Remove programs and uninstall Office 2003. And then run the following utility to cleanup stuff left behind. The utility is called ‘Office Removal Wizard’ and located in the \FILES\PFILES\MSOFFICE\OFFICE11 folder on the install CD. OFFCLN.EXE)
- Install Outlook 2007
- Open BES SMB msi to start installation wizard. Accept license agreement and continue following the steps in installation wizard
- Start BB controller [ see Correct_order_to_stop_and_start_BES_services ]