Zimbra APxJ Partner Summit - Techincal Track
•
7 gefällt mir•8,218 views
Zimbra APxJ Partner Summit - Techincal Track
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Andere mochten auch
Andere mochten auch (18)
Ähnlich wie Zimbra APxJ Partner Summit - Techincal Track
Ähnlich wie Zimbra APxJ Partner Summit - Techincal Track (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Zimbra APxJ Partner Summit - Techincal Track
- 3. • Zimbra Talk • Cisco UC • Customizations 3 May 16 Zimbra Partner Summit 2016
- 9. Zimbra Talk Caveats • DNS server needs to be accessible by the user, Zimbra Server and the Zimbra Talk Server • Installer creates a zone /ile that can be used with dnsmasq • All the certi/icates used by the Zimbra Talk server must be valid and cover all required names o yourdomain.tld o xmpp.yourdomain.tld o conference.yourdomain.tld o external.yourdomain.tld o conference.external.yourdomain.tld o auth.yourdomain.tld o jitsi-videobridge.yourdomain.tld o focus.yourdomain.tld 9 Zimbra Partner Summit 2016 May 16
- 11. UC Integrations – Cisco 8.7 brings back UC Integration: • Click-2-Call§ • Visual Voicemail • Presence Noti/ication • WebEx (WebEx Cloud and WebEx On-Premise) • ZD support for WebEx • Roadmap – ZD support for Click2Call § - will work without the Cisco Unity Connection server which was a dependency in 8.5 or lower 11 Zimbra Partner Summit 2016 May 16
- 12. 3rd Party Integrations Universal Dialer (from Zetalliance) • Support as many PBX systems as possible allowing to originate a call through a SIP phone • Support 1. SipX/SipXecs (working) 2. Asterisk (working, to be improved) 3. 3cx (not tested) 4. MetaSwitch (not tested) • Available from here – https://github.com/ZeXtras/universal-dialer 12 Zimbra Partner Summit 2016 May 16
- 13. 3rd Party Integrations ownCloud (from Zetalliance) • Designed for Zimbra version 8.6 and ownCloud versions 8 and 9 • Demo video: https://www.youtube.com/watch?v=gfVLE22kJ6o • User manual : http://barrydegraaff.github.io/owncloud/ • Available from here – https://github.com/Zimbra-Community/owncloud-zimlet 13 Zimbra Partner Summit 2016 May 16
- 19. Themes and Skins • Zimbra web client allows customization of the look and feel using skins • Skins can be applied at the user/domain/server Chameleon Skin • Theme applied to a domain • The chameleon skin is *not* a skin at all • Instead, it is a collection of LDAP attributes that affect the appearance of *all* of the skins for a given domain 19 Zimbra Partner Summit 2016 May 16
- 21. Anatomy of a Skin • Zimbra WebApps - /opt/zimbra/jetty/webapps/zimbra/ • Individual skin – WebApps/skins/<skin_name> • https:///iles.zimbra.com/docs/skins/Themes.html • Main components of a skin – 1. manifest.xml - XML /ile that describes the skin to the application. Each /ile item in the manifest represents a /ile that will be loaded in as part of your skin. 2. skin.properties - sets up most skin variables (override from skins/_base/base3/skin.properties) 3. Copy an existing skin (sand or lake) to a new skin 21 Zimbra Partner Summit 2016 May 16
- 22. Sample Skin # Sample Skin SkinName = MySkin SkinVersion = 1.0 LogoImgDir = /zimbra/skins/@SkinName@/logos LogoURL = http://www.yourcompany.com LoginBannerImg = @LogoImgDir@/LoginBanner.png LoginBanner = @img(, LoginBannerImg, 500px, 160px)@ AppBannerImg = @LogoImgDir@/AppBanner.png AppBanner = @img(, AppBannerImg, 110px, 35px)@ LogoWidth = 120px; AppC = #fec855 #base color of the background and most of the application AltC = #ddbc76 #base color for toolbars and highlighted buttons SelC = #ffffcc #highlight color for lists, such as the list of messages 22 Zimbra Partner Summit 2016 May 16 WebAppsskins |------- MySkin |------ skin.properties |------ manifest.xml |------ logos |------ LoginBanner.png |------ AppBanner.png
- 25. Other Skin Files … • skin.html – Provides structure to the application layout (eg: where to put components like the Overview Tree and Mini-Calendar) • splash.html – Provides HTML for the Splash Screen, which is displayed to the user as the application is loading. • skin.js – Provides a bridge or Application Programming Interface (API) between the skin and the main application code of the ZWC (eg: custom menus, changes in Preferences) • skin.css – CSS selectors for the skin and splash screen themselves 25 Zimbra Partner Summit 2016 May 16
- 26. Touch Client Logos • Logo on the login and splash screens for the Touch Client 1. Low DPI devices – /skins/_base/logos/TouchLonginBanner.png Dimension of the graphic must be exactly 300 x 65. 2. Retina display - /skins/_base/logos/TouchLonginBanner@2x.png Dimemsion of the graphic must be exactly 600 x 130. • Watermark image in the bottom right of an email 1. Low DPI devices – /skins/_base/logos/TouchWatermarkBanner.png Dimension of the graphic must be exactly 200 x 45. 2. Retina display – /skins/_base/logos/TouchWatermarkBanner@2x.png Dimension of the graphic must be exactly 400 x 90. • Bookmark image on the Springboard (Phone) 1. Low DPI devices – /img/logo/Icon.png (57 x 57) 2. Retina display – /img/logo/Icon@2x.png (114 x 114 ) 26 Zimbra Partner Summit 2016 May 16
- 27. 27
- 30. • Introduction • Prerequisites • Early Planning • Prepare Source Environment • Prepare Middle Environment • Prepare Destination Environment • Zimbra Migration Tool Steps • MX Record Cutover • Post Migration 30
- 31. Introduction 31
- 33. Prerequisites 33
- 34. Prerequisites • Both the Source and the Destination systems must be functional • Destination environment (Zimbra systems) must meet sizing requirement • All environment can communicate each other (speci/ic ports should be opened) • Latest Version of Zimbra Migration Tools installed on Middle Server 34
- 36. Early Planning • De/ine Migration Strategy ( https:///iles.zimbra.com/website/docs/8.6/ Zimbra_Migration_Exchange_Admin_8.6.0.pdf) • Plan DNS Con/iguration Change • Plan how to educate end user to understand that Zimbra features not completely same as Exchange features • Plan the rollback scenario 36
- 38. Prepare Source Environment • Prepare Exchange Administrator account for Outlook Pro/ile • Make sure the necessary ports are opened in order to connect to the Exchange server (TCP 443) and Active Directory Server (TCP/UDP 389, TCP 3268) • Capture existing distribution list • Capture existing Room List • Capture existing aliases 38
- 40. Prepare Middle Environment • Install Windows OS • Create Outlook Administrator Pro/ile • Install Zimbra Migration Tool 40 Exchange Systems (source environment) Middle Server (windows) Zimbra Systems (destination environment)
- 42. Prepare Destination Environment • Make sure the necessary ports are opened (443, 7071) • Create distribution list with no members (one by one manually) • Create Room List (one by one manually) • Create Aliases (one by one manually) 42
- 57. Post Migration • Check Zimbra Service • Check User Accounts • Check Distribution List • Check Room List • Check send / receive email • Change end user outlook con/iguration 57
- 58. 58
- 61. • Zimbra and MS Exchange co-exist overview • Con/igure on both system v Mail /low and integration • Manage user by MS Exchange console • Automatic user provisioning • GAL Con/igure and Authentication Con/igure • Active Directory password change • Q and A 61 <Company Logo>
- 63. Purposes • Migrate legacy LEGO OpenSource email to Zimbra • Single panel of user management in MS Exchange Console • Maintain single user store to better single password policy • Single Global contact for both system 63
- 64. Design 64
- 70. Zimbra ConQigure • Accept All email (avoid recipient check error) • De/ine default route email to MS Exchange Edge Server • De/ine RelayHost via MS Exchange Edge Server • De/ine SMTP submission host to MS Exchange Edge Server • Disable DNS lookup 70 zmprov mcf zimbraMtaDnsLookupsEnabled FALSE zmprov md boonmee.org zimbraMailCatchAllAddress @boonmee.org zmprov md boonmee.org zimbraMailCatchAllForwardingAddress @boonmee.org zmprov md boonmee.org zimbraMailTransport smtp:ad-ex.boonmee.org:25 zmprov mcf zimbraMtaRelayHost ad-ex.boonmee.org:25 zmprov ms $(zmhostname) zimbraSmtpHostname ad-ex.boonmee.org:25
- 83. ADPassword v IMPORTANT NOTE § Authentication Con/igure to Active Directory must select SSL § To select SSL , You have to import Active Directory CA Certi/icate into java certi/icate store 83
- 87. • Introduction • Key Projects • Addressing common issues • Deploying on AWS 87
- 89. My Directory Sdn Bhd • Established in 1999 as a Linux company offering Internet services and solutions. • Founder: Mr. Naisiew Yeak. • Became Zimbra VAR in year 2009. • Our business focus today: Zimbra Deployment. • Other services – Linux support & services, VMware virtualization and AWS cloud migration. 89
- 91. Zimbra for State Government, 2010 • Migrate from Netscape Messaging to Zimbra • Setup Split-Domain to allow old and new system to work together. • Create Self-Service portal for users to approve migrate • Total accounts: 20,000 • Active users: 10,000 • Number of domains: 10 • Platform: VMware VM • Scope: Consult, deploy, customize theme, develop migration script, Preauth SSO, training and technology transfer. 91
- 92. Zimbra Email for ISP, 2011 • Migrate from Scalix to Zimbra • On-shot migration because less data involved. • Total accounts: 40,000 • Active users: 5,000 • Number of domains: 200 • Platform: physical servers with RH cluster in Production and RH virtualization in DR • Scope: Consult, deploy, customize theme, develop migration script, DR failover/fallback script, and MySQL replication. 92
- 94. Issue: A lot of spam! • Make sure Zimbra is enabled to update spam rules: 1. Read: https://wiki.zimbra.com/wiki/Improving_Anti-spam_system 2. zmlocalcon/ig -e antispam_enable_rule_updates=true 3. zmlocalcon/ig -e antispam_enable_restarts=true • Adjust autolearn threashold. 1. bayes_auto_learn_threshold_nonspam -2.0 2. bayes_auto_learn_threshold_spam 9.0 • Integrate 3rd party solution such as E.F.A. Project (efa- project.org), or use commercial Barracuda Email Security Gateway. 94
- 95. Issue: Untrusted self-signed SSL • Use a commercial cert. • Can get FREE commercial cert from StartCom Ltd (startssl.com). • Valid for 1 year. If expired, generate again. • Domain validated for “mail.your-domain.com” and “your- domain.com”. 95
- 96. Issue: Compromised accounts • Some users lost their accounts due to phishing trap. • Use Two-Factor-Authentication – available in Zimbra 8.7. • Before 8.7 publicly available, restrict email access to local network only and use VPN for external connection. 96
- 97. Issue: IP blacklisted • Sending too many mails can cause IP blacklisted. • Solutions: 1. Ensure RDNS is done. 2. Whitelist IP with dnswl.org, barracudacentral.org. etc. 3. Sign up mxtoolbox.com to monitoring your IP. 4. Slow down sending rate for bulk sender. 5. Integrate with AWS SES just in case. • There are more to learn and discover… 97
- 99. Sizing: 100 ~ 200 users • Small deployment work well on low end system: 1. Any modern processor with 4 cores above. 2. 4GB RAM min. 3. RAID1 on 2 disks (7.2K) 4. Direct install on physical server. • Example customer spec: Dell Optiplex 3010, 4GB RAM, 1TB SATA. 99
- 100. Sizing: 500 ~ 1,000 users • Use VMware ESXi and run Zimbra as VM: 1. Any modern processor with 4 cores above 2. 8GB – 16GB RAM 3. RAID6 on 8 disks above (7.2K) 4. Run as VM in single or multiserver mode. 5. Could add other VM such as EFA, pfSense, etc. • Example customer spec: VMware ESXi, 4C, 16GB RAM, iSCSI 100
- 101. Sizing: 10,000 users • Use VMware ESXi and run Zimbra as VM: 1. Any modern processor with 4 cores above 2. 16GB – 32GB RAM 3. RAID6 on 10 disks above (10K) – watch out for IOPs 4. Run in multiserver mode. 5. Could add other VM such as EFA, pfSense, etc. • Example customer spec: VMware ESXi, 4C, 16GB RAM, FC SAN. 101
- 102. Deploying on AWS • We have Zimbra Hosting at AWS Singapore region. • Main attraction for using AWS: 1. We /inally can add values to our email hosting services. 2. No longer bogged down by insuf/icient bandwidth, IOPs, disk space, scalability, backup or redundancy. • With AWS, we could offer unbeatable Zimbra Hosting for small and large businesses. • Current sizing 1. T2.micro – for ldap and proxy with 8GB disk space. 2. T2.small – for mta with 20GB disk space. 3. T2.medium – for mailbox up to 1,000 users. 102
- 103. Thank You! 103