Welcome to Zimbra Day at Bucknell! - Bucknell University
Welcome to Zimbra Day at Bucknell! - Bucknell University Welcome to Zimbra Day at Bucknell! - Bucknell University
Welcome to Zimbra Day at Bucknell! uc e
- Page 2 and 3: Today’s agenda 8:45 a.m.: Welcome
- Page 4 and 5: Some Bucknell background • Our ol
- Page 6 and 7: Timeline: Evaluation and purchase F
- Page 8 and 9: Timeline: Implementation • Decemb
- Page 10 and 11: Zimbra project team Name Title Role
- Page 12 and 13: • Imapsync Server challenges •
- Page 14 and 15: User support challenges • 4.5 iSy
- Page 16 and 17: The bottom line: What we we’d d d
- Page 18 and 19: Where are we today? • Web client
<strong>Welcome</strong> <strong>to</strong><br />
<strong>Zimbra</strong> <strong>Day</strong> <strong>at</strong><br />
<strong>Bucknell</strong>! uc e
Today’s agenda<br />
8:45 a.m.: <strong>Welcome</strong>! Breakfast; meet and greet<br />
9:30 – 11:30 a.m.: The <strong>Bucknell</strong> <strong>Zimbra</strong> experience<br />
11:30 a.m. – 1:30 p.m.: Lunch<br />
<strong>Zimbra</strong> roadmap presented by Neil Ringers, Direc<strong>to</strong>r of Sales<br />
Follow-up Follow up discussion and Q & A<br />
1:30 p.m. – 3:00 p.m.: Breakout sessions<br />
Server<br />
Desk<strong>to</strong>p<br />
CIO/CTO<br />
3:00 p.m. – 4:00 p.m.: <strong>Zimbra</strong> 5.0 issues and plans; Q & A<br />
4:00 p.m. p m – Optional <strong>to</strong>ur and Swarthmore Commvault Desk<strong>to</strong>p meeting
This morning’s agenda<br />
• Getting <strong>to</strong> know each other, snapshots of<br />
our environments and our <strong>Zimbra</strong> st<strong>at</strong>us<br />
• The <strong>Bucknell</strong> <strong>Zimbra</strong> experience p<br />
– Project overview<br />
– Wh<strong>at</strong> went well?<br />
– Wh<strong>at</strong> were the challenges?<br />
– Wh<strong>at</strong> would we do differently?
Some <strong>Bucknell</strong> background<br />
• Our old environment<br />
– Email server: Unix/sendmail, pop, imap<br />
– Calendar: Meeting Maker (for staff)<br />
– Email clients: Eudora, Outlook, webmail<br />
(horde/imp)<br />
– Smart phones: mostly Treos, mostly PalmOS
• No integr<strong>at</strong>ion<br />
• PPoor performance f<br />
Why change?<br />
– Inefficient mailbox form<strong>at</strong><br />
– Larger quotas problem<strong>at</strong>ic<br />
– Webmail<br />
• No over-the-air calendar and contact<br />
synchroniz<strong>at</strong>ion for smart phones<br />
• General user diss<strong>at</strong>isfaction with Meeting Maker<br />
and dWWebmail b il<br />
• Calendar scalability
Timeline: Evalu<strong>at</strong>ion and purchase<br />
Fall 2006<br />
– Need for new system becomes evident (webmail, Meeting Maker, smart<br />
phones, h OOutlook); tl k) began b di discussing i need d ffor project j t<br />
January - March 2007<br />
– Researched altern<strong>at</strong>ives, installed demo systems, and consulted other<br />
schools<br />
– Narrowed research <strong>to</strong> Exchange and <strong>Zimbra</strong><br />
April 2007<br />
– Presented both options <strong>to</strong> advisory committees and <strong>University</strong><br />
Management Group; desire for campus-wide calendaring is expressed<br />
by committees<br />
May 2007<br />
– Visit <strong>to</strong> <strong>Zimbra</strong><br />
JJune 2007<br />
– Signed <strong>Zimbra</strong> contract<br />
– Project team form<strong>at</strong>ion
Summer 2007<br />
Timeline: Testing<br />
– Determine ete e hardware a d a e co configur<strong>at</strong>ion; gu <strong>at</strong> o ; oorder de hardware a d a e<br />
– Implement<strong>at</strong>ion planning with <strong>Zimbra</strong><br />
September 2007<br />
– Test server installed, , Outlook installs continue<br />
Oc<strong>to</strong>ber 2007<br />
– Server install<strong>at</strong>ion and configur<strong>at</strong>ion<br />
– System y Administra<strong>to</strong>r training g<br />
– Internal ISR testing begins<br />
– Train the trainer<br />
November 2007<br />
– Multiple Meeting Maker d<strong>at</strong>a migr<strong>at</strong>ion tests<br />
– Pilot with faculty, staff, and students<br />
– Communic<strong>at</strong>ion <strong>to</strong> campus
Timeline: Implement<strong>at</strong>ion<br />
• December 2007<br />
– ZCO rollouts rollo ts<br />
– More campus communic<strong>at</strong>ion<br />
– Introduc<strong>to</strong>ry sessions <strong>to</strong> campus – general and targeted<br />
– Start of mail d<strong>at</strong>a migr<strong>at</strong>ion<br />
• January 2008<br />
– Thursday Thursday, January 33, 2008: Meeting Maker goes down <strong>at</strong> 5 pp.m. m<br />
– Friday, January 4, 2008: Email unavailable <strong>at</strong> midnight<br />
– Monday, January 7, 2008: Go live, Outlook Parties
Project highlights<br />
• <strong>Zimbra</strong> project team<br />
– Membership<br />
– Weekly meeting; subteams met more often<br />
• Project management<br />
– Use of Sharepoint critical
<strong>Zimbra</strong> project team<br />
Name Title Role on Team<br />
Jeannie Zappe Interim Co‐Direc<strong>to</strong>r of ISR Project Sponsor<br />
George Lincoln Interim Direc<strong>to</strong>r of Technology<br />
Integr<strong>at</strong>ion and ISR Project<br />
Management Lead<br />
Jennifer Harper Interim Systems Integr<strong>at</strong>ion Group<br />
Leader<br />
Project Leader<br />
Server Lead, Calendar D<strong>at</strong>a Migr<strong>at</strong>ion<br />
Chris Weber Systems Integra<strong>to</strong>r –Lead UNIX Mail Infrastructure Expert<br />
Lisa Veloz Integr<strong>at</strong>ed Online Services<br />
Technologist and Project Leader<br />
User Experience Lead<br />
Varied Communic<strong>at</strong>ions Lead<br />
Keelan Cleary Technology Support Project Specialist Desk<strong>to</strong>p Deployment Lead
Wh<strong>at</strong> we’d do again<br />
• Meeting Maker d<strong>at</strong>a migr<strong>at</strong>ion with Sum<strong>at</strong>ra;<br />
repe<strong>at</strong>ed test imports<br />
• General and targeted inform<strong>at</strong>ion sessions<br />
• Targeted communic<strong>at</strong>ions<br />
• Conversion <strong>to</strong> Outlook for mail before <strong>Zimbra</strong><br />
• Moving <strong>to</strong> one password for all key systems<br />
(AD)<br />
• Take care of your y staff when they y are running g<br />
fast and hard<br />
• Project management approach
• Imapsync<br />
Server challenges<br />
• Mail d<strong>at</strong>a migr<strong>at</strong>ion<br />
• Load testing<br />
• Server naming<br />
• TTomc<strong>at</strong> t and d JVM iissues and d other th settings<br />
tti
User support challenges<br />
• Getting all Meeting Maker users <strong>to</strong> Outlook prior<br />
<strong>to</strong> <strong>Zimbra</strong><br />
• ZCO:<br />
– Testing<br />
– Functionality<br />
– Error handling<br />
– Distribution (au<strong>to</strong>m<strong>at</strong>ion, chunking)<br />
– Settings<br />
• Lack of ZCO document<strong>at</strong>ion<br />
• Calendar download time
User support challenges<br />
• 4.5 iSync<br />
• <strong>Day</strong> 1 planning and weeks 1 and 2 after<br />
go live<br />
– Launch parties<br />
– Downloading d<strong>at</strong>a<br />
– GGetting tti settings tti right i ht<br />
• Smart phones<br />
• Importing contacts and mail from local<br />
PSTs
The bot<strong>to</strong>m line:<br />
Wh<strong>at</strong> we we’d d do differently<br />
• Separ<strong>at</strong>e mail and calendaring (ZCO)<br />
implement<strong>at</strong>ion<br />
– Good ZCO testing<br />
– Live calendar testing<br />
– BBetter tt Smartphone S t h testing t ti<br />
– Load distribution/testing<br />
• To really y understand how the ZCO worked we<br />
needed <strong>to</strong> understand how Exchange worked<br />
• Figure out wh<strong>at</strong>’s different between old and new<br />
system and communic<strong>at</strong>e those differences<br />
early<br />
• Communic<strong>at</strong>ion was <strong>to</strong>o much/<strong>to</strong>o fast/<strong>to</strong>o long
The bot<strong>to</strong>m line:<br />
Wh<strong>at</strong> we we’d d do differently<br />
• Failure analysis<br />
– ZCO: How can we make this product fail?<br />
• Ask <strong>Zimbra</strong> for the expert(s) p ( ) yyou<br />
need<br />
• Meet more often than once a week<br />
• Perhaps we could have waited for 55.0 0<br />
(bug-wise)<br />
• HHow could ld GGartner t hhave hhelped l d us with ith<br />
our research about the players?
The bot<strong>to</strong>m line:<br />
Test environment consider<strong>at</strong>ions<br />
• Consider and plan for load testing early the<br />
process ( (and d perhaps h bbefore f you sign i th the<br />
contract)<br />
• UUnderstand d t d hhow people l currently tl use your<br />
systems; make a list of tasks and clients<br />
• Understand your smart phone flavors and test<br />
accordingly<br />
• You will never be able <strong>to</strong> test for everything<br />
• Figure out how <strong>to</strong> live in the ZCO
Where are we <strong>to</strong>day?<br />
• Web client seemingly well received<br />
• Nearly all issues are with ZCO<br />
• Some server issues<br />
• Planning for SAN expansion this spring<br />
• Pl Planning i ffor a Zi <strong>Zimbra</strong> b 55.0x 0 iimplement<strong>at</strong>ion l t ti<br />
over Memorial <strong>Day</strong> weekend<br />
• Planning for future fail-over environment
<strong>Zimbra</strong> 5.0x<br />
• Sharing of issues and plans<br />
•Q & A