Welcome to Zimbra Day at Bucknell!

Transcription

1 Welcome to Zimbra Day at Bucknell!

2 Today s agenda 8:45 a.m.: Welcome! Breakfast; meet and greet 9:30 11:30 a.m.: The Bucknell Zimbra experience 11:30 a.m. 1:30 p.m.: Lunch Zimbra roadmap presented by Neil Ringers, Director of Sales Follow-up discussion and Q & A 1:30 p.m. 3:00 p.m.: Breakout sessions Server Desktop CIO/CTO 3:00 p.m. 4:00 p.m.: Zimbra 5.0 issues and plans; Q & A 4:00 p.m. Optional tour and Swarthmore Commvault Desktop meeting

3 This morning s agenda Getting to know each other, snapshots of our environments and our Zimbra status The Bucknell Zimbra experience Project overview What went well? What were the challenges? What would we do differently?

4 Some Bucknell background Our old environment server: Unix/sendmail, pop, imap Calendar: Meeting Maker (for staff) clients: Eudora, Outlook, webmail (horde/imp) Smart phones: mostly Treos, mostly PalmOS

5 Why change? No integration Poor performance Inefficient mailbox format Larger quotas problematic Webmail No over-the-air calendar and contact synchronization for smart phones General user dissatisfaction with Meeting Maker and dwebmail Calendar scalability

6 Timeline: Evaluation and purchase Fall 2006 Need for new system becomes evident (webmail, Meeting Maker, smart phones, Outlook); began discussing i need for project January - March 2007 Researched alternatives, installed demo systems, and consulted other schools Narrowed research to Exchange and Zimbra April 2007 Presented both options to advisory committees and University Management Group; desire for campus-wide calendaring is expressed by committees May 2007 Visit to Zimbra June 2007 Signed Zimbra contract Project team formation

7 Timeline: Testing Summer 2007 Determine e hardware a configuration; o order hardware a Implementation planning with Zimbra September 2007 Test server installed, Outlook installs continue October 2007 Server installation and configuration System Administrator training Internal ISR testing begins Train the trainer November 2007 Multiple Meeting Maker data migration tests Pilot with faculty, staff, and students Communication to campus

8 Timeline: Implementation December 2007 ZCO rollouts More campus communication Introductory sessions to campus general and targeted Start of mail data migration January 2008 Thursday, January 3, 2008: Meeting Maker goes down at 5 p.m. Friday, January 4, 2008: unavailable at midnight Monday, January 7, 2008: Go live, Outlook Parties

9 Project highlights Zimbra project team Membership Weekly meeting; subteams met more often Project management Use of Sharepoint critical

10 Zimbra project team Name Title Role on Team Jeannie Zappe Interim Co Director of ISR Project Sponsor George Lincoln Jennifer Harper Interim Director of Technology Integration and ISR Project Management Lead Interim Systems Integration Group Leader Project Leader Server Lead, Calendar Data Migration Chris Weber Systems Integrator Lead UNIX Mail Infrastructure Expert Lisa Veloz Integrated Online Services Technologist and Project Leader User Experience Lead Varied Communications Lead KeelanCleary Technology Support Project Specialist Desktop Deployment Lead

11 What we d do again Meeting Maker data migration with Sumatra; repeated test imports General and targeted information sessions Targeted communications Conversion to Outlook for mail before Zimbra Moving to one password for all key systems (AD) Take care of your staff when they are running fast and hard Project management approach

12 Server challenges Imapsync Mail data migration Load testing Server naming Tomcat and JVM issues and other settings

13 User support challenges Getting all Meeting Maker users to Outlook prior to Zimbra ZCO: Testing Functionality Error handling Distribution (automation, chunking) Settings Lack of ZCO documentation Calendar download time

14 User support challenges 4.5 isync Day 1 planning and weeks 1 and 2 after go live Launch parties Downloading data Getting settings right Smart phones Importing contacts and mail from local PSTs

15 The bottom line: What we d do differently Separate mail and calendaring (ZCO) implementation Good ZCO testing Live calendar testing Better Smartphone testing ti Load distribution/testing To really understand how the ZCO worked we needed to understand how Exchange worked Figure out what s different between old and new system and communicate those differences early Communication was too much/too fast/too long

16 The bottom line: What we d do differently Failure analysis ZCO: How can we make this product fail? Ask Zimbra for the expert(s) you need Meet more often than once a week Perhaps we could have waited for 5.0 (bug-wise) How could Gartner have helped us with our research about the players?

17 The bottom line: Test environment considerations Consider and plan for load testing early the process (and perhaps before you sign the contract) Understand d how people currently use your systems; make a list of tasks and clients Understand your smart phone flavors and test accordingly You will never be able to test for everything Figure out how to live in the ZCO

18 Where are we today? Web client seemingly well received Nearly all issues are with ZCO Some server issues Planning for SAN expansion this spring Planning for a Zimbra 5.0x implementation ti over Memorial Day weekend Planning for future fail-over environment

19 Zimbra 5.0x Sharing of issues and plans Q & A