In today’s climate IT departments are under a lot of pressure to cut costs yet maintain services that don’t compromise on features. So it’s no surprise we hear more and more the questions, “How does Zimbra total cost-of-ownership (TCO) compare with Microsoft Exchange?” In fact, it recently hit #3 on our popularity chart as organizations contemplate Exchange upgrades again (we’ll save the top two questions for another day).
Public field data typically shows Zimbra Collaboration Suite ahead of MS Exchange Server when licensing and hardware costs are compared for various on-premises deployments. However, while licensing and hardware cost data is readily available, perhaps the most significant recurring cost components in the equation are less well documented — additional time spent administering servers and software and the high cost of support contracts.
This cost differential often gets hazy because most organizations do not closely log time spent on specific tasks, including software administration or escalated user support issues. Instead, in most circles you simply hear something analogous to “my Exchange servers are really cranky.” But how much valuable productivity are you actually losing?
|Per User Cost||$7.5||$3|
|Above: Penn admin resource distribution and resulting monthly per-user costs charged back to departments
According to Adam Preset, an IT Technical Director in Information Systems & Computing (Penn’s central IT organization), Penn’s IT Services added Zimbra 18 months ago to provide departments across the campus a Web 2.0 option in addition to Microsoft Outlook and Exchange 2007 (Zimbra can share Active Directory, resources and free-busy times with Exchange). Today their split-mode deployment consists of 3,100 Exchange users and 13,700 Zimbra users (each with grad students, faculty and employees) running equivalent feature sets (email, calendaring, sharing, mobile, etc).
Split-mode deployments are not uncommon (see Argonne National Labs), but in the case of Penn, the central IT staff’s administration time is closely logged on each system because they charge back time for service rendered to the other departments. Combined with a single team managing both systems simultaneously in split-mode and you have a natural control for cost data.
Adam says they have found Zimbra takes significantly fewer man-hours to administer. In absolute terms Exchange servers take 33% more effort and require one extra full-time headcount per year — even with 4.4 times more users on the Zimbra servers.
Here is a video where Adam discusses their deployment, cost methodology and why more users chose Zimbra over Exchange on campus:
Adam later noted, “to bring the Exchange user base up to Zimbra’s scale and provide the expected level of support we’d need to hire new administrators – probably two or more FTEs, which isn’t practical.”
He also added that common culprits impacting costs in the Microsoft deployment are Outlook client and PST data issues, more support needs on the desktop due to lack of adoption of Outlook Web Access (OWA), Exchange data restores and more frequent server downtime. Whereas advantages for Zimbra are easier overall server administration and fewer help desk incidents because so many users say they prefer the Zimbra AJAX Web Client over traditional desktop clients.
So what’s the key take-away? Though every organization has different cost sensitivity; data points like this serve as gentle reminders not to forget the whole picture. While a license discount or storage price drop can be helpful for initial TCO calculation, the human capital component is key to understanding real long-term value!
Adam Preset spoke at EDUCAUSE Annual with Pam Buffington of Georgia Tech on “Implementing a Cost-Effective and User-Friendly E-Mail, Calendaring, and Collaboration System.”